Octocom MCP

Octocom exposes its API as an MCP (Model Context Protocol) server. Once connected, an AI agent can manage almost every aspect of your Octocom workspace on your behalf — from inspecting why a bot replied a certain way to writing new Python actions.

MCP is currently in private beta. Access is enabled per-organization as we roll out. If you'd like early access, reach out to us and we'll enable it for your workspace.

What you can do with the Octocom MCP

The best way to discover what's possible is to ask your agent itself: "What Octocom tools do you have and what can you do with them?" The agent will introspect its available tools and give you an up-to-date overview.

Popular use cases include:

• Deeply debug bot responses. The agent can pull the exact system prompt the bot saw on any past response and the full sequence of tool calls it made — then trace which rule, workflow, article, or action drove the behavior, and fix it.
• Drive test conversations against your bot. The agent can literally chat with your Octocom bot through MCP, send messages, read replies, then iterate on the configuration in a tight loop — like an automated QA engineer.
• Operate on real customer conversations. List and read conversations, inspect transcripts, tag them, close them, or hand them off to humans.
• Manage every part of the bot's configuration:
  • Bot rules — the policies that guide responses, with full version history and rollback
  • Workflows — multi-step playbooks for handling specific situations, with variants
  • Articles & documents — the knowledge base, with versioning, soft-delete and restore
  • Macros & folders — canned responses for human agents
  • Tags — for routing, reporting, and conversation triage
  • Data collection prompts — structured intake of customer info (email, order number, etc.)
  • Global bot config — model, tone, safety settings, and more
• Write custom code on your behalf, and test it before deploying:
  • Python actions — let the bot do anything Python can do
  • API actions — call any external API as a bot action
  • Condition providers — Python-based gates that decide when workflows/rules apply
  • Event handlers — Python listeners that react to bot/conversation events
  • Sidebar widgets — Python-rendered widgets for the agent UI
  • Every one of these has a matching test_* tool, so the agent can validate its code with real inputs before you push it live.
• Configure social media response automation — comment workflows that handle Instagram/Facebook comments and DMs, including testing them against sample comments.
• Configure the review-response bot — Trustpilot, Okendo, and Google review workflows, including simulating an incoming review end-to-end and inspecting workflow runs.
• Build and run AI-generated product catalog parsers. Hand the agent any product feed (XML/JSON/CSV) and have it write a Python parser that maps it into Octocom's product catalog — sample the feed, write the parser, run it, inspect the execution, iterate. Useful for stores not on a directly-supported platform.
• Search and inspect your product catalog directly from your agent.
• Use the dashboard's docs as a reference. The MCP exposes Octocom's own documentation as tools, so the agent can pull up the right page when it doesn't know how something works — no Octocom expertise required on your end.

The real superpower: combining tools at scale

The individual tools are useful, but the leverage shows up when you combine them with what AI is already great at — reading large dumps of unstructured input, writing and testing code, and driving repeated test conversations. A few examples of what this looks like in practice:

• "Configure this, then stress-test it." Ask the agent to set up a workflow, action, or rule, then run 20 test conversations against it with varied scenarios, summarize where it broke, and iterate.
• "Here's a CSV of feedback — fix the bot." Drop a CSV (or spreadsheet) of conversation IDs and human comments. The agent reads each conversation, correlates the feedback, and proposes/applies targeted changes — rule by rule, article by article.
• "Here are 100 sample customer comments — evaluate the social media workflow." Hand the agent a batch of real comments. It runs each one through your comment workflow (or data collection prompt), writes the responses back to a CSV, and analyzes overall quality, edge cases, and failure modes.
• "Build me an integration." Describe an external system. The agent writes a Python action, tests it with realistic inputs, wires it into a workflow, then runs end-to-end test conversations to confirm it all works.

In short: it's not just that you can do individual things through MCP — it's that you can finally do them at scale, with the same agent doing the analyzing, the coding, the configuring, and the testing in one loop.

We keep evolving the MCP and our goal is that you can do everything through MCP — eventually going beyond what's possible in the dashboard.

You're responsible for what the agent does

When you connect an AI agent to Octocom via MCP, that agent acts on your behalf with your permissions. The person driving the agent is responsible for everything it does — including misconfigured bots, deleted or broken workflows, unintended messages sent to real customers, and large conversation counts run up by automated testing. Octocom does not take responsibility for these outcomes.

That said, we work hard to make the MCP safer to use:

• Read-only mode (see below) lets you use the MCP without any risk of mutations.
• Version history and soft-delete on most configuration entities (workflows, articles, bot rules, etc.), so it's almost always possible to revert a bad change.
• Tool design is biased toward clarity and safety — descriptive names, explicit test_* companions to mutating tools, and unambiguous arguments so the LLM is unlikely to do something it didn't mean to.
• Rate limiting to prevent runaway loops and unbounded tool-call sprees.
• Audit logging of every MCP tool call.

These are guardrails, not guarantees. The agent can still make wrong choices, and an unattended agent can still cause real damage. Treat MCP like a powerful intern with full keyboard access: review what it proposes before merging, supervise it during meaningful changes, and reach for read-only mode whenever you don't need write access.

Read-only mode

Octocom MCP exposes two endpoints:

Read-only mode is useful when you want the agent to analyze, audit, or explain your Octocom setup without any risk of accidental mutations — for example:

• A first-time exploration where you just want the agent to describe what's configured
• Letting a teammate connect their own AI agent for inspection only
• Running scripted audits, reports, or one-off analyses
• Pairing with another MCP server (e.g. your data warehouse) where Octocom is purely a source of context

Connect to the read-only endpoint the same way as the regular one — just use the ?readonly=true URL when adding the custom connector. The OAuth flow is identical.

You can also have both endpoints connected at once in the same client (e.g. as Octocom (read-only) and Octocom), and decide per-conversation which one to use.

Connect from Claude (chat, Cowork, or Desktop)

Anthropic calls this a custom connector using remote MCP, and the same connector configuration works across the Claude chat (claude.ai), Claude Cowork, and Claude Desktop — connect once and it's available everywhere you use Claude on that account. It's supported on Free, Pro, Max, Team, and Enterprise plans (the setup steps differ slightly between individual and Team/Enterprise plans — see below).

These instructions are valid as of May 20th, 2026. The Claude app is updated frequently — if the buttons described below no longer exist, search Anthropic's support docs for how to add a custom MCP connector. The latest reference is Get started with custom connectors using remote MCP.

Pro and Max plans (individual)

1. Navigate to Customize > Connectors.
2. Click "+", then "Add custom connector".
3. Enter the MCP server URL: https://api.octocom.ai/mcp
4. Set the name to Octocom.
5. Click Add.

You don't need to touch Advanced settings — leave the OAuth Client ID and Secret fields empty.

Once added, click Connect. You'll be redirected to the Octocom dashboard to grant the MCP access to your account, and then back to Claude.

Team and Enterprise plans

On Team and Enterprise, custom connectors must first be configured at the organization level by an Owner or Primary Owner. After that, individual members can connect.

Step 1 — Owner adds the connector (one-time setup):

1. Navigate to Organization settings > Connectors.
2. Click Add.
3. Hover over Custom, then select Web.
4. Enter the MCP server URL: https://api.octocom.ai/mcp
5. Set the name to Octocom.
6. Click Add.

You don't need to touch Advanced settings — leave the OAuth Client ID and Secret fields empty.

Step 2 — Each member connects:

1. Navigate to Customize > Connectors.
2. Find the Octocom connector in the list (it will have a Custom label).
3. Click Connect to authenticate. You'll be redirected to the Octocom dashboard to grant access, and then back to Claude.

Connect from Claude Code

Add Octocom to your project's .mcp.json (or your user-level Claude Code config):

{
  "mcpServers": {
    "octocom": {
      "type": "http",
      "url": "https://api.octocom.ai/mcp"
    }
  }
}

The first time Claude Code calls an Octocom tool, it will open a browser window for you to authenticate with the Octocom dashboard. After that, the OAuth tokens are cached and the connection stays live.

Connect from other MCP clients

Any MCP client that supports remote HTTP MCP servers with OAuth can connect to Octocom. The general steps are:

1. Add a new remote/HTTP MCP server in your client's configuration.
2. Use the URL https://api.octocom.ai/mcp.
3. Leave any OAuth Client ID / Client Secret fields empty — the server handles OAuth dynamic client registration automatically.
4. Trigger the connection. The client will open the Octocom dashboard in your browser to authenticate, then return you to the client with the connection ready.

If your client doesn't support remote MCP servers directly, you can usually bridge to it using mcp-remote:

npx -y mcp-remote https://api.octocom.ai/mcp

Refer to your MCP client's documentation for the exact configuration format.