Summary
Wraps the Close CRM API v1 through Pipeworx's gateway infrastructure, giving Claude direct access to your sales pipeline data. The server doesn't list specific tools in the docs, but Close's API typically covers leads, contacts, opportunities, activities, and reporting. Useful when you want to query deal status, update contact records, or pull sales metrics without leaving your AI workflow. Runs as a hosted service over streamable HTTP, so no local setup required. You can connect to just the Close integration or use the full Pipeworx gateway to access 673+ data sources through a single connection. The ask_pipeworx natural language interface lets you query in plain English rather than calling structured tools directly.
Plug Mailtrap into your AI workflow and let it handle the email.
Connect Mailtrap MCP →
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →
Make coding agent sessions - Searchable, Shareable, Vendor-neutral & Scored.
Try For Free →
Your agent targets a perfect 10 Code Health score. Deterministic. Every commit.
Try For Free →
Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →
belt cli automatically finds the best tools and skills for your agent. image, video, music, tts...
one prompt install →
mcp-close-crm
Close CRM MCP Pack — wraps the Close (close.com) API v1.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
Tools
| Tool | Description |
|---|---|
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. |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"close-crm": {
"url": "https://gateway.pipeworx.io/close-crm/mcp"
}
}
}
What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/close-crm/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Close Crm data" })
The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Featured
Plug Mailtrap into your AI workflow and let it handle the email.
Connect Mailtrap MCP →Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →Make coding agent sessions - Searchable, Shareable, Vendor-neutral & Scored.
Try For Free →Your agent targets a perfect 10 Code Health score. Deterministic. Every commit.
Try For Free →Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →belt cli automatically finds the best tools and skills for your agent. image, video, music, tts...
one prompt install →Categories
Registryactive
TransportHTTP
UpdatedJun 1, 2026
