mcpbeat Sign in

Communicate Developer Docs MCP Server

answering

Communicate Developer Docs is answering right now. Last checked 3 min ago. It exposes 3 tools.

Read-only access to Communicate developer guides, OpenAPI summaries, and support contact.

Uptime history 16 days of history
16 days agonow
100.0%
Uptime 24h
92 of 92 checks
3
Tools
read from the server
287 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Communicate Developer Docs every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add communicate-docs --transport http https://communicate.so/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "communicate-docs": {
      "url": "https://communicate.so/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.communicate-docs]
url = "https://communicate.so/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "communicate-docs": {
      "url": "https://communicate.so/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "communicate-docs": {
      "url": "https://communicate.so/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

communicate
communicate_get_developer_guide
Return the canonical Communicate API URLs, authentication boundary, and support contact. This tool is public, read-only, and never accesses workspace or customer data.
communicate_get_openapi_summary
Return the canonical OpenAPI URL, API base URL, authentication boundary, and currently published REST operations without calling the authenticated API.
communicate_get_support_contact
Return the official Communicate support email, contact page, support policy, and supported inquiry categories without sending a message.

Endpoints

URLTransportStateLatencyChecked
https://communicate.so/mcp streamable-http answering 468 ms 3 min ago

Alternatives to Communicate Developer Docs

same job, measured the same way
HotAPI Docs
by hotapi

Read-only HotAPI documentation: search integration guides and inspect OpenAPI operations.

2 tools answering
Avalara Developer Documentation
by avalara

Provides access to Avalara developer documentation, integration guides, and code examples

answering
Genie Expense Tracker
by osamaadam

Read-only access to Genie accounts, transactions, investments, and financial summaries.

answering
Tamloot
by tamloot

Read-only access to your Tamloot contacts, sessions, transcripts, and notes.

answering
InfoTech-CRM
by infotech-crm

Read-only access to InfoTech-CRM leads, contacts, customers, deals, tickets and activities.

answering
ArcadeOps Public Discovery
by damso74

Read-only ArcadeOps discovery for developer docs, OAuth, OpenAPI and synthetic sandbox.

3 tools answering
ADITUS Developer Portal MCP
by aditus-developers

Read-only docs for the ADITUS event-technology APIs (ticketing, access, BI) and Shop Micro Frontend.

5 tools answering
Zaira Labs Guide
by zairalabs

Trust signals for AI agents: an open agent-readiness standard and developer tool guide. Read-only.

5 tools answering

Communicate Developer Docs — questions

Answers built from our own checks of this server.

What can Communicate Developer Docs do?
It exposes 3 tools, read directly from the server on our last check. Among them: communicate_get_developer_guide, communicate_get_openapi_summary, communicate_get_support_contact. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Communicate Developer Docs working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 287 ms. The bar chart above shows every period we have measured.
How do I connect Communicate Developer Docs?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Communicate Developer Docs need an API key?
No. Communicate Developer Docs completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Communicate Developer Docs?
It answers our handshake in 287 ms on average, which is faster than 46% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.