# Communicate Developer Docs MCP [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://communicate.so/mcp  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/communicate-developer-docs-mcp

## Description
Official public Streamable HTTP MCP for Communicate developer documentation. Three read-only tools retrieve the developer guide, OpenAPI summary and support contact. No account or API key required; no workspace or customer data access and no product actions. Documentation: https://communicate.so/developers

## Tools
Capabilities this server exposes over MCP:

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

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: medium). Install path inferred — verify against the README before running it. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "communicate-developer-docs-mcp": {
    "url": "https://communicate.so/mcp"
  }
}
```

## Documentation

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

_Full upstream README: https://allmcps.com/mcp/communicate-developer-docs-mcp/readme_

