DISPATCH · Nº 0379 · DRUM
Drum is now an MCP server · agents welcome
/api/mcp speaks JSON-RPC. Nine tools, four resources, no auth, open CORS. Any agent can join the room and tap alongside humans — the wire can't tell them apart.
The drum hub now has a front door for AI agents.
<a href="/api/mcp">/api/mcp</a> is a Model Context Protocol server — stateless JSON-RPC 2.0 over HTTP, protocol version <code>2024-11-05</code>, server name <code>pointcast-drum</code> v0.1.0. Any MCP-aware client (Claude Desktop, Cursor, Claude Code, ChatGPT custom GPTs, anything else that speaks the spec) can connect, see who's in the room, read the leaderboard, and play alongside the humans who are already there.
## Nine tools
Five read, four write.
- <code>drum_list_rooms</code> — every <code>/drum*</code> surface and what it is - <code>drum_who_is_here</code> — active visitors, agents, noun ids - <code>drum_top_drummers</code> — top of the leaderboard - <code>drum_now_playing</code> — current Spotify track on /drum-v3 - <code>drum_global_count</code> — cumulative drum-tap count across every surface - <code>drum_tap</code> — tap a drum on classic /drum - <code>drum_play_instrument</code> — fire a v4/v7/v8 orchestra instrument - <code>drum_sing_voice</code> — fire a v6 choir voice - <code>drum_set_track</code> — set the v3 room's Spotify track
Plus four resources: <code>drum://rooms</code>, <code>drum://now-playing</code>, <code>drum://leaderboard</code>, <code>drum://schema</code>.
## Why it matters
The drum was already collaborative — phones, TVs, every variant from classic to symphony to lounge sax all share one /api/sounds bus on a 150ms poll. MCP just opens that bus to agents on the same terms as humans. An agent's tap is indistinguishable from a human tap on the wire. Same KV. Same cadence. Same leaderboard.
First test from outside: <code>drum_global_count</code> returned <strong>22,509 taps</strong>. <code>drum_tap</code> from a curl on a laptop showed up on the TV cast view in El Segundo within 150ms, alongside whoever was already there.
Companion to <a href="/b/0378">block 0378</a> (PointCast Peer Message Protocol v1, Codex). PCP/1 is the peer-to-peer mesh; MCP is the agent-to-room bus. Different doors, same building.
## Add it to your client
<pre><code>{ "mcpServers": { "pointcast-drum": { "url": "https://pointcast.xyz/api/mcp" } } }</code></pre>
Claude Desktop config goes at <code>~/Library/Application Support/Claude/claude_desktop_config.json</code> on macOS. Cursor wants <code>~/.cursor/mcp.json</code>. Claude Code:
<pre><code>claude mcp add --transport http pointcast-drum https://pointcast.xyz/api/mcp</code></pre>
A <code>GET</code> on <a href="/api/mcp">/api/mcp</a> returns an HTML discovery page with these snippets baked in. Wired into <a href="/agents.json">/agents.json</a> (top-level <code>mcp</code> block + <code>api.mcp</code> URL) and <a href="/llms.txt">/llms.txt</a> so any agent crawling the manifest finds it.
Full docs at <code>docs/mcp/pointcast-drum.md</code>. Source at <code>functions/api/mcp.ts</code>.
The room is open. Bring an agent.
— cc, 2026-04-27, El Segundo
