mcpbeat Sign in

Communicate MCP Server

answering

Communicate is answering right now. Last checked 12 min ago.

Read-only discovery of AI agents in your Communicate workspace.

Uptime history 16 days of history · worst day 98%
16 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
398 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Communicate missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add communicate --transport http https://app.communicate.so/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "communicate": {
      "url": "https://app.communicate.so/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.communicate]
url = "https://app.communicate.so/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "communicate": {
      "url": "https://app.communicate.so/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "communicate": {
      "url": "https://app.communicate.so/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://app.communicate.so/mcp streamable-http sign-in 335 ms 12 min ago

Alternatives to Communicate

same job, measured the same way
Plori
by plori

Plori runs AI agents in Workspaces.

answering
AI Workstation Open Source Intelligence
by zxhwolfe-dev

Read-only AI project discovery, verification, comparison, shortlisting, and stack planning.

9 tools answering
Seiche Agent Community
by beepboop2025

Free read-only discovery of owner-published finance agent profiles and source-linked discussions.

5 tools answering
MCP Oci
by dockndevai

Oracle Cloud discovery + Terraform generation for AI agents — read-only, secret-safe.

47 installs/wk local only
Liquid
by ertad-family

Connect your AI agent to anything — APIs, databases, and agents; read and write, auto-discovered.

91 installs/wk local only
gws-admin-mcp
by antct11

Safe Google Workspace admin for AI agents: read-only by default, confirm-gated deletes, audit log.

local only
Govenant Audit
by govenantstandard

Run the GOVENANT trust audit on your own AI agents — read-only, aggregate-only. Detects…

answering
Cartography
by datasynx

MCP-first read-only discovery of your infra & SaaS landscape as MCP resources, tools and prompts.

local only

Communicate — questions

Answers built from our own checks of this server.

Why is there no tool list for Communicate?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Communicate working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 398 ms. The bar chart above shows every period we have measured.
How do I connect Communicate?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Communicate?
No API key is involved. Communicate answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Communicate?
It answers our handshake in 398 ms on average, which is faster than 31% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.