Skip to content

MCP at MyChatBot ​

MCP (Model Context Protocol) is how AI tools such as Claude, Codex, and Cursor call outside tools. MyChatBot uses it in two directions:

  1. Your AI tool works on your MyChatBot account. You connect Claude, Codex, Cursor, or your own client to one of MyChatBot's own servers, and it reads or changes your assistants, leads, catalogs, agents, or content. See MyChatBot's own servers.
  2. Your assistants and agents use someone else's server. You give a Sales assistant or an agent a server you or a vendor host, so it can call those tools while it works. See Connect another MCP server.

MyChatBot's own servers ​

You want toUseSet it up
Set up and run the whole account from Claude Code or Codex, with guided workflowsMyChatBot plugin: one connection to the Sales, Agents, content, and Docs tools, signed in through the browserInstall the plugin; no key to copy
Build a sales assistant in a chat in the Claude app, no terminalMyChatBot connector for the Claude appAdd MyChatBot from Claude's directory
Manage sales assistants, leads, chats, channels, outreach, knowledge, orders, calendar, and automations from any AI toolSales Platform MCP (Sales-Management MCP), whole or one area at a timeAgents → Connectors → a From your sales platform card → Connect AI tools
Search one product catalogProduct search MCPKnowledge Base → a product catalog card → Connect AI tools
Build agents, skills, knowledge, connectors, and routinesAgents MCPAny agent → Tasks → Connect Claude or Codex
Generate media, post, and read social analytics and adsContent (UGC) MCPThe account access key
Search and read these docsDocs MCPPublic; no key

Besides the plugin and the Claude connector, MyChatBot exposes five MCP surfaces you connect to directly: the Agents MCP, the Sales-Management MCP, the Product MCP, the UGC MCP, and the public, read-only Docs MCP. Choose the narrowest one that matches the job.

For Sales work, start with Sales tools by domain and open the Sales tools reference for exact parameters. Two how-tos cover the most common changes: Edit long instructions and skills safely and Assistant settings, hours, and Flight Control. For campaigns, follow Build and operate outreach with Claude or Codex.

For Agents work, connect the Agents MCP and ask Claude or Codex to call get_routine_authoring_context before it drafts, then follow Build routines with Claude or Codex. Claude or Codex is where you configure and try things; a validated routine then runs inside MyChatBot on its own. See the Agents Platform operating model.

Connect another MCP server ​

Who uses the serverWhat to addWhere
A customer-facing Sales assistantA Custom MCP integration: the server's address, and headers or a sign-in if the server asks for oneIntegrations → pick the assistant → MCP Providers → Custom MCP
An agent on the Agents PlatformA custom connector, or one of the external apps (HubSpot, Gmail, Slack, Notion, Stripe, and more)Agents → Connectors — see Connectors

A custom server is a different thing from MyChatBot's own servers above: those let your AI tool reach MyChatBot; a custom server lets MyChatBot reach your tools.

Keys and safety ​

  • The plugin and the Claude connector sign you in through the browser. The Sales, Agents, and Content servers take the account's access key in an Authorization: Bearer header. Only the account owner or an Admin can create these keys and see them listed, and a key reaches the whole account. To revoke a key, contact support.
  • Treat every access key and every Product MCP address as a credential. Don't paste them into routine YAML, skills, documents, screenshots, source control, or chat transcripts. Ask support to revoke a key you no longer need or that was exposed.
  • The account in a Sales-Management address selects the account and area; it never authorizes a request on its own. Only the access key does.
  • The Docs MCP is public and read-only: it reads only docs.mychatbot.app and can't reach an account.
  • Read tools may contact real systems. Changes, messages, calls, deletions, and billed previews deserve a deliberate review in your AI tool; switching on a schedule or trigger is a separate step.

See also ​