Overview#
AutomateNexus CRM supports the Model Context Protocol (MCP), an open standard that allows AI assistants and development tools to interact with your CRM data securely. Through the CRM's MCP server, you can connect Claude, ChatGPT, Claude Desktop, Claude Code, Cursor, and other MCP-compatible clients to look up contacts and customers, manage deals, project tasks, and checklists, and send email and text messages, using natural language. There are two ways in: Claude and ChatGPT connect with your CRM sign-in, with no key to copy, and other clients use an MCP key from the MCP server card. This guide covers both.
Prerequisites#
Before configuring MCP integrations, ensure you have:
- An owner or admin account in your AutomateNexus CRM organization. The Claude and ChatGPT and MCP server cards are shown to owners and admins only.
- For the Claude or ChatGPT sign-in, an organization on a paid plan. An MCP key works while the workspace has a live plan.
- Claude, ChatGPT, or another MCP-compatible client (e.g., Claude Desktop, Claude Code, or Cursor).
- Node.js and npm on the computer that runs Claude Desktop, if you connect it with the MCP key: that configuration runs the
mcp-remotebridge withnpx. - Basic familiarity with JSON configuration files (for client-side MCP setup).
What is MCP?#
The Model Context Protocol (MCP) is an open protocol that standardizes how AI applications connect to external data sources and tools. It follows a client-server architecture where:
- MCP Servers expose data and functionality through a standardized interface. AutomateNexus CRM acts as an MCP server, providing tools to interact with your CRM data.
- MCP Clients are AI applications that connect to MCP servers to access their data and tools. Examples include Claude Desktop, Claude Code, Cursor, and other AI-powered development and productivity tools.
MCP defines tools, resources and prompts. The AutomateNexus CRM server exposes tools: functions the AI can call to read and change CRM data (e.g., list contacts, create a deal, complete a task). It does not publish resources or prompt templates.
Connecting Claude or ChatGPT with Your CRM Sign-In#
Claude and ChatGPT can connect to AutomateNexus CRM with a sign-in instead of a key. The Claude and ChatGPT card, the first section under Administration → Integrations → Developer, shows the Connector address, https://app.automatenexuscrm.com/mcp, with a Copy button.
- In Claude, open Settings, then Connectors, and choose Add custom connector.
- Name it AutomateNexus CRM and paste the connector address.
- Choose Connect. An AutomateNexus CRM page opens: sign in with your CRM account, pick the organization to connect, and choose Allow (Deny connects nothing).
In ChatGPT:
- Open Plugins, choose the plus button, then Add custom MCP server.
- Name it AutomateNexus CRM, paste the connector address as the public endpoint and choose OAuth.
- Choose Create as a plugin. An AutomateNexus CRM page opens: sign in with your CRM account, pick the organization to connect, and choose Allow.
Who Can Connect#
An owner or admin of an organization on a paid plan, with the MCP server switched on. The sign-in page lists your organizations and says why one can't be chosen, and the card shows the same reason. This is checked again on every call, so a connection stops working if you stop being an owner or admin, the plan ends, or the MCP server is switched off.
Only Claude (claude.ai and claude.com), ChatGPT (chatgpt.com) and programs on your own computer, such as Claude Code or Codex, can be connected this way. Any other app is shown This app can't be connected, with only Decline. When the sign-in would return to a program on your computer, the page warns you to allow it only if you started the connection yourself.
What the Connection Can Do#
The connection acts as you, with every tool listed under Available MCP Tools, including sending email and text messages. The permission toggles on the MCP server card apply to the MCP key, not to a Claude or ChatGPT connection. By default each connection can send up to 100 emails and 50 text messages in 24 hours; owners and admins can change this under Daily sending limits on the MCP server card.
Managing Connections#
Connected to this organization on the card lists each connected app with the teammate who connected it, when it was connected, and when it was last used. An app that has not reached the CRM since you chose Allow is shown as Allowed, with a note that it hasn't reached the CRM yet: its sign-in did not finish, so connect it again from the app. Disconnect cuts it off at once; to use it again, connect from the app again.
Enabling the AutomateNexus CRM MCP Server#
Activating MCP#
- Navigate to Administration → Integrations → Developer. The MCP server card is the second section on the page, after Claude and ChatGPT.
- Turn on the switch on the MCP server card and expand the card. While the switch is off, the server refuses every key and every signed-in connection.
- The card shows your MCP Endpoint URL (it ends in
/functions/v1/mcp-server, for examplehttps://app.automatenexuscrm.com/functions/v1/mcp-server) with a copy button. The server uses the Streamable HTTP transport: JSON-RPC 2.0 messages sent by HTTPS POST to this single URL. There is no SSE endpoint. - Under API Key, click Generate API Key. The key (it starts with
mcp_) is displayed once, with the note "Copy this key now. It will not be shown again." Copy it, then click Dismiss. Afterwards the card shows only the start of the key; make a new one if it is lost. - The card shows Active once the switch is on and a key exists. It shows Key not working when the key has expired or the person who made it is no longer an owner or admin; revoke it and make a new one.
The MCP key is separate from your REST API keys: the MCP server accepts only keys generated on this card, and the REST API refuses the MCP key. The card manages one key; use Revoke key… and confirm with Revoke before generating a replacement, and update every client that used the old key.
Configuring MCP Permissions#
Control which CRM capabilities the MCP key exposes:
- Once a key exists, the Permissions block appears on the MCP server card.
- Toggle each scope on or off:
- Contacts (read) and Contacts (write)
- Deals (read) and Deals (write)
- Tasks (read) and Tasks (write)
- Conversations (read) and Conversations (write)
- Analytics (read)
- Send emails and Send text messages
- By default every read scope is on, and every write scope and both sending scopes are off. Changes save immediately.
Tools whose scope is switched off are not listed to the client at all, and a call to one of them returns a permission-denied error.
MCP Authentication#
MCP connections made with the MCP key are authenticated like this:
- Each client sends the key as a bearer token:
Authorization: Bearer mcp_…. - The key's permission toggles decide which tools the client sees and can call.
- The key works only while the person who generated it is still an owner or admin, and while the workspace has a live plan.
- Tool calls are limited to 1,000 an hour for the organization, counting every key and connection together. Over the limit, the server answers
429with aRetry-Afterheader.
Connecting Claude Desktop#
About Claude Desktop MCP#
Claude Desktop supports MCP connections, allowing Claude to directly interact with your AutomateNexus CRM data. You can ask Claude to look up contacts, summarize deal pipelines, create tasks, and more using natural language. The sign-in in Connecting Claude or ChatGPT with Your CRM Sign-In needs no key; the steps below connect Claude Desktop with the MCP key instead.
Step-by-Step Claude Desktop Setup#
- On the MCP server card, expand Connection Instructions. It contains a ready-made Claude Desktop configuration with your endpoint URL filled in, and a copy button.
- Open Claude Desktop on your computer.
- Navigate to Settings (click the gear icon or use the keyboard shortcut).
- Select Developer from the settings sidebar.
- Click Edit Config to open the MCP configuration file (
claude_desktop_config.json). - Paste the configuration into the
mcpServerssection. It has this shape:{ "mcpServers": { "crm": { "command": "npx", "args": [ "-y", "mcp-remote", "https://app.automatenexuscrm.com/functions/v1/mcp-server", "--header", "Authorization:${AUTH_HEADER}" ], "env": { "AUTH_HEADER": "Bearer <YOUR_MCP_KEY>" } } } } - Replace
<YOUR_MCP_KEY>with the key you generated, keepingBearerand the space in front of it. Keep the endpoint URL exactly as the card shows it. The key travels in theAuthorizationheader:mcp-remoteignores anAPI_KEYsetting, so a configuration that puts the key there does not connect. - Save the configuration file.
- Restart Claude Desktop.
- The AutomateNexus CRM tools will appear in Claude Desktop. You can verify by clicking the tools icon in the chat input area.
Using Claude Desktop with AutomateNexus CRM#
Once connected, you can interact with your CRM data through natural conversation with Claude:
- "Look up the contact details for John Smith."
- "Show me all deals in the negotiation stage."
- "Add a task to the Acme rollout project for the kickoff call, due next Friday."
- "What is the total value of deals by stage?"
- "Mark the project task 'Send proposal' as completed."
- "Search for anything related to TechCo."
Connecting Claude Code#
Connection Instructions on the MCP server card also gives a Claude Code command of the form claude mcp add --transport http crm "https://app.automatenexuscrm.com/functions/v1/mcp-server" --header "Authorization: Bearer <YOUR_MCP_KEY>", with your endpoint URL filled in. Copy it, replace the key placeholder, and run it in a terminal. Keep --transport http: without it, Claude Code takes the address for a local command to run. The AutomateNexus CRM tools are then available in your Claude Code sessions.
Connecting Cursor#
About Cursor MCP#
Cursor is an AI-powered code editor that supports MCP connections. Connecting AutomateNexus CRM to Cursor allows developers to query CRM data while building integrations, debugging API calls, or developing custom features.
Step-by-Step Cursor Setup#
- On the MCP server card, expand Connection Instructions and copy the Cursor configuration.
- Add it to
~/.cursor/mcp.json. It connects to the endpoint directly, with no bridge to install:{ "mcpServers": { "crm": { "url": "https://app.automatenexuscrm.com/functions/v1/mcp-server", "headers": { "Authorization": "Bearer <YOUR_MCP_KEY>" } } } } - Replace
<YOUR_MCP_KEY>with your MCP key, save the file, and restart Cursor if prompted. - The AutomateNexus CRM tools will be available in Cursor's agent mode.
Available MCP Tools#
The following tools are available to MCP clients. With the MCP key, each needs the permission named; a Claude or ChatGPT sign-in connection has all of them.
Contact and Customer Tools#
- list_contacts: Search and list contacts by name or email; returns name, email, phone, job title and the associated customer. Requires Contacts (read).
- get_contact: Retrieve full details for a specific contact. Requires Contacts (read).
- create_contact: Create a new contact (first and last name required; email, phone, job title and customer optional). Requires Contacts (write).
- update_contact: Update fields on an existing contact. Requires Contacts (write).
- list_customers: List customers (companies/accounts), optionally filtered by status. Requires Contacts (read).
- search: Full-text search across contacts, deals, tasks and customers. Requires Contacts (read).
Deal Tools#
- list_deals: List deals with optional filters by stage or title. Requires Deals (read).
- get_deal: Retrieve a deal with its customer details. Requires Deals (read).
- create_deal: Create a deal with a title and optional value, stage, customer, description and expected close date. Requires Deals (write).
- update_deal: Update a deal, including moving it to a different stage. Requires Deals (write).
- get_pipeline_stats: Deal count and total value by stage. Requires Analytics (read).
To-Do Tools#
These work on the CRM's to-dos: the follow-ups on the dashboard and on customers and deals.
- list_tasks: List to-dos with optional status and priority filters. Requires Tasks (read).
- create_task: Create a to-do with a title and optional description, priority, due date, customer and deal. Requires Tasks (write).
- complete_task: Mark a to-do as completed. Requires Tasks (write).
Project Tools#
These work on the tasks in your projects (Projects → Tasks).
- list_projects: List your projects, to find the project a task belongs on. Requires Tasks (read).
- list_project_tasks: List project tasks, optionally for one project, status, or person, or the subtasks under one task; each task has its lead and everyone on it. Requires Tasks (read).
- create_project_task: Add a task to a project, or a subtask under any task. Requires Tasks (write).
- complete_project_task: Mark a project task as completed. Requires Tasks (write).
- set_project_task_client_visibility: Share a project task with the project's client, or make it internal. Requires Tasks (write).
- list_task_checklists: A project task's checklists with their items and progress. Requires Tasks (read).
- add_checklist_item and set_checklist_item_done: Add an item to a task's checklist, and tick it off or on again. Require Tasks (write).
- list_task_links and link_project_tasks: The tasks a project task is linked to, and a new link (relates to, duplicates, or is duplicated by). Require Tasks (read) and Tasks (write).
Conversation and Sending Tools#
- list_conversations: List recent internal or client conversations. Requires Conversations (read).
- send_message: Send a message in a conversation. Requires Conversations (write).
- send_email: Send an email to one person, as the person who made the key or connected Claude: from their own mailbox when they have one connected, with their signature, and put on the contact's timeline. Requires Send emails.
- send_text: Send a text message to one person from the organization's Twilio number. Requires Send text messages.
Nobody who unsubscribed or bounced is emailed, and numbers that opted out are never texted. Each key or connection can send up to its daily limit: 100 emails and 50 text messages in 24 hours, unless an owner or admin changed Daily sending limits on the MCP server card.
Security Best Practices#
- Use the sign-in for Claude and ChatGPT: The connector needs no key in a configuration file, and Disconnect on the card cuts it off at once.
- Restrict MCP permissions: Only enable the scopes your clients need. If you only need read access, leave the write and sending toggles off; they are off by default.
- Monitor MCP usage: The Usage block on the MCP server card shows requests today, when a client last connected, and the most-used tools.
- Rotate the key periodically: Click Revoke key…, confirm with Revoke, then Generate API Key, and update your clients. Revoking immediately disconnects every client that used the old key.
- Secure your configuration files: Ensure the
claude_desktop_config.json,~/.cursor/mcp.jsonand similar MCP configuration files are not committed to public repositories or shared in insecure channels.
Testing MCP Connections#
- Verify server status: Navigate to Administration → Integrations → Developer and check that the MCP server card shows Active.
- Test from Claude: Ask a simple CRM query like "List my most recent contacts." Verify that Claude calls the AutomateNexus CRM tools and returns accurate data. A Claude or ChatGPT connection appears under Connected to this organization on the Claude and ChatGPT card.
- Test write operations: With the relevant write scope on (a Claude or ChatGPT connection has them all), ask Claude to create a test contact or task. Verify the record appears in AutomateNexus CRM.
- Test from Cursor or Claude Code: Ask for CRM data and verify the response includes real data from your CRM.
- Check usage: After testing, the Usage block on the card should show the requests and the tools that were called.
Troubleshooting#
MCP Server Not Connecting#
- Verify the MCP server switch is on under Administration → Integrations → Developer. While it is off, every call is answered "The MCP server is switched off for this workspace."
- Check that the key in your client configuration is the MCP key from the card (not a REST API key) and has not been revoked, and that the card does not show Key not working.
- Ensure the endpoint URL matches the MCP Endpoint URL on the card exactly.
- The endpoint accepts HTTP POST only; a client configured for SSE will not connect. In Claude Code, add the server with
--transport http.
Claude or ChatGPT Will Not Connect#
- Only an owner or admin of an organization on a paid plan, with the MCP server switched on, can connect Claude or ChatGPT. The sign-in page and the Claude and ChatGPT card say which of these is missing.
- This app can't be connected: Only Claude, ChatGPT and programs on your own computer can be connected. Decline, and nothing is connected.
- "The sign-in has expired or was revoked" or "This connection was disconnected": Connect AutomateNexus CRM again from the app's connector settings.
- The app showed an error after you chose Allow, and the card says it hasn't reached the CRM yet: its sign-in did not finish. Connect again from the app.
Tools Not Appearing in Claude Desktop#
- Restart Claude Desktop after updating the configuration file.
- Check the configuration file for JSON syntax errors (missing commas, brackets, etc.).
- Make sure Node.js and npm are installed so that
npx -y mcp-remotecan run. - Check the Claude Desktop developer console for error messages.
Permission Denied Errors#
- Check the Permissions toggles on the MCP server card. The scope the tool needs must be on; write tools need the matching write scope, and the sending tools need Send emails or Send text messages.
- Tools for a disabled scope are hidden from the client; if a tool is missing from the client's list, this is why.
Emails or Texts Refused#
- Each key or connection can send up to its daily limit: 100 emails and 50 text messages in 24 hours, unless an owner or admin changed Daily sending limits on the MCP server card. Send the rest from the CRM.
- Each call sends to one recipient. People who unsubscribed or bounced are not emailed, and numbers that opted out are not texted.
- send_text sends from the organization's Twilio number; see Communication Integrations.
Slow MCP Responses#
- Check your internet connection stability.
- Large queries (e.g., listing contacts without a search term) may take longer. Use the query filters and the
limitandoffsetarguments. - A burst of tool calls can reach the organization's 1,000-an-hour limit; the server then returns
429until the window passes.
Related Articles#
- API Overview & Authentication — The REST API, for integrations that are not AI clients.
- AI Provider Configuration — Configure the AI providers the CRM's own AI features use.
- Webhooks & Custom Integrations — Build custom integrations that complement your MCP setup.
- Automation Platform Connections — Connect automation platforms alongside MCP for comprehensive workflow coverage.