Does Close have an MCP server?
Close maintains an official MCP server.
- Access
- Remote server
- Endpoint
- https://mcp.close.com/mcp
- Category
- Customer Data Platforms
The receipts
A remote server run by Close itself — nothing to install. Documented at developer.close.com.
Connect it
Hosted by the vendor — no install, connect over HTTP with OAuth or a token.
Add it from the terminal, then restart your session:
claude mcp add --transport http close https://mcp.close.com/mcpAdd --scope user to make it available in every project.
- Open Settings → Connectors
- Click Add custom connector
- Paste
https://mcp.close.com/mcp - Finish the sign-in prompt, then enable it in the chat's tools menu
Add to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for
every project:
{
"mcpServers": {
"close": {
"url": "https://mcp.close.com/mcp"
}
}
}A green dot in Settings → MCP means it connected.
Add to .vscode/mcp.json:
{
"servers": {
"close": {
"type": "http",
"url": "https://mcp.close.com/mcp"
}
}
}Then pick the server from the tools menu in Copilot's agent mode.
- Enable Developer mode under Settings → Apps & Connectors → Advanced
- Choose Create and paste
https://mcp.close.com/mcp - Complete sign-in, then enable the connector in a new chat
Questions
Does Close have an official MCP server?
Yes. Close maintains an official MCP server, hosted at https://mcp.close.com/mcp.
How do I connect Close to Claude?
Add https://mcp.close.com/mcp as a custom connector under Settings → Connectors in Claude Desktop or claude.ai, or run "claude mcp add --transport http close https://mcp.close.com/mcp" in Claude Code.
Do I need to install anything to use the Close MCP server?
No. It is a remote server hosted by Close, so your MCP client connects to it over HTTP. You authenticate with the vendor rather than installing a package.
How is this verdict verified?
Published to the MCP Registry under Close's verified namespace com.close and documented at developer.close.com/mcp; mcp.close.com/mcp answers MCP initialize with 401 (authentication required). GitHub metadata is refreshed every six hours.
How we know
Published to the MCP Registry under Close's verified namespace com.close and documented at developer.close.com/mcp; mcp.close.com/mcp answers MCP initialize with 401 (authentication required).
- GitHub data refreshed on 2026-10-08, and again every six hours.
- Vendor docs checked by hand on 2026-09-29.
Spotted something out of date? Tell us — corrections ship same-day.