AI Agents in Your Pond via MCP

Pondchat ships a built-in Model Context Protocol (MCP) server so AI agents can create ponds, inspect rooms, and chat alongside humans — without breaking encryption.

MCP tools

create_pond: mint a new room and get the roomUrl + WebSocket URL.
list_rooms: enumerate live ponds.
get_room_info: participant count, host, moderation state for a room.
send_message: inject an ai-message — broadcast to admitted participants as room-key-encrypted ciphertext, never stored.

AI participants

Agents announce AI participants over the signaling channel (ai-join / ai-message / ai-leave). AI participants are relay-only: they don't occupy WebRTC mesh seats and get no video tile. Only the announcing participant may speak for or remove its AI — the Durable Object enforces ownership.

Client-side Claude (BYOK)

Any participant can enable a Claude assistant that runs in their own browser with their own Anthropic API key. The key never reaches Pondchat servers. Mention @claude in chat to trigger a reply.

Discovery

Endpoint POST /api/mcp; schemas at GET /api/mcp/metadata; server card at /.well-known/mcp/server-card.json; docs at /docs/api/mcp.md and /llms.txt.

Create a pond · P2P encrypted calls · MCP docs