Snapstate MCP Server

What the code does

We read the source, 13 h ago · rules 3dff92dd89df

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

  el.innerHTML = msg;

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add snapstate -- npx -y snapstate-sdk

{
  "mcpServers": {
    "snapstate": {
      "args": [
        "-y",
        "snapstate-sdk"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.snapstate]
command = "npx"
args = ["-y", "snapstate-sdk"]

{
  "mcpServers": {
    "snapstate": {
      "args": [
        "-y",
        "snapstate-sdk"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "snapstate": {
      "args": [
        "-y",
        "snapstate-sdk"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: SNAPSTATE_API_URL (SnapState API URL), SNAPSTATE_API_KEY (Your SnapState API key (starts with snp_)). The author declared them in the registry entry; get the values from the project itself.