How to Use Claude with Your CRM via MCP

Claude and the Model Context Protocol share the same origin story (both were created at Anthropic to make AI more capable and useful. If you use Claude as your daily AI assistant, connecting it to your CRM through MCP is the most direct path to managing contacts, deals, and tasks without leaving your conversation.

Booked55's hosted MCP endpoint gives Claude full read-and-write access to your CRM: contacts, companies, pipelines, tasks, and events across 16 tools. This guide covers two connection methods: custom connectors in Claude Desktop (recommended) and the mcp-remote bridge for config-file setups.

What you'll need

• Claude Desktop or a Claude.ai plan with connector support
• A Booked55 account (14-day free trial)
• About 10 minutes for first-time setup

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.

1. Open Claude Desktop → Settings → Connectors.
2. Click Add custom connector.
3. Enter the remote MCP server URL: https://mcp.booked55.com
4. Complete OAuth authorization when prompted, sign in with your Booked55 credentials and click Authorise.
5. The connector appears in your connectors list when ready. Start a new conversation and ask Claude to search contacts or update a deal to confirm the connection.

Method 2: mcp-remote Bridge (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:

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

{
 "mcpServers": {
 "booked55": {
 "command": "npx",
 "args": ["-y", "mcp-remote", "https://mcp.booked55.com"]
 }
 }
}

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.

Things to try once connected

Claude excels at multi-step reasoning, which makes it particularly powerful with MCP tools. Here are workflows that showcase the combination:

Claude gets access to all 16 Booked55 MCP tools once connected, including bulk operations like bulk_update_contacts_pipeline. See the complete tool reference in our MCP overview.

Claude vs. ChatGPT for CRM

Both AI clients connect to the same Booked55 MCP server with the same tools. The difference is in how they use them:

• Claude tends to chain multiple tool calls in a single turn, useful for complex multi-step workflows like post-meeting cleanup.
• ChatGPT shows explicit tool call confirmations before executing writes, useful when you want to review every action before it happens.
• Claude Desktop supports local MCP servers alongside remote ones, you can connect Booked55 alongside filesystem, GitHub, or database servers in one conversation.

Many teams use both: ChatGPT for quick mobile CRM updates and Claude Desktop for deep pipeline analysis sessions. The MCP server is the same either way.

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.

Authentication fails

Ensure 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.

Tools return errors

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

Advanced Claude Workflows for CRM Power Users

Once you are comfortable with basic CRM commands, these advanced workflows showcase Claude's multi-step reasoning with MCP:

• Account planning sessions(“Build an account plan for Acme Corp: all contacts, deal history, open tasks, and suggested next steps.”
• Territory analysis) “Group my contacts by city and show me which regions have the most pipeline value.”
• Competitive displacement, “Find all deals where the contact mentioned a competitor in their notes.”
• Quarterly business review prep, “Summarize my Q2 performance: deals closed, pipeline added, activity levels, and top accounts.”

These workflows require Claude to call five or more MCP tools in sequence and synthesize the results (something that would take 30+ minutes of manual CRM navigation and spreadsheet work.

Claude.ai (Web) vs. Claude Desktop

Both Claude Desktop and Claude.ai support custom MCP connectors through Settings → Connectors. Claude Desktop additionally supports local stdio servers and the mcp-remote config-file method, plus Developer logs for debugging tool calls.

For CRM workflows, either client works) add https://mcp.booked55.com as a custom connector. Free plans include one connector; Pro, Max, Team, and Enterprise plans support more.

Security Considerations

When connecting Claude to your CRM, keep these security practices in mind:

• Use OAuth when possible, It scopes access to your user account and can be revoked without rotating API keys.
• Review tool calls before confirming writes, Claude shows you what it intends to change before executing create/update operations.
• Do not share config files (Your claude_desktop_config.json may reference local server paths. Treat it like a sensitive file.

Real-World Example: Insurance Broker Morning Routine

Diane is an independent P&C broker with 180 client households. She starts each day in Claude Desktop before her first appointment:

“Show me policies renewing in the next 60 days, any overdue follow-up tasks, and contacts I have not reached in 30 days. Prioritize by renewal date.”

Claude calls list_pipelines, list_tasks, and search_contacts, then returns a prioritized call list. After her 10 AM meeting with the Okonkwo family about their commercial property renewal, she says: “Log the call, they want quotes for two additional locations by month-end. Create tasks for each quote and move the renewal deal to Proposal.” Five MCP tool calls, under two minutes, no CRM tabs opened. For similar workflows on mobile, see AI CRM for solo sales reps and natural language CRM queries.

Best Practices for Claude + CRM

• Be specific with names and values, “Move the Meridian Health deal to Proposal at $80K” beats “update that deal.”
• Confirm bulk operations, When Claude chains five or more writes, review the summary before approving.
• Use Claude for analysis, ChatGPT for quick mobile updates, Many reps use both clients against the same MCP server for different contexts.
• Start with read-only queries, Build confidence with “show me my pipeline” before attempting multi-step write workflows.

Voice and Mobile: CRM Without a Keyboard

Solo reps spend most of their day away from a desk. ChatGPT and Claude mobile apps support voice input, which pairs naturally with MCP:

• Dictate post-meeting updates while walking to your car
• Ask pipeline questions over coffee before your first appointment
• Batch-add networking contacts from voice notes after an evening event

The MCP server does not care whether your input was typed or spoken (the AI transcribes, parses intent, and calls the same 16 tools. Combined with Booked55's native iOS and Android apps for contact lookup, solo reps get full CRM capability without sitting at a laptop. See our ChatGPT MCP guide for mobile connection setup.

Test Claude MCP workflows with three daily tasks before expanding: post-meeting contact updates, morning pipeline review, and end-of-day task creation.

Anthropic's MCP documentation for Claude covers connector setup, OAuth flows, and tool-call debugging.

Claude Desktop custom connectors require OAuth setup once, then persist across sessions. Test with low-risk queries first) list recent contacts, summarize last week's activities, before asking Claude to create or update records. Booked55 MCP exposes 16 read/write tools; start with read-only workflows until your team trusts AI-generated CRM updates.

Document three approved MCP workflows for your team before expanding to write operations, controlled rollout beats permission chaos.

Start Claude MCP with read-only contact queries, add write operations after one week of verified responses (controlled rollout prevents bad CRM data from AI typos.

Document approved Claude MCP prompts for your team so CRM updates stay consistent across users.

The Bottom Line

When Claude invokes Booked55 MCP tools, you see a structured confirmation before any write operation executes. The UI shows:

• Tool name) e.g., create_contact or update_pipeline_item
• Arguments, The exact JSON parameters Claude will send to the MCP server
• Approve / Deny, You control whether the write proceeds

Read operations like list_pipelines and search_contacts typically execute without confirmation because they do not modify data. This human-in-the-loop pattern is why connecting AI to production CRM data is safe for regulated industries and solo practitioners alike, you see every change before it happens.

Developer logs in Claude Desktop (Settings → Developer → MCP Logs) show the full JSON-RPC request and response for each tool call, useful when troubleshooting auth errors or verifying that the correct MCP endpoint is configured.

tool reference and our guide on what MCP is and how it works. Questions? Contact us.