MCP Server

What you can do with it

Once connected, you can talk to your MotherBot account in plain language. Some things people actually ask for:

• “How many messages did we send last week, and what was the delivery rate?”
• “Find the contact for +91 94065 37037 and tell me what we last said to them.”
• “Which of my approved templates are for order updates?”
• “Add Asha Kulkarni as a contact and tag her as a wholesale lead.”
• “Build me a chatbot that asks for an order number and looks it up in Shopify.”
• “Create a workflow that waits an hour after a cart is abandoned, then messages the customer.”

The assistant only ever sees your account — the one the API key belongs to. Everything it returns is already scoped to your organisation.

What it deliberately cannot do

The tool list is read-heavy with safe writes. 34 of the 41 tools only read. The writes it does have change one record at a time: send one message, create or edit one contact, build one automation.

For the same reason, workflows and chatbots are always created switched off. An assistant can build one for you in seconds; you review it in the builder and turn it on yourself. Activating one re-validates the whole thing first, so a half-finished automation can never go live.

Before you start

Connect Claude Desktop

Open Settings → Connectors → Add custom connector, and give it the URL below. Claude will ask for the key.

https://motherbot.io/api/mcp

If your version of Claude Desktop uses a config file instead, add this to claude_desktop_config.json and restart the app. On macOS the file is at ~/Library/Application Support/Claude/; on Windows, %APPDATA%\Claude\.

{
  "mcpServers": {
    "motherbot": {
      "url": "https://motherbot.io/api/mcp",
      "headers": {
        "Authorization": "Bearer motherbot_your_key_here"
      }
    }
  }
}

Connect Claude Code

One command, from any project directory:

claude mcp add --transport http motherbot https://motherbot.io/api/mcp \
  --header "Authorization: Bearer motherbot_your_key_here"

Add --scope user to make it available in every project rather than just this one. Check it worked with /mcp.

Connect Cursor

Settings → Cursor Settings → MCP → Add new global MCP server, or create .cursor/mcp.json in your project:

{
  "mcpServers": {
    "motherbot": {
      "url": "https://motherbot.io/api/mcp",
      "headers": {
        "Authorization": "Bearer motherbot_your_key_here"
      }
    }
  }
}

A project-level .cursor/mcp.json is committed to your repository, so put the key in a global config instead unless your repository is private and you are comfortable with that.

Connect VS Code (GitHub Copilot)

Create .vscode/mcp.json. VS Code can prompt for the key rather than storing it in the file:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "motherbot-key",
      "description": "MotherBot API key",
      "password": true
    }
  ],
  "servers": {
    "motherbot": {
      "type": "http",
      "url": "https://motherbot.io/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:motherbot-key}"
      }
    }
  }
}

Open Copilot Chat, switch to Agent mode, and the MotherBot tools appear in the tool picker.

Connect Windsurf, Zed and other clients

Any client that speaks MCP over HTTP works. The two things it needs are the URL and an Authorization header.

{
  "mcpServers": {
    "motherbot": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://motherbot.io/api/mcp",
        "--header", "Authorization: Bearer motherbot_your_key_here"
      ]
    }
  }
}

Check it works

If a client will not connect and does not say why, ask the server directly. This is the handshake every client sends first:

curl -sS -X POST https://motherbot.io/api/mcp \
  -H "Authorization: Bearer motherbot_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0", "id": 1, "method": "initialize",
    "params": { "protocolVersion": "2025-11-25", "capabilities": {} }
  }'

A working key answers with the server's capabilities. To see the tools your key allows:

curl -sS -X POST https://motherbot.io/api/mcp \
  -H "Authorization: Bearer motherbot_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{ "jsonrpc": "2.0", "id": 2, "method": "tools/list" }'

Scopes and what each one unlocks

A tool only appears if your key holds the scope its endpoint needs. Keys created before scopes existed hold all of them.

Every tool

41 tools. Your key sees the ones its scopes allow — the rest are neither listed nor callable.

Building automations with an assistant

Workflows and chatbots have their own vocabulary — specific trigger keys, step types and node types. An assistant cannot guess them, so it should ask first:

• get_workflow_catalogue — every trigger and step a workflow can use. Pass step= or trigger= to get the full field list for the ones it intends to use.
• get_chatbot_catalogue — every chatbot node type, the trigger types, and the rules a flow has to satisfy.

Good assistants do this on their own — the server tells them to. If one invents a step type anyway, the refusal names the problem and points at the catalogue, and nothing is saved.

Security

• Your key is your boundary. The server acts only on the account the key belongs to, and only within its scopes and channel restrictions. Every single call is checked — not just the first one.
• Scopes are enforced twice. Tools outside your scopes are not offered, and are refused if called anyway.
• Nothing goes live on its own. Workflows and chatbots are created switched off; activating one re-validates it in full.
• Everything is rate limited — the same per-minute allowance your plan gives the REST API.
• Calls are attributed. Requests from MCP are tagged, so you can tell an assistant's activity from a script's.

For developers

The server is stateless: every request carries its own credential and is answered on its own, so there is no session to keep alive and no sticky routing needed in front of it. Each tool is one endpoint of the public REST API — same parameters, same responses, same limits.