Back to Browse

Statelode Bridge MCP Server

Developer ToolsLow Risk10.0MCP RegistryLocalRemote
Free

Server data from the Official MCP Registry

Shared task layer for AI coding agents. One MCP surface: task_search, task_get, task_mutate.

About

Shared task layer for AI coding agents. One MCP surface: task_search, task_get, task_mutate.

Remote endpoints: streamable-http: https://api.statelode.dev/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry.

Endpoint verified · Requires authentication · 2 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

StateLode workspace bearer token. Mint at app.statelode.dev.Required

Environment variable: STATELODE_TOKEN

How to Install & Connect

Available as Local & Remote

This plugin can run on your machine or connect to a hosted endpoint. during install.

Documentation

View on GitHub

From the project's GitHub README.

statelode-bridge

npm version npm downloads license MCP Registry

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 every IDE's repo guide file so the project is in context even without the global setup:

FileIDE
AGENTS.mdCodex, Cursor
CLAUDE.mdClaude Code
.github/copilot-instructions.mdVS Code (Copilot)
.cursor/rules/statelode.mdcCursor (project rule, alwaysApply)

Re-running is the refresh path: npx statelode-bridge@latest init rewrites every guide block with the latest rules (we add agent hints over time) and keeps this repo's existing pin — no need to pass the slug again. Use @latest so npx doesn't serve a cached older bridge. For the global block, re-run setup the same way. --no-agents writes only the marker.

Keep your token in STATELODE_TOKEN (or the MCP server config) — never in statelode.json or any of the guide files.

Reviews

No reviews yet

Be the first to review this server!