Docs·MCP Server
MCP Server
MailBridge speaks the Model Context Protocol. Point Claude Desktop, Cursor, or any MCP-compatible client at your workspace and it can read conversations, search your knowledge base, and — with your explicit confirmation — reply to customers directly.
Overview
The MCP server exposes a single streamable-HTTP endpoint. Every tool call runs against your own workspace's data — conversations, contacts, and knowledge base — scoped to the API key you connect with. There's no separate MCP-specific setup: if you can generate an API key, you can connect an MCP client.
Connect a client
Generate an API key from Developer Tools → API Keys, then add MailBridge as an MCP server. Most clients (Claude Desktop, Cursor) accept a remote streamable-HTTP server config like this:
{ "mcpServers": { "mailbridge": { "type": "http", "url": "https://api.usemailbridge.com/api/mcp", "headers": { "Authorization": "Bearer mb_live_xxxxxxxxxxxxxxxxxxxx" } } } }
Authentication
The MCP endpoint uses the same Bearer token auth as the REST API — generate a key under Developer Tools → API Keys and pass it as an Authorization header. Every tool call is scoped to that key's organisation — there is no cross-workspace access.
Authorization: Bearer mb_live_xxxxxxxxxxxxxxxxxxxx
Available tools
Read tools require no confirmation. Write tools marked confirm first are customer-facing or hard to undo — well-behaved clients ask before calling them.
Read
list_conversationsList support conversations, optionally filtered by status, category, priority, or search text.
get_conversationGet a single conversation by ID, including its full message thread and notes.
list_contactsList customer contacts derived from conversation senders, with conversation counts.
get_contact_conversationsList all conversations from a specific contact's email address.
search_knowledge_baseSearch the team's knowledge base for articles relevant to a query.
get_analytics_overviewGet a summary of support activity — volume, categories, sentiment, priority — over a recent window.
Write
reply_to_conversationconfirm firstSends a real, customer-facing email reply. Cannot be unsent — only call after explicit confirmation of the exact text.
add_conversation_noteAdd an internal note to a conversation. Never visible to the customer.
update_conversation_statusChange a conversation's status. Internal state only — does not notify the customer.
escalate_conversationEscalate a conversation internally (e.g. to Slack/Discord) with a reason.
create_knowledge_base_documentCreate a new knowledge base article. Queued for indexing, searchable shortly after.
update_knowledge_base_documentconfirm firstEdit an existing article's title and/or content — directly changes what the AI and chat widget see as truth.
archive_knowledge_base_documentconfirm firstArchive (soft-delete) a document. Removed from search and the widget, reversible from the dashboard.