Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

StateLode

by Statelodeversion 0.1.9i★ –iComputer or cloud
Registry namedev.statelode/statelode

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Computer or cloud
  • Transport: stdio, Streamable HTTP
  • Category: Docs, sheets & office work
  • You need to fill in: STATELODE_TOKEN, Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • You fill in yourself: STATELODE_TOKEN, Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • Runs in the cloudNothing to install; it connects over the internet
  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "statelode": {
      "command": "npx",
      "args": [
        "-y",
        "statelode-bridge"
      ],
      "env": {
        "STATELODE_TOKEN": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http statelode https://api.statelode.dev/mcp --header 'Authorization: your-value'

Or run it on your computer

claude mcp add statelode --env STATELODE_TOKEN=your-value -- npx -y statelode-bridge

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "statelode": {
      "url": "https://api.statelode.dev/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "statelode": {
      "command": "npx",
      "args": [
        "-y",
        "statelode-bridge"
      ],
      "env": {
        "STATELODE_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "statelode": {
      "type": "http",
      "url": "https://api.statelode.dev/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "statelode": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "statelode-bridge"
      ],
      "env": {
        "STATELODE_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • STATELODE_TOKEN secret required env
    StateLode workspace bearer token. Mint at app.statelode.dev.
  • Authorization secret HTTP header
    Optional. Leave unset to sign in with OAuth in the browser. For CI or headless use: Bearer from app.statelode.dev.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain statelode.dev (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Docs, sheets & office worki

  • More stars than 0% of the other 2167 servers in this category
  • Published to the registry more recently than 86% of the other 2167 servers in this category
  • Basic checks equal to or better than 100% of the other 2167 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is StateLode safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: STATELODE_TOKEN, Authorization

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.9) reached the registry 4 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Agent-Native Google Calendar - manage events, sync, and public booking

Runs in the cloud★ 7,620MITUpdated 2 months ago
Install

Excel MCP Server

by haris-musa

Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.

Runs on your computer★ 4,276MITUpdated 5 days ago
Install

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

Runs on your computer★ 847MITUpdated 3 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

Ask PopNx