Communicate Developer Docs MCP logo

Communicate Developer Docs MCP

Public Streamable HTTP MCP endpoint for retrieving Communicate API documentation, OpenAPI details, and support information.

Install Communicate Developer Docs MCP

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://communicate.so/mcp

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Hosted endpointLive · 3d agoLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 3d ago · Nov 13, 2026, 16:30 UTC

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://communicate.so/mcp

Overview

Communicate Developer Docs MCP MCP server exposes Communicate’s public developer documentation through three read-only tools over Streamable HTTP. It returns the developer guide, OpenAPI summary, or official support details without calling authenticated APIs. No account or API key is required, and it does not access workspace or customer data. Use it when an agent needs current Communicate API references or support-routing information.

Use cases

  • Look up canonical Communicate API URLs
  • Inspect the published OpenAPI REST operations
  • Check Communicate authentication boundaries
  • Find official support channels and inquiry categories

Key features

  • Streamable HTTP MCP endpoint
  • Three read-only documentation tools
  • Developer guide retrieval
  • OpenAPI summary retrieval
  • Support contact and policy retrieval
  • No account or API key required

Tools3

What Communicate Developer Docs MCP lets your agent do. Expand a tool for its parameters.

Verified live~345 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

9/9 checks healthy over the last 45d

What it can do

From the 3 tools this server returned when we ran it.

Makes network requests · 1Read-only tools · 3

Observed 2026-10-16 in an isolated sandbox. A description of reach, not a security audit.

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

MaintenanceActively maintainedStatus declared by the project or listing owner.
Availability100%Our rolling endpoint + install checks that succeeded.
Tools exposed3Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Communicate Developer Docs MCP works

What Communicate Developer Docs MCP MCP server does

Communicate Developer Docs MCP provides a public MCP endpoint for reading selected parts of Communicate’s developer documentation. It is intended for agents that need API reference information without access to a Communicate account, workspace, customer records, or product actions.

The Communicate Developer Docs MCP MCP server exposes three read-only operations. One returns the canonical developer guide details, another describes the published OpenAPI reference and REST surface, and the third provides official support contact information. None of these operations sends a support request or invokes an authenticated Communicate API.

How it works

Clients connect to the public Streamable HTTP MCP endpoint published at https://communicate.so/mcp. After connection, an agent can call one of the available tools and receive documentation-related information from Communicate.

The guide tool returns canonical API URLs, explains the authentication boundary, and identifies the support contact. The OpenAPI tool returns the canonical OpenAPI URL, the API base URL, the authentication boundary, and the REST operations currently published in the documentation. The support tool returns the official support email, contact page, support policy, and supported inquiry categories.

Because the endpoint is read-only, it is suitable for answering documentation and routing questions, but not for changing Communicate configuration, sending messages, or retrieving workspace data.

Setup and configuration

Connect an MCP-compatible client to https://communicate.so/mcp using Streamable HTTP.

The public documentation site is available at https://communicate.so/developers. The MCP endpoint and documentation site serve reference content; the server does not provide authenticated access to Communicate’s REST API.

Tools and capabilities

  • communicate_get_developer_guide: Retrieves canonical API URLs, the authentication boundary, and the support contact.
  • communicate_get_openapi_summary: Retrieves the canonical OpenAPI URL, API base URL, authentication boundary, and currently published REST operations without calling the authenticated API.
  • communicate_get_support_contact: Retrieves the official support email, contact page, support policy, and supported inquiry categories without sending a message.

The Communicate Developer Docs MCP MCP server therefore fits documentation lookup, API-discovery, and support-routing workflows. It should not be selected for workflows that require data access or product mutations.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Communicate Developer Docs MCP

Communicate Developer Docs MCP is an MCP server that connects clients to Communicate’s public developer documentation over Streamable HTTP. Its main tools retrieve the developer guide, OpenAPI summary, and support contact details. The server is read-only, requires no account or API key, and does not access workspace or customer data.

Connect your MCP client to `https://communicate.so/mcp` using Streamable HTTP. Client-specific installation steps are not provided.

It provides three read-only tools: `communicate_get_developer_guide`, `communicate_get_openapi_summary`, and `communicate_get_support_contact`. They return API URLs and authentication details, the published OpenAPI and REST summary, and official support information respectively.

No, it cannot access workspace or customer data. The endpoint only returns public documentation and support information, and it does not perform product actions, call the authenticated API, or send support messages.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewCommunicate Developer Docs MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/communicate-developer-docs-mcp?style=directory)](https://allmcps.com/mcp/communicate-developer-docs-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/communicate-developer-docs-mcp"><img src="https://allmcps.com/api/badge/communicate-developer-docs-mcp?style=directory" alt="Communicate Developer Docs MCP on AllMCPs" /></a>