statelode-bridge

statelode-bridge

statelode-bridge lets stdio-first MCP clients talk to StateLode's hosted Streamable HTTP MCP endpoint.

npx statelode-bridge --token statelode_live_...

Prefer environment variables in checked-in IDE config:

STATELODE_TOKEN=statelode_live_... npx statelode-bridge

The bridge forwards newline-delimited JSON-RPC from stdio to POST /mcp, keeps the Mcp-Session-Id header in sync, and relays GET /mcp server-sent events back to stdio as JSON-RPC notifications.

Teaching agents to use StateLode

Different IDEs auto-load different instruction files, so the bridge writes the StateLode rules where each agent will actually see them. There are two commands.

setup — once per machine

npx statelode-bridge setup        # add --dry-run to preview

Installs a global StateLode protocol into each installed IDE's global instruction file — ~/.claude/CLAUDE.md (Claude Code), ~/.codex/AGENTS.md (Codex), ~/.codeium/windsurf/memories/global_rules.md (Windsurf) — and prints a block to paste into the IDEs that keep global rules in app settings (Cursor → User Rules; VS Code → Copilot instructions). It only touches IDEs that are installed, and upserts a delimited block so it never clobbers your existing rules.

After setup, any agent:

• uses a repo's StateLode project when the repo has a statelode.json, and
• offers to set one up (with your permission) when it doesn't — so you don't have to initialize every project up front.

init — pin one repo to a project

npx statelode-bridge init <project-slug>   # defaults to the directory name

Writes statelode.json (the marker that maps this repo to a StateLode project) and a ## StateLode block into both AGENTS.md (Codex / Cursor) and CLAUDE.md (Claude Code) so the project is in context even without the global setup. Re-run after a project rename to refresh the block; --no-agents writes only the marker.

Keep your token in STATELODE_TOKEN (or the MCP server config) — never in statelode.json, AGENTS.md, or CLAUDE.md.