Model Context Protocol
Outbound OS exposes an MCP server for Claude and other MCP-capable clients. Ask about live leads, inspect a customer timeline, prepare a follow-up, create a draft campaign or pull current analytics without exporting the workspace first.
What it looks like
The assistant is not guessing from a summary you pasted in. It calls the same tools the dashboard uses, against the live workspace, with the permissions of the account that connected it.
Nothing sends on its own. Drafts stay drafts until a person approves them — the same rule the rest of the product follows.
What it unlocks
The useful part is not chatting about a CRM. It is letting the client call explicit tools against the workspace and show what it used.
“Which open deals went quiet this week?”
The client can list relevant leads, open their timelines and compare current status with recent activity. The answer comes from CRM records rather than a spreadsheet copied yesterday.
list_leads · get_lead · lead_timeline“Draft the next follow-up for unanswered quotes.”
The client can inspect conversation history, request a reply suggestion and prepare a campaign in draft. A person can review the recipients, wording and channel before starting it.
list_messages · ai_reply_suggestion · create_campaign“Pause automated sending and show me sender health.”
An approved client can stop the automated queue, inspect WhatsApp sender readiness and see the current system state. That is a real write operation, not a recommendation in chat.
system_pause_resume · whatsapp_accounts · system_statusTool coverage
List, search, inspect, create, update, assign, change status and work with lead timelines.
Read WhatsApp and email history, request a suggested reply and send through connected accounts.
Create and edit drafts, preview matching leads, start or pause campaigns and inspect results.
Pull current overview, funnel, campaign and email-performance data held by the product.
Inspect sending and account state, list team members, and pause or resume automated sending.
Use Claude or another client that supports remote MCP servers.
The endpoint is not public. The connection uses an approved credential that should be protected like product access.
Read tools and write tools have different consequences. Configure confirmation behavior before using send, campaign or destructive actions.
Ask the client to show the records and tool calls behind its answer, especially before a message or campaign changes state.
Connection model
MCP lowers the distance between a question and the CRM action. It does not remove the responsibility to control who can connect, which tools can run and what requires confirmation.
Where the line is
Price, scope, terms and relationship context still need a reliable source in the CRM or an explicit person in the loop.
Some tools send immediately or change campaign state. Client approval settings and credential control matter.
The same provider rules apply whether a person clicked the action or an approved MCP client called the tool.
Bring the task you would give an assistant and the approval boundary your team needs.