Intercom vs Docs MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Intercom vs Docs MCP
In-depth architectural comparison of the Intercom and Docs MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Intercom
Communication · Local stdio
Quality: 48/100 (Fair) | Auth: No auth required
Docs MCP
Communication · Remote HTTP/SSE
Quality: 84/100 (Excellent) | Auth: No auth required
Verdict Summary: Choose Intercom if you need specialized Communication tools running via a local process. Choose Docs MCP if your workspace requires Communication integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Intercom when:
You need dedicated capabilities in the Communication domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Relays messages between two Claude Code sessions on different machines using the Channels API
CometChat's official MCP server — searches CometChat documentation and returns curated implementation bundles for adding real-time chat, voice, video, and moderation to your app (React, React Native, Flutter, iOS, Android, JS SDK).
Category & Scope
Tools & Capabilities Breakdown
Intercom Tools (2)
send_message
Sends a message and returns immediately with an **id**. It does not wait for an answer — the reply arrives later as its own inbound message.
check_message
Answers the question a fire-and-forget channel otherwise can't: is this reply slow, or is it never coming? Pass an `id`, or omit it to list everything outstanding.
Docs MCP Tools (4)
search_cometchat_docs
Search across SDK guides, UI Kit references, REST API documentation, and OpenAPI specs. Returns ranked snippets with titles + direct links. Optional `version` filter.
fetch_cometchat_doc_page
Fetch the full content of any documentation page as markdown by URL or relative path.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Intercom is categorized under Communication and uses a local stdio subprocess. In contrast, Docs MCP belongs to Communication using remote streaming HTTP/SSE transport. Select Intercom when you need capabilities focused on communication and Docs MCP when you require tools for communication.