Connect Claude to Booked55

Follow these steps to connect Claude Desktop or Claude.ai to Booked55 via the MCP server. Once connected you can manage contacts, companies, pipelines, tasks, and events using natural language.

Method 1 — Custom Connectors (Recommended)

Claude Desktop supports remote MCP servers through its built-in Connectors UI — no config file editing required. Booked55 authenticates via OAuth when you first use a CRM tool.

Open Claude Desktop.
Go to Settings → Connectors (sometimes labelled MCP).
Click Add custom connector.
Enter the MCP server URL: https://mcp.booked55.com
Expand Advanced settings and enter the OAuth Client ID b55_a6e0faeeedc74d50c5d9fec98bf9a75c and the client secret you received from us — both fields are required.
Complete OAuth authorization when prompted — sign in with your Booked55 credentials and click Authorise.
The connector appears in your connectors list when ready. Start a new conversation and confirm the tools are available.

Method 2 — mcp-remote Config File

Claude Desktop's config file only supports stdio MCP servers — not direct url fields. To connect a remote server via the config file, use the mcp-remote bridge:

Open Claude Desktop → Settings → Developer → Edit Config to open claude_desktop_config.json.
Add the Booked55 entry using npx mcp-remote:

{
  "mcpServers": {
    "booked55": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://mcp.booked55.com",
        "--static-oauth-client-info", "{ \"client_id\": \"b55_a6e0faeeedc74d50c5d9fec98bf9a75c\", \"client_secret\": \"YOUR_CLIENT_SECRET\" }"
      ]
    }
  }
}

The --static-oauth-client-info argument is required — without it mcp-remote tries to register an OAuth client automatically, which Booked55 does not support. Replace YOUR_CLIENT_SECRET with the client secret we share on request (contact us).

If you already have other MCP servers configured, add the booked55 entry alongside them inside the existing mcpServers object — do not replace the entire file.

Save the config, fully quit Claude Desktop (Claude menu → Quit Claude), and relaunch. On first tool use, complete OAuth authorization in your browser. Requires Node.js installed for npx.

Method 3 — Claude.ai (Web)

Claude.ai supports the same custom connector flow as Claude Desktop for remote MCP servers.

Go to claude.ai and sign in.
Navigate to Settings → Connectors.
Click Add custom connector.
Enter the MCP server URL: https://mcp.booked55.com
Expand Advanced settings and enter the OAuth Client ID b55_a6e0faeeedc74d50c5d9fec98bf9a75c and the client secret you received from us — both fields are required.
Complete OAuth authorization — sign in with your Booked55 credentials and click Authorise.

Verify the connection

Start a new conversation and try a read-only query to confirm the MCP server is working:

Search my contacts for anyone named Sarah.

Claude should call the search_contacts tool and return matching records from your Booked55 workspace. If you see tool-call confirmations or results, the connection is active.

Example prompts

Try these prompts once connected:

Add a contact

Add a new contact: John Smith, [email protected], VP of Sales at Acme Corp.

Search contacts

Find all contacts whose name contains "Sarah".

Pipeline review

Show me all deals in my sales pipeline. Which ones have been in the same stage for more than two weeks?

Post-meeting cleanup

I just met with Marcus Webb from Northwind Logistics. Add him as a contact, create a company record for Northwind, and set a follow-up task for next Tuesday.

Troubleshooting

Server not appearing in Claude

Check Settings → Developer → MCP Logs for error messages. Common issues: malformed JSON in the config file, missing comma between server entries, or Claude not fully restarted after saving changes.

"Automatic client registration isn't supported by booked55"

This message appears when the connector was added without a client ID. Edit the connector, expand Advanced settings, enter the OAuth Client ID b55_a6e0faeeedc74d50c5d9fec98bf9a75c and your client secret, and reconnect.

"Authentication failed" right after you authorize

Signing in and clicking Authorise succeeds, but Claude then reports an authentication failure and the connector stays disconnected — and each tool call re-opens the authorization screen. This means the connector has the Client ID but not the client secret, so the final token exchange is rejected. Edit the connector, add the client secret alongside the Client ID, and reconnect. Contact us if you don't have the secret yet.

Authorization fails

Verify you are signing in with the same email used for your Booked55 account. If using the mcp-remote method, verify Node.js is installed and npx can reach the network. If you don't have an account yet, create one for free.

Tools return errors

Check that the MCP endpoint is set to exactly https://mcp.booked55.com with no trailing slash. Confirm your Booked55 account is active and you have data in your workspace to query.

Next steps

Ready to try it?

Get Started Free Learn More