MCP server for Close — enables Claude to interact with Close data and workflows.
Add new capabilities to Claude beyond text generation
Example: Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example: Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example: Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Time estimate: 15-60 minutes depending on server complexity
Prerequisites
Gmail
MCP server for Gmail — enables Claude to interact with Gmail data and workflows.
Guru
MCP server for Guru — enables Claude to interact with Guru data and workflows.
Intercom
MCP server for Intercom — enables Claude to interact with Intercom data and workflows.
Clay
MCP server for Clay — enables Claude to interact with Clay data and workflows.
SimilarWeb
MCP server for SimilarWeb — enables Claude to interact with SimilarWeb data and workflows.
Slack
MCP server for Slack — enables Claude to interact with Slack data and workflows.
Close is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Strong directory entry: Close surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Close has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
According to our notes, Close benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Close is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
I recommend Close for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Strong directory entry: Close surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Close is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
We evaluated Close against two servers with overlapping tools; this profile had the clearer scope statement.
We wired Close into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
showing 1-10 of 30
Share your MCP server with the developer community
Select a client to integrate this server.
Claude Desktop configuration
{
"mcpServers": {
"close": {
"type": "http",
"url": "https://mcp.close.com/mcp"
}
}
}Close MCP server for Claude integration. Enables AI assistants to interact with Close data and workflows.
Close is an official MCP server included in Anthropic's knowledge-work-plugins repository. It enables Claude to interact with Close through the Model Context Protocol. Protocol: HTTP. Endpoint: https://mcp.close.com/mcp. Used in plugins: sales.
Add the following to your .mcp.json file to connect Claude to Close. No local installation required — this is a remote HTTP server.
README content is unavailable from source data for this server.
Open GitHub repository →Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.