Chatflow

io.github.YersatPublished by GitHub account Yersatv1.0.0Updated Oct 25, 2026

WhatsApp CRM for AI agents: search contacts, read chats, manage the sales pipeline, send messages.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Hosted MCP server for ChatFlow, a WhatsApp/Telegram/Instagram CRM, letting an assistant search contacts, read chats, manage the sales pipeline and optionally, g

What you can do
Search contacts by name or phone substring and create new WhatsApp contacts with a conversation from a phone number. List recent conversations with previews and unread counts, and read a single chat's contact, notes, deal value and recent messages. View the sales pipeline as kanban columns and move a lead between stages or set notes and deal value. Send a text message to a customer when the workspace owner has enabled sending. Check subscription tier, limits and current monthly usage.
When to use it
Useful for small teams running sales or support over WhatsApp, Telegram or Instagram who want an assistant to look up customers, summarize conversations, keep the pipeline up to date, or draft and send replies from the shared inbox.
Requirements
A remote Streamable HTTP endpoint; no local package. A ChatFlow workspace and an API key created by the workspace owner under Settings, AI agents (MCP), sent as an Authorization Bearer header. Sending additionally requires the workspace owner to enable the allow-agents-to-send toggle.
Before you install
The Authorization API key is a workspace credential shown once; keep it private and consider setting an expiry. send_message messages a real customer and counts toward the monthly quota; it is off by default and should stay off unless the agent is trusted. Message text and notes are written by customers, so prompt injection is possible. Moving leads, updating deals and creating contacts change CRM data.

Installation

In SourceWeft

  1. Open Chatflow in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Yersat%2Fchatflow/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "chatflow": {
      "type": "http",
      "url": "https://valuable-sockeye-14.eu-west-1.convex.site/mcp"
    }
  }
}

README

ChatFlow MCP

Connect your AI agent to your WhatsApp CRM.

ChatFlow is a WhatsApp/Telegram/Instagram CRM for small teams — a shared inbox, a drag-and-drop sales pipeline, AI auto-replies, and broadcast campaigns. This is its hosted MCP (Model Context Protocol) server: point Claude, Claude Code, Cursor, or any MCP-compatible agent at your workspace and it can search contacts, read conversations, manage your pipeline, and — when you allow it — send messages.

  • Endpoint: https://valuable-sockeye-14.eu-west-1.convex.site/mcp
  • Transport: Streamable HTTP (stateless)
  • Auth: Authorization: Bearer <API key> — create one in ChatFlow → Settings → AI agents (MCP)

Quick start

  1. In ChatFlow, open Settings → AI agents (MCP) (workspace owner) and click Create API key. Copy it — it's shown once. Optionally give it an expiry.
  2. Add the server to your client:

Claude Code

bash
claude mcp add --transport http chatflow \  https://valuable-sockeye-14.eu-west-1.convex.site/mcp \  --header "Authorization: Bearer cfk_YOUR_KEY"

Claude.ai / Claude Desktop — Settings → Connectors → Add custom connector → paste the endpoint URL and set the Authorization: Bearer cfk_YOUR_KEY header.

Cursor — .cursor/mcp.json:

json
{  "mcpServers": {    "chatflow": {      "url": "https://valuable-sockeye-14.eu-west-1.convex.site/mcp",      "headers": { "Authorization": "Bearer cfk_YOUR_KEY" }    }  }}

Full setup and troubleshooting: docs/setup.md.

Tools

ToolWhat it does
search_contactsFind contacts by name/phone substring
list_conversationsRecent chats with previews, unread counts, CRM fields
get_conversationOne chat: contact, notes, deal value, recent messages
list_pipelineKanban columns with the leads in each stage
move_conversationMove a lead to a pipeline column
update_leadSet notes / deal value on a conversation
create_contactCreate a WhatsApp contact + conversation from a phone number
send_messageSend a text to the customer (opt-in — see below)
get_usageSubscription tier, limits, current monthly usage

Read tools are annotated read-only; send_message is annotated as a world-affecting write so well-behaved clients confirm before calling it.

Sending is opt-in

send_message messages a real customer, so it's off by default. The workspace owner enables it with the "Allow agents to send messages" toggle in Settings. While off, agents can read everything and draft replies, but every send is rejected with a message explaining the toggle. When on, agent sends count toward your monthly quota, appear in the inbox with the AI badge, pause the auto-reply assistant on that chat (so two AIs never answer at once), and support an idempotencyKey so a retry can't double-send.

Prompt-injection note: message text and notes an agent reads are written by your customers. Keep the send toggle off unless you trust the agent driving it.

Links

Source: README.md at commit 4819e63

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.