Close MCP Server
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.
Accessing Close’s Remote MCP Server
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 data
For more information on which tools are available for each scope, see Close MCP Tools.
MCP Client Setup
Claude (Web, Desktop)
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:
- Navigate to Settings by clicking your name in the bottom left sidebar on web or desktop.
- In the Settings sidebar, select Connectors, then Organization connectors.
- Find and select the Close connector, then click Connect.
- Grant access to your desired Close organization and scopes.
- Make sure to enable the tools in any new chats.
Claude Code
- In your terminal, add the MCP server:
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.
- Launch a Claude Code session with
claudeand type/mcpto verify Close MCP was set up.
See the Claude Code MCP Docs for more information on using MCP servers with Claude Code.
ChatGPT
As of October 7, 2025, ChatGPT’s MCP support via Connectors remains limited and subject to your ChatGPT plan. Alternatively, you can connect Close to ChatGPT using the CloseGPT integration.
On any ChatGPT paid plan, you can give ChatGPT access to Close by adding a custom Connector:
- Navigate to your Connectors settings in ChatGPT.
- If you are not already in Developer Mode, scroll down to Advanced settings and toggle on Developer Mode.
- Click Create at the top right.
- Fill out the New Connector form with the following details:
- Icon: Use the Close logo icon
- Name: Close (or the name of your Close organization)
- Description: Connects to the Close MCP Server
- MCP Server URL:
https://mcp.close.com/mcp - Authentication: OAuth
- Click Create and ChatGPT should take you to Close to select your organization and desired scopes.
- Ask ChatGPT to “List all available tools in the Close connector” to test the tool is connected.


n8n
You can use n8n’s “AI Agent” node to set up a chatbot with read access to your Close Organization.
- Create a new Workflow and add Chat Trigger as your first step.

- Add an AI Agent node as your second step. The AI Agent node has three components:
- Chat Model — The LLM of your choice (n8n supports all major LLM providers)
- Memory — Allows a model to remember and reference past interactions. While not required, we recommend n8n’s “Simple Memory,” which requires no setup.
- Tool — This is where you will connect to Close’s MCP server.
- Connect the Chat Model and Memory options of your choice, and then add the MCP Client Tool node under Tool.
- For the MCP Client Tool node, use the following configuration:
- Endpoint:
https://mcp.close.com/mcp - Server Transport: HTTP Streamable
- Authentication: Header Auth
- Create a new Header Auth Credential in your n8n account with:
- Name:
Close-API-Key - Value: Your Close API Key
- Name:
- Tools to Include: All
- Endpoint:

- Start chatting with your new AI Agent in the “Chat” window at the bottom left of the Workflow Editor.
n8n only supports the mcp.read scope at this time.
Cursor
-
Click: Add Close to Cursor, or manually add the server URL
https://mcp.close.com/mcpin Cursor’s MCP Tools settings. -
You should see the Close MCP Server listed in MCP Tools in the Cursor desktop app. Click Install.

- The connection will be in the “Needs authentication” status. Click Connect and allow the Cursor app to direct you to the Close OAuth Authentication Page.

- Select the correct Close Organization and scope for your use case and click Allow.

- Return to the Cursor app. You should see that the connection is now “Loading Tools” or “Enabled”.

VS Code
Step 1: Configure the MCP server
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.
Step 2: Start the server
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:

Step 3: Start using the server
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.
Other MCP Clients
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.
FAQs
Does Close MCP support SSE?
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.
What tools does the MCP server have access to?
See Close MCP Tools for the full list of tools available for each scope.