mcpbeat Sign in

Sidclaw Governance MCP Server

local only

Sidclaw Governance MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 67 installs a week from npm. Last commit 25 Sep 2026.

Governance proxy for MCP servers — policy evaluation, human approval, audit trails.

Installs per day peak 24 · avg 7 · +91% w/w
a month agotoday
67
Installs / week
npm · @sidclaw/sdk
15
Stars
1 open issue
25 Sep 2026
Last commit
no releases in 90 days
Apache-2.0
License
TypeScript

What the code does

We read the source, 3 d ago · rules 995398eba69f

In the project's build, not in the package

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.

Runs an external command packages/sidclaw-demo/cli.mjs:36
    const child = spawn(opener[0], opener[1], { detached: true, stdio: 'ignore' });
Sends data to a third-party sink apps/api/src/routes/integrations/telegram.ts:136
  await fetch(`https://api.telegram.org/bot${botToken}/answerCallbackQuery`, {
Secret passed into the image build apps/landing/Dockerfile:23
ENV NEXT_PUBLIC_CF_BEACON_TOKEN=$NEXT_PUBLIC_CF_BEACON_TOKEN
Touches key and credential files hooks/sidclaw_agent_intel/bash_classifier.py:141
    ("/etc/shadow", re.compile(r"/etc/shadow\b")),

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

Nothing serious here today

Today is the operative word: we check Sidclaw Governance MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

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.

run in your terminal
claude mcp add sidclaw-governance-mcp -e 'SIDCLAW_API_KEY=<SIDCLAW_API_KEY>' -e 'SIDCLAW_AGENT_ID=<SIDCLAW_AGENT_ID>' -e 'SIDCLAW_UPSTREAM_CMD=<SIDCLAW_UPSTREAM_CMD>' -e 'SIDCLAW_UPSTREAM_ARGS=<SIDCLAW_UPSTREAM_ARGS>' -- npx -y @sidclaw/sdk
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "sidclaw-governance-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@sidclaw/sdk"
      ],
      "env": {
        "SIDCLAW_AGENT_ID": "<SIDCLAW_AGENT_ID>",
        "SIDCLAW_API_KEY": "<SIDCLAW_API_KEY>",
        "SIDCLAW_UPSTREAM_ARGS": "<SIDCLAW_UPSTREAM_ARGS>",
        "SIDCLAW_UPSTREAM_CMD": "<SIDCLAW_UPSTREAM_CMD>"
      }
    }
  }
}
~/.codex/config.toml
[mcp_servers.sidclaw-governance-mcp]
command = "npx"
args = ["-y", "@sidclaw/sdk"]
env = { SIDCLAW_API_KEY = "<SIDCLAW_API_KEY>", SIDCLAW_AGENT_ID = "<SIDCLAW_AGENT_ID>", SIDCLAW_UPSTREAM_CMD = "<SIDCLAW_UPSTREAM_CMD>", SIDCLAW_UPSTREAM_ARGS = "<SIDCLAW_UPSTREAM_ARGS>" }
.cursor/mcp.json
{
  "mcpServers": {
    "sidclaw-governance-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@sidclaw/sdk"
      ],
      "env": {
        "SIDCLAW_AGENT_ID": "<SIDCLAW_AGENT_ID>",
        "SIDCLAW_API_KEY": "<SIDCLAW_API_KEY>",
        "SIDCLAW_UPSTREAM_ARGS": "<SIDCLAW_UPSTREAM_ARGS>",
        "SIDCLAW_UPSTREAM_CMD": "<SIDCLAW_UPSTREAM_CMD>"
      }
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "sidclaw-governance-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@sidclaw/sdk"
      ],
      "env": {
        "SIDCLAW_AGENT_ID": "<SIDCLAW_AGENT_ID>",
        "SIDCLAW_API_KEY": "<SIDCLAW_API_KEY>",
        "SIDCLAW_UPSTREAM_ARGS": "<SIDCLAW_UPSTREAM_ARGS>",
        "SIDCLAW_UPSTREAM_CMD": "<SIDCLAW_UPSTREAM_CMD>"
      }
    }
  }
}

Put your own values in place of <SIDCLAW_API_KEY> (SidClaw API key for policy evaluation and audit logging), <SIDCLAW_AGENT_ID> (Agent identity for policy matching and audit trails), <SIDCLAW_UPSTREAM_CMD> (Command for the upstream MCP server (e.g., npx)), <SIDCLAW_UPSTREAM_ARGS> (Comma-separated args for the upstream MCP server). The author’s registry entry marks them as required.

Optional settings from the registry entry, left out of the block above: SIDCLAW_APPROVAL_MODE (Approval mode: error (default, returns immediately) or block (waits for approval)).

Alternatives to Sidclaw Governance MCP

same job, measured the same way
mcp-airlock
by shalimov04

Governance proxy for MCP servers: allowlist, forced dry run, human confirmation, blast radius, audit

137 installs/wk local only
Sovereign Gateway
by mattijsmoens

Gating proxy for MCP servers: policy, verification and one audit trail across upstreams.

114 installs/wk local only
Mova Flat Runner
by mova-compact

Governed AI workflows with human approval gates and audit trails for Claude and MCP clients.

57 installs/wk local only
Delego
by delego-dev

Intent-bound action authorization for AI agents: policy, human approval, and a signed audit trail.

116 installs/wk local only
Mastyf AI
by mastyf-ai

Runtime proxy for MCP security, cost governance & audit

52 installs/wk local only
Bulwark
by bpolania

AI agent governance: content scanning, audit logs, policy evaluation, session management.

local only
Aegis
by undercurrentholdings

Local stdio MCP server for the AEGIS governance client. The hosted evaluation service is offline.

224 installs/wk local only
AgentFabric — Human-in-the-Loop Review & Approval
by enzoduit

Human-in-the-loop review and approval for AI agents. Audit trail, approval policies, native MCP.

1 tools answering

Sidclaw Governance MCP — questions

Answers built from our own checks of this server.

Why is there no uptime for Sidclaw Governance MCP?
Sidclaw Governance MCP runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @sidclaw/sdk was installed 67 times last week.
How do I connect Sidclaw Governance MCP?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls @sidclaw/sdk straight from npm; nothing to host, nothing to sign up for.
How many people use Sidclaw Governance MCP?
The npm package @sidclaw/sdk was installed 67 times in the last week. Week over week that is +91%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Sidclaw Governance MCP open source?
Yes — it is published under the Apache-2.0 licence, written in TypeScript, 15 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.