Close MCP Server

Connectors requires a Claude paid plan

In order to access Claude’s Connectors library that includes Close, you must be on a paid plan.

1. Navigate to Settings by clicking your name in the bottom left sidebar on web or desktop.

2. In the Settings sidebar select Connectors, then Organization connectors.

3. Find and select the Close connector, then click Connect.

4. Grant access to your desired Close organization and scopes.

5. Make sure to enable the tools in any new chats.

In a few steps, you can access Close’s MCP server on the Claude desktop app on any plan:

1. Open ~/Library/Application\ Support/Claude/claude_desktop_config.json (you can locate the file via Settings > Developer > Edit Config in the app) and add the following code:

   {
     "mcpServers": {
       "close": {
         "command": "npx",
         "args": [
             "-y",
             "mcp-remote",
             "https://mcp.close.com/mcp",
             "--header",
             "Close-API-Key: ${CLOSE_API_KEY}",
             "--header",
             "Close-Scope: mcp.read"
         ],
         "env": {
           "CLOSE_API_KEY": "YOUR_API_KEY"
         }
       }
     }
   }

   • Replace YOUR_API_KEY with your Close API Key.

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

   • Optionally, change mcp.read to mcp.write_safe or mcp.write_destructive to increase the scope.

2. Restart the Claude desktop app.

1. Open your terminal and run CLOSE_API_KEY=YOUR_API_KEY, replacing YOUR_API_KEY with your Close API Key.

2. Run the following:

   claude mcp add --scope user --transport http close https://mcp.close.com/mcp --header "Close-API-Key: ${CLOSE_API_KEY}" --header "Close-Scope: mcp.read"

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

   • Optionally, change mcp.read to mcp.write_safe or mcp.write_destructive to increase the scope.

3. Launch a Claude Code session with claude and type /mcp to verify Close MCP was set up.

See Claude Code MCP Docs for more information on using MCP servers with Claude Code.

You can use n8n’s “AI Agent” node to set up a chatbot with read access to your Close Organization.

1. Create a new Workflow and add “Chat Trigger” as your first step.

2. 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 of the major LLM providers)

     • Memory — Memory allows a model to remember and reference past interactions with it. While it is 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.

3. 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 the following:

     • Name: Close-API-Key

     • Value: {{ Your Close API Key }}

   • Tools to Include: All

4. Start chatting with your new AI Agent in the “Chat” window at the bottom left of the Workflow Editor:

⚠️ Please note that n8n only supports the mcp.read scope at this time.

1. After clicking the “Add to Cursor” button above, you should see the Close MCP Server listed in MCP Tools in the Cursor desktop app. Click “Install”:
   

2. 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:
   

3. Select the correct Close Organization and scope for your use case and click “Allow”:
   

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

Step 1

Add the following to your settings.json :

{
	...
	"mcp": {
		"servers": {
			"close": {
				"url": "https://mcp.close.com/mcp",
				"type": "http",
				"headers": {
					"Close-API-Key": "${input:close-api-key}",
					"Close-Scope": "mcp.read"
				}
			}
		},
		"inputs": [
			{
				"id": "close-api-key",
				"description": "Enter your Close API key",
				"type": "promptString"
			}
		]
	}
}

This will add a read only MCP server to your VSCode. You can also 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

Use the command palette (Mac: Cmd+Shift+P, Windows: Ctrl+Shift+P) to list the MCP servers, select close-remote-mcp, 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!

With Copilot: Open the sidebar (Mac: Cmd+Shift+I, Windows: Ctrl+Alt+I) 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 you selected to run Org Info and return information