Close CRM MCP Server
Connect Close CRM to your AI agents with the Close CRM MCP server.
Updated
What is Close CRM MCP?
The Close CRM MCP server is a Model Context Protocol server that connects Close CRM to AI agents and assistants as a set of tools. With it connected, an agent can work with Close CRM (sales crm — leads, contacts, opportunities, activities) directly — instead of you copying data in and out by hand.
It is a remote MCP server that uses OAuth, so you point your client at the server URL, authorize once, and the Close CRM tools become available to the model.
Connect the Close CRM MCP server
Connect Close CRM MCP to Claude Code
- 1
Add the server
Use `claude mcp add` with the Close CRM MCP server URL (or its `npx` command), following the official docs.
- 2
Authorize
Complete authentication (OAuth) so Claude Code can call the server.
- 3
Verify
Ask Claude to use a Close CRM tool to confirm the connection is live.
Connect Close CRM MCP to Cursor
- 1
Open MCP settings
In Cursor, go to Settings → MCP → Add new server.
- 2
Add Close CRM
Provide the Close CRM MCP server URL or command and complete authentication.
- 3
Test
Reference Close CRM from chat to confirm Cursor can reach the tools.
Sample use cases
An agent enriches new Close leads with company data from external sources and updates custom fields
Richer lead profiles without manual research by the sales team.
A scheduled agent reviews stale opportunities and nudges reps via Slack with suggested next actions
Fewer deals falling through the cracks due to inactivity.
An agent logs call notes and email summaries to the correct Close lead after each interaction
Complete activity history without reps manually updating CRM records.
An agent pulls pipeline data from Close and generates a weekly sales forecast report
Consistent forecasting without manual data pulls and spreadsheet work.
A support agent looks up a customer's deal history and recent communications in Close during a help request
Faster support resolution with full customer context from the CRM.
An agent creates follow-up tasks in Close when a lead opens a proposal email but does not respond
Automated follow-up triggers based on engagement signals.
An agent syncs won deals from Close to an invoicing system and creates billing records
Seamless handoff from sales to finance with zero manual data entry.
Using Close CRM MCP with Gamut
On Gamut, the Close CRM MCP server becomes a tool your agents use inside an automated, event-driven workflow — triggered by an event or a schedule, acting through Close CRM and your other connected MCP servers, with the connection managed by Gamut rather than a local config file.
Frequently asked questions
What CRM data can agents access through the Close MCP server?
Agents can read and write leads, contacts, opportunities, activities (calls, emails, notes), tasks, and custom fields. This covers the core Close data model needed for sales automation.
Can the Close MCP server automate outbound sales sequences?
The server provides tools to create and update leads, log activities, and manage tasks. Agents can orchestrate multi-step outreach by creating tasks, logging touchpoints, and updating lead status based on engagement.
Does the Close MCP server support pipeline reporting?
Yes. Agents can query opportunities by stage, value, and date to build pipeline snapshots, win-rate analyses, and sales velocity reports without manual exports.
How does authentication work with the Close MCP server?
The server uses Close API keys for authentication. In Gamut, you configure the key once in your agent's secrets, and the MCP connection handles auth automatically for all subsequent requests.