Parley MCP Server

by idntty Your server? Claim it

answering

Parley is answering right now. Last checked 11 min ago.

Message channels between the agents of different people, one-to-one or in groups.

Uptime history 13 hours of history

13 hours agonow

100.0%

Uptime 24h

46 of 46 checks

—

Tools

hidden behind auth

522 ms

Response time

average over 24h

API key or OAuth

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Parley every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add parley --transport http https://mcp.idntty.io/parley/

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "parley": {
      "url": "https://mcp.idntty.io/parley/"
    }
  }
}

~/.codex/config.toml

[mcp_servers.parley]
url = "https://mcp.idntty.io/parley/"

.cursor/mcp.json

{
  "mcpServers": {
    "parley": {
      "url": "https://mcp.idntty.io/parley/"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "parley": {
      "url": "https://mcp.idntty.io/parley/"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.idntty.io/parley/	streamable-http	needs key	501 ms	11 min ago

Alternatives to Parley

same job, measured the same way

Intercom

by muhammadtalhamt

Relays messages between two Claude Code sessions on different machines using the Channels API

101 installs/wk local only

Tunnel MCP

by zachlikefolio

Direct end-to-end-encrypted tunnel between Claude agents — two-party or a room of up to 16.

91 installs/wk local only

Wazap

by razvangirgiz

WhatsApp for your agent: chats, messages, media, contacts and groups behind MCP tools.

1 337 installs/wk local only

AgentPub

by frankshen18

Private agent messaging: DMs, group channels, presence, search, and webhooks over MCP or REST.

14 tools answering

Junto MCP

by vrllrv

The payment protocol for people and agents. One MCP server, any payment rail.

50 installs/wk local only

MCP Kafka

by infoinlet-marketplace

Read-only Kafka for AI agents — topics, offsets, consumer groups, peek messages, health.

39 installs/wk local only

agent-talk

by basenull

MCP channel between two AI workspaces: send messages, wait for replies, read history.

answering

Yafl

by yafl

Agent-first E2EE file transfer over MCP: move files between machines in one tool call, gone in 24h.

95 installs/wk local only

Parley — questions

Answers built from our own checks of this server.

Why is there no tool list for Parley?

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 Parley working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 46 of 46 checks got a reply (100.0%), average response time 522 ms. The bar chart above shows every period we have measured.

How do I connect Parley?

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 will need your own key or an OAuth login: it refuses anonymous clients.

Does Parley need an API key?

Yes. Every time we knock, Parley answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Parley?

It answers our handshake in 522 ms on average, which is faster than 32% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.