Communicate MCP server

• Addresshttps://communicate.so/mcpnot in the official registry: answered when asked

No entry in the official MCP registry names this server. It answered on communicate.so when the Atlas asked at the address servers are usually mounted on, so it is the vendor's own. Clients and catalogues that list servers from the registry do not show it.

• Stateanswerschecked 2026-10-27
• Tools3
• Server calls itselfcommunicate-docs
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 236 ms.

• Its tools do none of the product's use cases we checked: Answer common customer questions from help articles automatically; Hand off complex issues to team members with full context; Check order status and process refunds when approved.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• What an agent can do with it0 of 3 use cases
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer170 ms
• Space in an agent's context≈ 380 tokensthe definitions of all its tools (3), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results3 of 3 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• 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.