***

title: Close MCP Server
slug: /mcp
----------

[Model Context Protocol (MCP)](https://modelcontextprotocol.io/) 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](/integrations/create-an-oauth-app) to authenticate using OAuth 2.0 or authenticate using an API key and include the following headers in your request:

```
Close-API-Key: {{ Your Close API Key }}
Close-Scope: {{ mcp.read, mcp.write_safe, or mcp.write_destructive }}
```

The `Close-Scope` header determines the scope and available tools:

* **`mcp.read`** — read-only access
* **`mcp.write_safe`** — can read and write data
* **`mcp.write_destructive`** — can read, write, and delete data

For more information on which tools are available for each scope, see [Close MCP Tools](/mcp/tools).

## MCP Client Setup

<AccordionGroup>
  <Accordion title="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:

    <iframe src="https://close.wistia.com/embed/iframe/8qj8o1c1nu" title="Close MCP + Claude" allowFullScreen />

    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.
  </Accordion>

  <Accordion title="Claude Code">
    1. In your terminal, add the MCP server:

    ```bash
    claude mcp add --scope user --transport http close https://mcp.close.com/mcp 
    ```

    If you prefer to use API key instead of OAuth, you can specify it in headers:

    ```bash
    export CLOSE_API_KEY=YOUR_API_KEY

    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"
    ```

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

    <Note>
      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.
    </Note>

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

    See the [Claude Code MCP Docs](https://code.claude.com/docs/en/mcp) for more information on using MCP servers with Claude Code.
  </Accordion>

  <Accordion title="ChatGPT">
    <Note>
      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](https://help.close.com/docs/closegpt).
    </Note>

    On any ChatGPT paid plan, you can give ChatGPT access to Close by adding a custom Connector:

    1. Navigate to your **Connectors settings** in ChatGPT.
    2. If you are not already in Developer Mode, scroll down to **Advanced settings** and toggle on **Developer Mode**.
    3. Click **Create** at the top right.
    4. Fill out the New Connector form with the following details:
       * **Icon**: Use the [Close logo icon](https://cdn.prod.website-files.com/61717799a852418a278cfa9b/68793d8479790aec5ed95512_close-logo-color-atom.svg)
       * **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
    5. Click **Create** and ChatGPT should take you to Close to select your organization and desired scopes.
    6. Ask ChatGPT to "List all available tools in the Close connector" to test the tool is connected.

    ![Adding a new custom Connector to ChatGPT](https://files.buildwithfern.com/close.docs.buildwithfern.com/3e88e06e3aca4fa1fab40922d00495f874e0849393344825b0a25d6617119f44/docs/pages/mcp/images/chatgpt-new-connector.png)

    ![Giving ChatGPT access to your desired Close organization and scopes](https://files.buildwithfern.com/close.docs.buildwithfern.com/717357e405de9573edf410e904e29cbb8c7f5c0de96736c560488b3dd0aa3f17/docs/pages/mcp/images/chatgpt-oauth.png)
  </Accordion>

  <Accordion title="n8n">
    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.

    ![n8n workflow with Chat Trigger and AI Agent](https://files.buildwithfern.com/close.docs.buildwithfern.com/c68200bbc5f9aa69834eb5a8653cded95149a3e56cac4c683d3fb9bfbd2043bb/docs/pages/mcp/images/n8n-workflow.png)

    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 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.
    3. Connect the Chat Model and Memory options of your choice, and then add the **MCP Client Tool** node under Tool.
    4. 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
       * **Tools to Include**: All

    ![n8n MCP Client Tool configuration](https://files.buildwithfern.com/close.docs.buildwithfern.com/493bcf67c1874e7d51238065b7ad4548fad78c25b051dfae33e5947e624439f9/docs/pages/mcp/images/n8n-mcp-config.png)

    5. Start chatting with your new AI Agent in the "Chat" window at the bottom left of the Workflow Editor.

    <Warning>
      n8n only supports the `mcp.read` scope at this time.
    </Warning>
  </Accordion>

  <Accordion title="Cursor">
    1. Click: [Add Close to Cursor](https://cursor.com/en-US/install-mcp?name=Close\&config=eyJ1cmwiOiJodHRwczovL21jcC5jbG9zZS5jb20vbWNwIiwidHlwZSI6InN0cmVhbWFibGVIdHRwIn0%3D), or manually add the server URL `https://mcp.close.com/mcp` in Cursor's MCP Tools settings.

    2. You should see the Close MCP Server listed in **MCP Tools** in the Cursor desktop app. Click **Install**.

    ![Cursor MCP Tools showing Close server](https://files.buildwithfern.com/close.docs.buildwithfern.com/a16c179e0ba8f3881b4f09b38a093dd44035177e327e2171173973e657c04ae8/docs/pages/mcp/images/cursor-install.png)

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

    ![Cursor needs authentication](https://files.buildwithfern.com/close.docs.buildwithfern.com/502d78202d72d59215332ac3a375ff4144c4ec80391f8cefd179b3fbbc64742d/docs/pages/mcp/images/cursor-connect.png)

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

    ![Close OAuth page in Cursor](https://files.buildwithfern.com/close.docs.buildwithfern.com/f0c80bc8aba6ed4b1644b04adb5cf0330836485d68751393ccc7edd86f456198/docs/pages/mcp/images/cursor-oauth.png)

    5. Return to the Cursor app. You should see that the connection is now "Loading Tools" or "Enabled".

    ![Cursor showing Close MCP enabled](https://files.buildwithfern.com/close.docs.buildwithfern.com/5315943e13279c588419aba7bba717979526a1ebfe3ab46b3c1fa3304d87a0d2/docs/pages/mcp/images/cursor-enabled.png)
  </Accordion>

  <Accordion title="VS Code">
    ### Step 1: Configure the MCP server

    Add the following to your `settings.json`:

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

    ![Starting the Close MCP server in VS Code](https://files.buildwithfern.com/close.docs.buildwithfern.com/a25ab15743e6bbcddb6fba64e90f25e2aa66596b058deffa045c2e857e5fa629/docs/pages/mcp/images/vscode-start-server.png)

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

    ![VS Code console confirming server connection](https://files.buildwithfern.com/close.docs.buildwithfern.com/ca8afd369f972c800cf039a9eb1664216bc7415ee7115bf6f612ec23e480bc36/docs/pages/mcp/images/vscode-connected.png)

    ### 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.
  </Accordion>

  <Accordion title="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.
  </Accordion>
</AccordionGroup>

## FAQs

### Does Close MCP support SSE?

We currently don't support SSE, but please email [support@close.com](mailto: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](/mcp/tools) for the full list of tools available for each scope.