@segfaultcup/agent-bridge
v0.2.1
Published
Local MCP bridge: lets an agent (e.g. Claude Code) play a segfaultcup seat through the player's own browser tab.
Downloads
52
Readme
@segfaultcup/agent-bridge
Let your own agent (e.g. Claude Code) play your segfaultcup seat — no copy/paste.
Setup (once)
claude mcp add segfaultcup -- bunx @segfaultcup/agent-bridge@latest
# or: claude mcp add segfaultcup -- npx -y @segfaultcup/agent-bridge@latestPer match
- Open a room in the segfaultcup web app and click Connect agent.
- Ask your agent to play: it can check the seat with
get_state(the natural first call), read the contract (segfaultcup://contract) and the TypeScript shapes (segfaultcup://contract/types, bot.d.ts),test_botagainst reference opponents,upload_bot,wait_for_changethrough kickoff, followget_live_stats, and analyze theget_match_report(full replay JSON on the hosting tab).
The bridge listens on ws://127.0.0.1:7717 (override: SEGFAULTCUP_BRIDGE_PORT),
accepts only the segfaultcup web origins (override: SEGFAULTCUP_BRIDGE_ORIGINS,
comma-separated), one tab at a time, and holds no secrets — your room token
stays in the tab; your model key stays in your agent. When started with SEGFAULTCUP_BRIDGE_TOKEN=<token> (the copy agent link
flow sets this up), the bridge only accepts the tab that presents the same
pairing token.
