Developer · Remote MCP server
Communicate Developer Docs
Read-only access to Communicate developer guides, OpenAPI summaries, and support contact.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.uditgoenka/communicate-docs- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-10-01
- Updated
- 2026-10-01
- Publisher
- uditgoenka (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/uditgoenka) · how
- Listed under
- OpenAPI MCP servers
- Website
- communicate.so/developers
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://communicate.so/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- communicate-docs 1.0.0 · protocol 2025-06-18
- Tools discovered
- 3:
communicate_get_developer_guide,communicate_get_openapi_summary,communicate_get_support_contact - Checked on
- 2026-10-05
How to connect Communicate Developer Docs
Communicate Developer Docs is a remote MCP server: there is nothing to install. Its endpoint is https://communicate.so/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| CombinedQuery synced business data with scoped, read-only SQL and freshness through MCP. | Remote · HTTP |
| ComiceditorialComic publishing for coding agents. Comics, chapters, AI panels, CBZ export. stdio + remote SSE. | Remote & Local · SSE, stdioLive check: ✓ SSE reachable |
| CommercialDiscover DigitalPublic plans, trust, ROI, status and autonomous Sandbox enrollment for AI agents. | Remote · HTTPLive check: ✓ handshake |
| Commit - Supply Chain Risk ScoringSupply chain risk scoring for npm, PyPI, Cargo, and Go. 9 tools. Behavioral signals. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| ComOS FederationMulti-tenant MCP gateway for AI commerce. One connection, every store. | Remote · HTTPLive check: ✓ handshake |
| ComOS Federation GatewayMulti-tenant MCP gateway for AI commerce. One connection, every store. | Remote · HTTPLive check: ✓ handshake |
| ComOS Federation GatewayMulti-tenant MCP gateway for AI commerce. One connection, every store. | Remote · HTTPLive check: ✓ handshake |
| CompactPromptReview and compact prompts, docs, and AI-agent skills to save tokens, preserving structure. | Local · stdio |