← All servers

Communicate Developer Docs

warnings

communicate.so

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

https://communicate.so/mcpWebsiteOAuthMCP 2025-11-25v1.0.0last checked 1 Oct 2026spoke MCP on 1 of 1 check (30 days)initialize in 381 ms

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✕Claude CodeNot supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

Claude Code docs · read on 2026-08-30

✕Claude (claude.ai & Desktop)Not supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✕ChatGPTNot supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

ChatGPT docs · read on 2026-08-30

✕CursorNot supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

Cursor docs · read on 2026-08-30

✕VS Code (Copilot)Not supported

The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 1 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	OAuth
Issuer	https://app.communicate.so/api/v1
Dynamic client registration	✕Not advertised A client that cannot register itself needs credentials issued out of band before it can begin the flow.
Client ID Metadata Document	✕Not advertised
PKCE	✕None advertised MCP requires S256; a client that implements only that has no method in common with this server.
Grant types	client_credentials
Scopes	agents:read, chat:write
Protected-resource metadata	✓Published (RFC 9728)
Anonymous access	Handshake succeeds; 3 tools listable
Documentation	https://communicate.so/developers

What the probe found

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

3 tools usable without signing in

The server exposes a public surface before authorization: communicate_get_developer_guide, communicate_get_openapi_summary, communicate_get_support_contact.

Tools

communicate_get_developer_guidecommunicate_get_openapi_summarycommunicate_get_support_contact

Contract history

1 Oct 2026v1.0.0first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Own this server?

Sign in to claim this listing by proving control of its host.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/communicate-developer-docs/badge.svg)](https://mcpi.app/servers/communicate-developer-docs)