StateLode

dev.statelodePublished by statelode.devOfficial publisherv0.1.9Updated Nov 3, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

StateLode's hosted MCP server (api.statelode.dev), published by statelode.dev; OAuth sign-in or API key required; Streamable HTTP.

No AI overview yet: these facts come from the registry entry and the server itself.

Publisher
statelode.dev
Endpoint
api.statelode.dev
Last checked

Installation

In SourceWeft

  1. Open StateLode in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.statelode%2Fstatelode/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "statelode": {
      "type": "http",
      "url": "https://api.statelode.dev/mcp"
    }
  }
}

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.

bash
npx statelode-bridge --token statelode_live_...

Prefer environment variables in checked-in IDE config:

bash
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

bash
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

bash
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.

Source: README.md at commit 9bf4dea

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.1.9LatestNov 3, 2026
  2. v0.1.1Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts