Appearance

MCP surface map ​

MyChatBot exposes four MCP surfaces. Choose the narrowest one that matches the job: use the Agents MCP to configure and test the Agents Platform, Sales-Management to operate account-scoped sales resources, Product to search one catalog, and UGC for social content and analytics.

For non-trivial systems, Claude or Codex uses these surfaces as the configuration and prototyping plane. A validated routine then runs on MyChatBot as the production orchestration plane. External MCP access configures the system; runtime routine steps use the connectors and tools enabled on their executing agents. See the routine-first operating model.

Choose a surface ​

GoalMCP surfaceScopeWhere to get the setup
Build agents, skills, knowledge, connectors, routines, schedules, and triggersAgents MCPOne account, derived from its Bearer access keyAny Agent → Tasks → Connect Claude or Codex
Read or manage sales assistants, clients, chats, channels, outreach, knowledge, orders, calendar, and related areasSales-Management MCPOne account plus an optional areaAgents → Connectors → a From your sales platform card → Connect AI tools
Search products in one catalogProduct MCPOne connected product catalogKnowledge Base → Products card → Connect AI tools
Generate social content or use posting, analytics, and ads toolsUGC MCPOne business and an optional areaUse the per-account UGC setup

Common paths ​

Build and test a routine ​

Connect the Agents MCP, then ask Claude or Codex to call get_routine_authoring_context before it drafts. The context links the canonical raw Markdown references and exposes the current YAML contract. Follow Build routines with Claude or Codex for inventory, validation, bounded preview, and separately staged automation.

Work with Sales Platform data ​

Connect one Sales-Management area when possible so the client sees a focused tool list. Use the combined surface only when one workflow genuinely crosses several areas. Start at Sales tools by domain, then open the full parameter reference for exact inputs and result shapes.

Use Sales-Management to configure and test Sales primitives during the Claude/Codex session. In the promoted routine, give the executing agent the narrow Sales Platform connector or tool it needs. Native Sales events do not trigger Agents routines today; use a scheduled polling routine for Sales-only feedback loops.

For outreach authoring, use the focused sales_outreach area and follow the two distinct safety paths in Build outreach with Claude or Codex: postponed sequences are staged as drafts and published separately, while creating an immediate campaign schedules real customer contact.

Give an agent an external MCP server ​

That is a custom connector, not one of the account administration surfaces above. Add its URL under Agents → Connectors, authorize it once for the account, and enable it only on the agents that need it. See Connectors.

Security boundaries ​

  • Treat Product MCP URLs and every Bearer key as credentials. Do not paste them into routine YAML, skills, documentation, screenshots, source control, or chat transcripts.
  • An Agents MCP key determines the account; its tools do not accept an account_id that a model can change.
  • A Sales-Management URL contains account and area selectors, but its Bearer key still authorizes the request. The URL alone is not authorization.
  • Prefer one area and least privilege. Revoke or rotate access that is no longer needed.
  • Read tools may contact real systems. Write tools and billed previews require explicit review in the client; enabling a schedule or trigger is a separate action.

Complete machine-readable reference ​

The full setup, server addresses, client snippets, tool inventory, dry-run semantics, and security details remain in MCP & connectors. Agent clients can read it directly at https://docs.mychatbot.app/agents/mcp-and-connectors.md.

See also ​

Copyright © 2023–2026 MyChatBot