The Close MCP Server (Community), built by bcharleson (Community), provides close does not publish an official Model Context Protocol server — a `closeio/mcp-server` repo does not exist. It is community-built and best for API & Web.
by bcharleson (Community)
About
Close does not publish an official Model Context Protocol server — a `closeio/mcp-server` repo does not exist. The strongest real option is bcharleson/close-crm-cli, a TypeScript CLI-and-MCP-server hybrid that exposes Close's full REST API (160+ commands across 30 resource groups: leads, contacts, opportunities, tasks, calls, notes, emails, SMS, meetings, pipelines, custom fields, webhooks, outreach sequences, smart views, and analytics reports) both as terminal commands and as MCP tools. Run `close mcp` to start the server, or wire it into Claude Desktop / Cursor / Windsurf via `npx close-crm-cli mcp` with a `CLOSE_API_KEY` env var (generated from Close's Settings → API page). HTTP Basic Auth, offset-based pagination, and automatic exponential-backoff retry on 429/5xx are all handled for you, and JSON output is the default so responses pipe cleanly into an agent or `jq`. Typical use: ask Claude to "list my open opportunities in the demo-scheduled stage" or "log a call and create a follow-up task" without leaving the chat. Not an official Close product — early-stage community project, so expect rough edges and verify write operations before relying on them in production pipelines.
Trust verdict
How grades are computed →Grade A (94/100, reliable) from 1 measured signal, based on repository evidence. Only one signal stands behind it, so treat the grade as provisional.
What was measured
- Repository maintenance100/100 · weight 20
The repository has been pushed to or released within the last six months. — last push 2026-03-13.
- Source verification100/100 · weight 25
The repository URL was confirmed to resolve against the live GitHub API and is not archived.
- Provenance65/100 · weight 10
Community-built. That is not a mark against it — most of the ecosystem is community-built — but there is no vendor accountable for keeping it working.
- Listing ↔ repository match100/100 · weight 5
The listing name lines up with the linked repository bcharleson/close-crm-cli.
What could not be measured
These contributed nothing to the score — not a penalty, not a zero. They are why the confidence reads the way it does.
- Live MCP handshakeunknown
No remote endpoint to handshake — this server installs and runs locally over stdio, so there is nothing to probe from the outside.
- Measured uptimeunknown
No probe history recorded for this server yet.
- Tool-schema stabilityunknown
Drift is a difference between two successive checks, and this server has none recorded.
Installation
npx close-crm-cli mcpclose-crm-cli confirmed live on the npm registry — checked August 17, 2026.
Categories
Frequently Asked Questions
What is Close MCP Server (Community)?
Who built Close MCP Server (Community)?
Is Close MCP Server (Community) free?
How do I install Close MCP Server (Community)?
What does Close MCP Server (Community) integrate with?
Repo Health
Local/stdio install — runs on your machine, so there is no remote endpoint to verify live. Trust signal below is from the source repo.
- Last commit
- 6mo ago
- Install
- npm
- Package
- close-crm-cli
Quick Info
- Install Type
- npm
- Author
- bcharleson (Community)
- Categories
- 3
- Integrations
- 5
Related Servers
Fetch
Web content fetching and conversion for efficient LLM usage. Extract readable content from any URL.
Time
Time and timezone conversion capabilities for AI assistants.
21st.dev Magic
Create crafted UI components inspired by the best 21st.dev design engineers.
Apify MCP Server
The Apify MCP server gives AI agents access to 6,000+ ready-made cloud scrapers, crawlers, and automation tools on the Apify Store — no infrastructure required. Connect to Apify Actors that extract data from social media platforms (Instagram, TikTok, LinkedIn), search engines (Google, Bing), e-commerce sites (Amazon, eBay), maps (Google Maps), and virtually any website. Each Actor runs in the cloud with managed proxies, browser fingerprinting, and anti-bot bypass built in. Use the Apify MCP server to query Actors by task, stream results directly into your AI context, run custom scraping Actors from your Apify account, and chain multiple data extraction steps in a single workflow. Supports tool filtering to expose only the Actors you need, and integrates with Apify's RAG web browser Actor for retrieval-augmented generation use cases.
Browserbase MCP Server
Browserbase MCP and Stagehand MCP are the same server under two names, and this catalog lists both because people search for both — this page is the platform view, /servers/stagehand covers the natural-language automation layer that runs inside it. What Browserbase supplies is the browser itself: a headless Chrome session running in Browserbase's cloud rather than on the machine your agent is on, which is the reason to use it at all. The session is a real, addressable browser with its own residential-proxy and stealth configuration and a recorded replay you can watch afterwards, so an agent's browsing survives being run from a datacenter IP, and a failed run is debuggable after the fact instead of being a black box. Nothing renders on the developer's machine, so a long-running agent is not tied to a desktop staying awake. Browserbase's recommendation is the hosted server at https://mcp.browserbase.com/mcp over streamable HTTP — they operate it and absorb the model inference that the instruction-following tools require. Clients without HTTP transport connect via npx mcp-remote https://mcp.browserbase.com/mcp. Self-hosting installs @browserbasehq/mcp-server-browserbase from npm and needs BROWSERBASE_API_KEY and BROWSERBASE_PROJECT_ID from your dashboard. Six tools are exposed — start and end for session lifecycle, navigate, act, observe and extract — and they are documented in detail on the Stagehand entry, because the act/observe/extract trio is Stagehand's model rather than Browserbase's. One thing to know before self-hosting: the browserbase/mcp-server-browserbase repository was archived on 2026-07-20 and its README now says it is kept for historical reference and should not be read as representative of the current production service. The npm package still installs and the star count on this page belongs to that archived repo; the hosted endpoint is the path Browserbase actually maintains.
Sponsored
Better Stack
Free PlanGet alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.
Start monitoring free →