MCP Server

Work on your agent from the AI apps you already use. Once connected, you can tell Claude, ChatGPT, Codex or Cursor things like "add our shipping times to the shop agent and check what it answers now", and it does it: reads the knowledge base, adds what is missing, rewrites the instructions, sets up proactive messages and tests the answer right after.

MCP (Model Context Protocol) is the open standard these apps use to talk to other services. BitPalm runs an MCP server, your app connects to it and you sign in with your BitPalm account.

Server address: https://agents.bitpalm.ai/api/mcp

How it works

1. You add BitPalm in your AI app with the server address above.
2. The app opens a BitPalm page in your browser. You sign in, if you aren't already, and decide what the app may do: read and change, or read only.
3. You land back in the app, connected. No key to copy anywhere.

You can see every connected app under Settings in the BitPalm dashboard and disconnect it with one click. It loses access right away.

Which app works how

Claude

1. In Claude open Customize → Connectors and click Add custom connector.
2. Name: BitPalm. Server URL: https://agents.bitpalm.ai/api/mcp
3. Click Add, then Connect. Sign in with BitPalm and allow access.
4. In a chat click + → Connectors and switch BitPalm on.

On Team and Enterprise plans an owner adds the connector once under Organization settings → Connectors → Add → Custom. After that everyone connects with their own BitPalm account, so each person only reaches their own agents.

ChatGPT

ChatGPT connects custom MCP servers in developer mode. That needs a paid plan (Plus, Pro, Business, Enterprise or Edu) and works on the web for now.

1. In ChatGPT open Settings → Security and login and switch on Developer mode.
2. Create a new app with the + button in the apps area. Name: BitPalm. Server URL: https://agents.bitpalm.ai/api/mcp. If ChatGPT asks for the authentication, pick OAuth.
3. Sign in with BitPalm and allow access.
4. In a chat, BitPalm is now available with the developer tools.

OpenAI renames these menus now and then. If a label looks different, the steps stay the same: developer mode on, new app with the server URL, OAuth.

Claude Code

Run this once in your terminal:

claude mcp add --transport http --scope user bitpalm https://agents.bitpalm.ai/api/mcp

Then type /mcp inside Claude Code, pick bitpalm and choose to authenticate. Your browser opens, you sign in with BitPalm, done.

• --transport http tells Claude Code that BitPalm is a server on the internet, not a program on your computer.
• --scope user makes BitPalm available in all your projects. Leave it out to add it to the current project only.

Cursor

Add this to ~/.cursor/mcp.json, or open Cursor Settings → Tools & MCP and add a new server there:

{
  "mcpServers": {
    "bitpalm": {
      "url": "https://agents.bitpalm.ai/api/mcp"
    }
  }
}

The first time Cursor needs BitPalm, it opens your browser to sign in.

Codex

codex mcp add bitpalm --url https://agents.bitpalm.ai/api/mcp
codex mcp login bitpalm

The second command opens your browser to sign in with BitPalm. Codex keeps the sign-in, and the Codex extension for VS Code and Cursor uses the same setup.

API keys

For everything that can't sign in through a browser, such as scripts, n8n, Zapier or a CI job, use an API key instead.

1. In the dashboard go to Settings → API keys and click Create key. Tick Read only if the script should never change anything.
2. Copy the key. It starts with bp_live_ and is shown only once.
3. Send it with every request in one of these headers:
   • Authorization: Bearer bp_live_YOUR_KEY
   • x-api-key: bp_live_YOUR_KEY

The apps above take a key too, if you prefer that over the sign-in:

claude mcp add --transport http bitpalm https://agents.bitpalm.ai/api/mcp \
  --header "Authorization: Bearer bp_live_YOUR_KEY"

export BITPALM_API_KEY="bp_live_YOUR_KEY"
codex mcp add bitpalm --url https://agents.bitpalm.ai/api/mcp --bearer-token-env-var BITPALM_API_KEY

For Cursor, add "headers": { "Authorization": "Bearer bp_live_YOUR_KEY" } next to the url.

First things to ask

• "Which agents do I have on BitPalm? Show me the instructions of the shop agent."
• "Add our shipping times as knowledge to the shop agent, then ask it when an order arrives."
• "Which questions would go to the pricing specialist? Test five typical ones with route_question."
• "Add a proactive message on /pricing after 20 seconds that offers help with choosing a plan."
• "Run the agent check on the shop agent, then fix whatever it finds and ask it again."
• "Add three quick links under the greeting: prices, delivery times and contact, in German and English."

What the tools can do

Agents

Knowledge. Every knowledge tool takes an optional specialist id, then it works on that specialist's knowledge.

Quick links and triggers

Specialists and corrections

Tools and API endpoints. Keys and tokens are only entered in the dashboard, so they never go through an AI chat. Claude says where to enter them.

Testing and numbers

New system prompts switch the agent into expert mode, so the behavior form stops writing over them.

Good to know

• Read only means read only. An app or key without write access never sees the tools that change things, so the AI can't even try.
• Your account only. A connection or key reaches the agents of the account it belongs to, nothing else.
• Audit trail. Every change through MCP lands in the agent's audit log, marked as MCP together with the app's name.
• Keys stay in the dashboard. Tool keys and endpoint keys can't be set or read through MCP.
• No visitor data. Conversations, visitors and leads are not readable here. Numbers, yes. Content, no.
• Limit. 120 requests per minute per connection or key.
• Disconnecting works right away. Remove an app under Settings, or revoke a key, and everything running with it stops.

For developers

The server follows the MCP authorization spec, so any spec-compliant client finds its way on its own:

• Protected resource metadata: https://agents.bitpalm.ai/.well-known/oauth-protected-resource/api/mcp
• Authorization server metadata: https://agents.bitpalm.ai/.well-known/oauth-authorization-server
• Dynamic client registration (RFC 7591), authorization code flow with PKCE (S256 only), refresh tokens that rotate on every use, token revocation (RFC 7009)
• Scopes: read and write. Access tokens last an hour, refresh tokens 60 days.
• A request without credentials gets 401 with WWW-Authenticate: Bearer resource_metadata="…"

When something doesn't work

A tool that can't do what was asked answers with a normal result that explains why, so the AI can correct itself instead of giving up.