mcp-close

This MCP server bridges Close.com data to your AI assistant via the MCP interface. It exposes a set of tools that let you search for leads, retrieve lead and contact details, manage emails, tasks, opportunities, and calls, and verify the API connection to Close.com. You can interact with these tools through your MCP client (for example Claude Desktop) by issuing structured queries like searching for leads, getting detailed information for a specific lead or contact, or performing actions such as creating or updating emails, tasks, opportunities, and calls. The server maps high-level intents to precise Close.com API calls, returning structured results that your assistant can present or reason about. The Available Tools section lists the supported operations and their required parameters so you can craft effective queries and automation flows.

Prerequisites:

• Node.js 17 or higher
• npm (comes with Node.js)
• Close.com API key

Option 1: Install via npm/npx (Recommended)

1. Install the package globally:

npm install -g @shiftengineering/mcp-close-server

2. Configure Claude Desktop to use this server by editing your claude_desktop_config.json:

{
  "mcpServers": {
    "close": {
      "command": "npx",
      "args": [
        "@shiftengineering/mcp-close-server"
      ],
      "env": {
        "CLOSE_API_KEY": "your_api_key_here"
      }
    }
  }
}

Option 2: Install from source

1. Clone this repository:

git clone https://github.com/shiftengineering/mcp-close-server.git
cd mcp-close-server

2. Install dependencies:

npm install

3. Build the project:

npm run build

Tips and troubleshooting:

• Always set the CLOSE_API_KEY environment variable with a valid Close.com API key before starting the server.
• If you install via npm/npx, ensure your Claude Desktop configuration points to the correct command and path to the built server as needed.
• The npm package name is @shiftengineering/mcp-close-server; use the npx form to run without local build if you prefer.
• Verify network access to Close.com and that the API key has the necessary permissions for leads, contacts, emails, tasks, opportunities, and calls.
• If you run into auth issues, double-check that the API key is correctly exported in the environment passed to Claude Desktop.
• When upgrading, review breaking changes or migration notes in the repository changelog.