data-ai MCP Server
Peer-to-peer chat substrate that lets multiple Claude Code instances share the same context.
Discovered via github-topic:mcp and last synced 3mo ago.
Install instructions not detected yet
Check the source repository for the latest setup steps.
Action
Last N chat lines from this room's log
Behaviour
Share a local file with peers (iroh-blobs)
Broadcast a chat message into your room
Copy the active tab's ticket to clipboard
Block until someone @-mentions this Claude (or a timeout)
What it gives you
Same as `cc_send`, but with `@<nick>` prefix
New tab → paste a ticket to join
Files dropped into the room (with local paths)
Quit; host daemons stay alive
Bare-bones REPL-only joiner (no TUI). Mostly useful for protocol smoke tests. Prefer `room join`.
Reverse `install.sh` entirely: stop daemons, strip the hook + MCP entries, remove `~/.local/bin` symlinks. `--purge` also wipes `~/.cc-connect/`, `/tmp/cc-connect-$UID/`, and stale `~/.claude/*.json.bak.*` backups.
Close tab (if you started the host daemon, prompts to also stop it)
Overwrite this room's rolling summary (auto-injected on every prompt)
Same shape as `host-bg`, but for chat-session daemons (the gossip + chat.sock side; only matters in the multiplexer path).
Same shape, chat-daemon side. Don't run directly.
What it does
What it does
Tag pattern
Likely cause
auto` to get the richer Bun + React + Ink chat panel, that path still works. --- ## Command reference `claude` (asking it to call the MCP tools) is the only entry point you need day-to-day. Everything below is supporting / management / debug surface. ### Day-to-day human-side commands