Ecbot MCP Server

The Ecbot MCP Server lets an AI assistant such as Claude Code, Codex or Cursor work in your workspace. Connect it with an API key, then ask in plain words: "list the chats that need me", "add our new return policy to the knowledge base" or "tag this customer VIP". The assistant can do what the key's creator can do in the app.

Create an API keyCopy Anchor Link

The workspace owner and members with the built-in Admin role can create API keys. Custom roles can't. Open the workspace menu at the top of the sidebar, choose Settings (members choose the workspace name), then open API key:

1

2

1. 1API key in the settings sidebar lists every key in the workspace.
2. 2Create makes a new key.

Choose Create, give the key a name such as "Claude Code", and choose Create again. The new key appears once:

1

2

1. 1The secret is shown only this once. If you lose it, rotate the secret or create a new key.
2. 2Copy the whole value under x-api-key. This is the key your assistant sends.

If a key leaks, open its menu (...) and choose Rotate secret: the old secret stops working right away. Delete revokes the key for good.

Connect your assistantCopy Anchor Link

The server address is https://mcp.ecbot.dev/mcp. Your assistant sends the key with every request, as an x-api-key header or as a bearer token. Replace YOUR_KEY below with the value you copied.

Claude CodeCopy Anchor Link

claude mcp add --transport http --scope user ecbot https://mcp.ecbot.dev/mcp \
  --header "x-api-key: YOUR_KEY"

CodexCopy Anchor Link

export ECBOT_API_KEY="YOUR_KEY"
codex mcp add ecbot --url https://mcp.ecbot.dev/mcp \
  --bearer-token-env-var ECBOT_API_KEY

Cursor and other clientsCopy Anchor Link

Clients set up with a JSON file, such as Cursor's mcp.json, take the address and a header:

{
  "mcpServers": {
    "ecbot": {
      "url": "https://mcp.ecbot.dev/mcp",
      "headers": { "x-api-key": "YOUR_KEY" }
    }
  }
}

Keep a file that holds your key out of shared folders and code repositories.

What the assistant can doCopy Anchor Link

Uploading files, installing marketplace apps and permanently erasing a customer's data are only available in the app.

Build skills with your assistantCopy Anchor Link

The assistant can write a skill as steps, with branches, your tools and the built-in actions: hand off to staff, notify the team, add or remove a tag, schedule a follow-up and save customer info. Describe the procedure in plain words, for example:

Create a skill "Order status" for when a customer asks where their order is. Ask for the order code and call my Order lookup tool. If the order is late, say sorry and hand off to staff. Otherwise tell them the delivery date. Attach it to my shop agent.

The assistant can look up your tools and tags first, so the steps point at real ones. Open the skill in the app afterwards to check it. More prompts are in the cookbook.

Add Ecbot skills to your assistantCopy Anchor Link

Ecbot publishes skills that teach your assistant how to work in your workspace. Install them next to the server, and pick the ones you want:

npx skills add blackmouse572/ecbot

• ecbot: the safety rules, such as asking before a reply reaches a customer, and where each kind of setting belongs.
• ecbot-agent-builder: sets up an agent, or cleans one up. It keeps Extra instructions to tone and a few rules, moves facts to knowledge, and turns each workflow into a skill.
• ecbot-skill-builder: turns a requirement into a skill written as steps, the way the tutorial does.

Permissions and the activity logCopy Anchor Link

• The key acts as its creator. It always has the creator's current permissions: if they lose a permission or leave the workspace, the key loses it too.
• The assistant sees only the tools the key may use, so it does not try actions that would be refused.
• Every change is logged. Changes and replies show in Activity under the creator's name, as if they made them in the app. Opening a chat or a customer is logged as a view, the same way.
• Customer text is data, not instructions. Messages from customers and the text of your documents can say anything, so the server tells the assistant never to follow instructions found in them.