Dialogbrain MCP server

DialogBrain for Claude Code

Connect WhatsApp, Telegram, email and a chat on your website to one inbox, and build AI agents that answer your customers there — all from Claude Code.

DialogBrain is a customer messaging platform: every channel lands in one shared inbox, with contacts, calls, a task board and AI agents on top. This plugin puts that workspace inside Claude Code as tools, plus six skills that know the order of each setup job.

Install

claude plugin marketplace add saloprj/dialogbrain-claude-plugin claude plugin install dialogbrain@dialogbrain

Then run /mcp inside Claude Code and sign in to DialogBrain in the browser. There is no API key to copy, and the plugin can do exactly what your own account can do, in the workspace you are signed in to.

Things to ask for

Connect my WhatsApp and my work email.

Put a chat widget on example.com. Only allow my domain and keep replies as drafts I approve.

Create an agent that answers customers on WhatsApp and the website chat. Never promise prices. Test it before it answers anyone.

Where did we lose leads this week?

What the skills do

Ask in plain words; the matching skill loads on its own, and only then.

connects what needs no sign-in (an IMAP mailbox, a bot token) straight from the chat, and for the rest sends you a link that opens the exact screen.

• connect-channel — "connect my WhatsApp / my email / a Telegram bot":

restricts it to your domains, hands you the two script tags, and checks that an agent answers.

• setup-livechat-widget — "put a chat widget on my site": creates the widget,

description, wires a trigger, sends a test message and reads the trace.

• create-agent — "an agent that answers my customers": writes it from a

test it.

• voice-agent — "a phone agent": creates it, sets the voice, and calls you to

track what is overdue, comment with screenshots.

• tasks-board — the workspace task board: assign work to people or agents,

the threads, and writes one summary.

• lead-report — "where did we lose leads this week": queries analytics, reads

"notify me on every new lead": narrows the trigger to the messages you care about, then picks what happens — a reply, a note to you, a human takeover, a task on the board.

• react-to-events — "tell me when this person writes", "watch this group",

Letting DialogBrain reach you (not available to everyone yet)

The plugin also ships a channel server, so a DialogBrain agent can hand work to this session instead of answering by itself — a new lead worth judging, a task assigned from a phone.

Read this before trying. Inbound push into a Claude Code session is an experimental feature of Claude Code, and two of its gates are not ours to open:

itself carries, or from your organisation's managed settings. A plugin that is on neither is refused unless the session is started with --dangerously-load-development-channels, which is meant for local development.

• the Channels feature has to be enabled for your account;
• the channel has to be approved. Approval comes from an allowlist Claude Code

So installing the plugin does NOT give you this. It gives you the tools, the skills and the agents, which need no flags at all. If the steps below end with Claude Code saying the channel "is not on the approved channels allowlist", that is this gate, not a mistake on your side, and nothing in the plugin can lift it.

Nothing happens until you set it up either: with no API key the channel stays off, the session is unaffected, and the plugin's tools work as before.

It needs Node.js 20 or newer on PATH — Claude Code installed as a standalone binary does not bring one. Without it the channel never starts, and the only evidence is a spawn error in the session's own MCP log, so check node --version first.

Shortened. The full README is on GitHub.