Appearance
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:
- 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.
- 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 to | Use | Set it up |
|---|---|---|
| Set up and run the whole account from Claude Code or Codex, with guided workflows | MyChatBot plugin: one connection to the Sales, Agents, content, and Docs tools, signed in through the browser | Install the plugin; no key to copy |
| Build a sales assistant in a chat in the Claude app, no terminal | MyChatBot connector for the Claude app | Add MyChatBot from Claude's directory |
| Manage sales assistants, leads, chats, channels, outreach, knowledge, integrations, orders, calendar, and automations from any AI tool | Sales Platform MCP (Sales-Management MCP), whole or one area at a time | Agents → Connectors → a From your sales platform card → Connect AI tools |
| Search one product catalog | Product search MCP | Knowledge → a product source → Tools → Connect AI tools |
| Build agents, skills, knowledge, connectors, and routines | Agents MCP | Any agent → Tasks → Connect Claude or Codex |
| Generate media, post, and read social analytics and ads | Content (UGC) MCP | The account access key |
| Search and read these docs | Docs MCP | Public; 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. Where to start for common jobs:
| You want to | Start here |
|---|---|
| Change part of a long instruction or skill, or bring back an earlier version | Edit long instructions and skills safely |
| Change hand-off settings, Work Hours, control numbers, or live notes | Assistant settings, hours, and Flight Control |
| Hand a chat to a person or back to the AI, give stuck chats back in bulk, or check a channel's health | Chats, AI mode, and channel health |
| Connect a CRM, Google Calendar, Spreadsheet Orders, or a Custom MCP server | Connecting integrations |
| Set up the built-in Calendar's staff, services, and hours | Setting up the built-in Calendar |
| Pause an automation, or set up triggers and the Keyword Responder | Setting up automations |
| Run a campaign or follow-ups | Build and operate outreach with Claude or Codex |
| Test an assistant before customers see it | Testing & evals |
| Understand an error, or what MyChatBot support can change for you | Errors and refusals, Who can use which tool |
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 server | What to add | Where |
|---|---|---|
| A customer-facing Sales assistant | A Custom MCP integration: the server's address, and headers or a sign-in if the server asks for one | Integrations → pick the assistant → MCP Providers → Custom MCP |
| An agent on the Agents Platform | A 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: Bearerheader. 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.
- Integration API keys, header values, and sign-ins are never passed to a tool: you enter them in the dashboard, on the page the tools link you to. See Keys and sign-ins stay in the dashboard.
- No MCP tool creates an account or hands one over. An account is made when you sign up in the app, or in the browser window the Claude connector or the plugin opens.
- The Docs MCP is public and read-only: it reads only
docs.mychatbot.appand 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
- MyChatBot plugin for Claude Code and Codex — install, sign in, and the full tool inventory
- Sales Platform MCP — addresses, areas, and client setup for the Sales tools
- Agents MCP & connectors — build agents and routines from Claude or Codex
- Custom MCP — give a Sales assistant your own server
- Connectors — give an agent external apps or your own server
