# Close Crm [Health: Active]

**Category:** 👤 Customer Data Platforms  
**Repository:** https://github.com/pipeworx-io/mcp-close-crm  
**GitHub Stars:** 0  
**npm Downloads (last month):** 452  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/close-crm

## Description
Close CRM MCP Pack — wraps the Close (close.com) API v1.

## Tools
Capabilities this server exposes over MCP:

- **close_me** — Get the current Close user and organization for the supplied API key. Returns user ID, name, email, and the organizations (with IDs) the key can access. Use this to verify the key works and discover your organization context.
- **close_search_leads** — Search or list leads (companies/accounts in Close) using Close's query language. Returns a `data` array of leads (with id, display_name, contacts, status, custom fields) plus `has_more` and `total_results`. The `query` param accepts Close search syntax, e.g. `name:"Acme"`, `status_label:"Potential"`, `email_address:@example.com`, `lead_created_within:7d`, or free text. Omit `query` to list all leads. Page with `_limit` (max 200) and `_skip`.
- **close_get_lead** — Get a single lead by its Close lead ID (format `lead_...`). Returns full detail: display name, description, status, contacts, addresses, opportunities, custom fields, and timestamps.
- **close_list_opportunities** — List opportunities (pipeline deals) in Close. Returns a `data` array of opportunities with id, lead_id, status, value, currency, confidence, and expected close date, plus `has_more` / `total_results`. Pass `lead_id` to scope to one lead, or omit to list across the organization. Page with `_limit` / `_skip`.
- **close_list_contacts** — List contacts (people) in Close. Returns a `data` array of contacts with id, lead_id, name, title, emails, and phones, plus `has_more` / `total_results`. Optionally filter to one lead with `lead_id`. Page with `_limit` / `_skip`.
- **close_list_activities** — List activities for a lead — calls, emails, notes, SMS, meetings, and status changes. Returns a `data` array (with id, _type, type, date_created, and type-specific fields) plus `has_more` / `total_results`. Requires `lead_id`. Page with `_limit` / `_skip` to walk a lead's timeline.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "close-crm": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-close-crm"]
  }
}
```

## Documentation

## What Close Crm does

Close Crm exposes read-oriented access to Close CRM through MCP. The integration works with leads, contacts, opportunities, and activities, returning structured API data for use by an MCP-compatible client. Leads represent companies or accounts in Close, while contacts represent people associated with those leads.

The `close_me` tool checks the supplied Close API key and returns the authenticated user's ID, name, email, and accessible organizations. This makes it useful for confirming credentials and identifying the organization context before querying records.

## How it works

The integration can be used through the hosted Pipeworx endpoint at `https://gateway.pipeworx.io/close-crm/mcp`, or run locally as `@pipeworx/mcp-close-crm` over standard input and output. The hosted connection includes the Close tools plus shared Pipeworx meta-tools. The local process exposes only the Close pack's tools.

Close API credentials are passed as the `_apiKey` tool parameter. The hosted gateway does not provide a Close API key on the caller's behalf. Requests and responses use MCP operations such as `initialize`, `tools/list`, and `tools/call`.

A full Pipeworx gateway endpoint is also available at `https://gateway.pipeworx.io/mcp`. Both hosted URLs can reach Pipeworx's broader routing capability, but the pack endpoint lists the Close tools directly alongside the shared gateway tools.

## Setup and configuration

Add the hosted endpoint to an MCP client with a remote server configuration:

```json
{
  "mcpServers": {
    "close-crm": {
      "url": "https://gateway.pipeworx.io/close-crm/mcp"
    }
  }
}
```

For a local stdio connection, configure the package with `npx`:

```json
{
  "mcpServers": {
    "close-crm": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-close-crm"]
    }
  }
}
```

The package can also be started directly with `npx -y @pipeworx/mcp-close-crm`. Provide a valid Close API key through the relevant tool call using `_apiKey`.

## Tools and capabilities

- `close_search_leads` searches Close's lead index with query syntax such as name, status, email domain, creation period, or free text. It supports pagination with `_limit` up to 200 and `_skip`.
- `close_get_lead` retrieves one lead by its `lead_...` identifier, including contacts, addresses, opportunities, custom fields, status, and timestamps.
- `close_list_contacts` lists people across the organization or restricts results to a specified `lead_id`.
- `close_list_opportunities` lists pipeline deals across the organization or for one lead, including value, currency, confidence, status, and expected close date.
- `close_list_activities` walks a lead's timeline of calls, emails, notes, SMS, meetings, and status changes. It requires `lead_id` and supports pagination.

## Limitations and notes

The integration is unofficial and independent of Close. Its tools are focused on retrieving and inspecting CRM data; the listed capabilities do not include create, update, or delete operations. List responses include pagination metadata such as `has_more` and `total_results`, so clients should continue paging when a complete result set is needed.

_Full upstream README: https://allmcps.com/mcp/close-crm/readme_