Model Context Protocol (MCP) servers provide a standardized interface that allows any compatible AI model or agent to access your Close data in a simple and secure way. Below are instructions for adding Close’s MCP server to commonly used clients.
The MCP server URL is https://mcp.close.com/mcp and has “HTTP Streamable” and “OAuth 2.0 Dynamic Client Registration (DCR)” support.
We recommend accessing the MCP server via OAuth 2.0 using a supported MCP client (e.g. Claude, ChatGPT, Cursor, etc). If you prefer to interact with the MCP server using a custom setup, create an OAuth application to authenticate using OAuth 2.0 or authenticate using an API key and include the following headers in your request:
The Close-Scope header determines the scope and available tools:
mcp.read — read-only accessmcp.write_safe — can read and write datamcp.write_destructive — can read, write, and delete dataFor more information on which tools are available for each scope, see Close MCP Tools.
Close’s MCP server is officially supported across the Claude ecosystem. Watch this video to learn more about connecting Claude to Close and see some example use cases:
If you want to set up MCP for multiple organizations, you need to add custom connectors for each:
close-mcp-org-name.https://mcp.close.com/mcp?1. You will need to increment 1 for each additional connection (the second custom connector would have https://mcp.close.com/mcp?2 for the URL). This is a hack, as Claude does not allow multiple connectors with the same URL.If you prefer to use API key instead of OAuth, you can specify it in headers:
Optionally, change mcp.read to mcp.write_safe or mcp.write_destructive to increase the scope.
If you want to set up MCP for multiple organizations, you can give this a more specific name like close-your-org-name instead of close so that you can distinguish the servers from one another.
claude and type /mcp to verify Close MCP was set up.See the Claude Code MCP Docs for more information on using MCP servers with Claude Code.
Interact with Close’s MCP server by connecting Close’s official ChatGPT App.
You can use n8n’s “AI Agent” node to set up a chatbot with read access to your Close Organization.

https://mcp.close.com/mcphttps://mcp.close.com/mcp
OAuth is recommended. If you need to use an API key instead, select Header Auth for Authentication and create a Header Auth Credential with Name set to Close-API-Key and Value set to your Close API Key.
Click: Add Close to Cursor, or manually add the server URL https://mcp.close.com/mcp in Cursor’s MCP Tools settings.
You should see the Close MCP Server listed in MCP Tools in the Cursor desktop app. Click Install.




Add the following to your settings.json:
This will add a read-only MCP server to your VS Code. You can change Close-Scope to mcp.write_safe or mcp.write_destructive to increase the scope. Alternatively, you can add the snippet to your mcp.json file for workspace-level server access.
Use the command palette (Cmd+Shift+P on Mac, Ctrl+Shift+P on Windows) to list the MCP servers, select close, and click “Start Server.” Enter your Close API Key when prompted.

If the server is not in the list, use the command palette to “Reload Window.” The console will confirm that the server is connected:

Open Copilot in the sidebar (Cmd+Shift+I on Mac, Ctrl+Alt+I on Windows) and switch to agent mode. You can click the tool icon to list the available tools. Ask Chat what Close Organization you are working in and you should see that it uses the server to return organization information.
Any MCP client that supports HTTP Streamable transport can connect to Close’s MCP server at https://mcp.close.com/mcp. Use either OAuth 2.0 or API key authentication via the Close-API-Key and Close-Scope headers as described above.
We currently don’t support SSE, but please email support@close.com with your specific use case and MCP client details if this is something your team requires.
See Close MCP Tools for the full list of tools available for each scope.
Yes. You can add a custom connector for each organization with the URL as https://mcp.close.com/mcp and use either OAuth 2.0 or API key authentication via the Close-API-Key and Close-Scope headers. Each connection will need a unique name like close-mcp-org-name.