Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Routes agent tool calls through Guardian for ALLOW/ASK/DENY before execution.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
GUARDIAN_BASE_URL, GUARDIAN_AGENT_CREDENTIAL, GUARDIAN_CONNECTION_ID, GUARDIAN_ADAPTER_IDValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"guardian": {
"command": "npx",
"args": [
"-y",
"@odingard/guardian-mcp"
],
"env": {
"GUARDIAN_BASE_URL": "your-value",
"GUARDIAN_AGENT_CREDENTIAL": "your-value",
"GUARDIAN_CONNECTION_ID": "your-value",
"GUARDIAN_ADAPTER_ID": "your-value"
}
}
}
}Run this in your terminal
claude mcp add guardian --env GUARDIAN_BASE_URL=your-value --env GUARDIAN_AGENT_CREDENTIAL=your-value --env GUARDIAN_CONNECTION_ID=your-value --env GUARDIAN_ADAPTER_ID=your-value -- npx -y @odingard/guardian-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"guardian": {
"command": "npx",
"args": [
"-y",
"@odingard/guardian-mcp"
],
"env": {
"GUARDIAN_BASE_URL": "your-value",
"GUARDIAN_AGENT_CREDENTIAL": "your-value",
"GUARDIAN_CONNECTION_ID": "your-value",
"GUARDIAN_ADAPTER_ID": "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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"guardian": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@odingard/guardian-mcp"
],
"env": {
"GUARDIAN_BASE_URL": "your-value",
"GUARDIAN_AGENT_CREDENTIAL": "your-value",
"GUARDIAN_CONNECTION_ID": "your-value",
"GUARDIAN_ADAPTER_ID": "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 one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
GUARDIAN_ADAPTER_ID envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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
The registry name was verified with the GitHub account Odingard, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
You need to fill in: GUARDIAN_BASE_URL, GUARDIAN_AGENT_CREDENTIAL, GUARDIAN_CONNECTION_ID
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.3.2) reached the registry 2 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, TF Rooms
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
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Live room availability, rates and stay quotes for 12 New Leaf motels in Twin Falls, Idaho.
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.
MCP server that routes an agent's tool calls through Guardian — Human Authority Infrastructure for Autonomous AI. Every tool call gets a deterministic ALLOW / ASK / DENY decision before anything executes; DENY means the action never runs, and ASK holds it until a human approves.
npm i -g @odingard/guardian-mcp
{
"mcpServers": { "guardian": { "command": "guardian-mcp", "env": { "GUARDIAN_BASE_URL": "https://guardian-api.odingard.com", "GUARDIAN_AGENT_CREDENTIAL": "gak_…", "GUARDIAN_CONNECTION_ID": "con_…" } } } }
GUARDIAN_ADAPTER_ID optionally overrides the tool adapter.
| Tool | What it does |
|---|---|
guardian_invoke_tool | Propose a tool call. ALLOW executes and returns the receipt; ASK returns a requestId held for human approval; DENY refuses with a reason code. |
guardian_claim | Claim an approved ASK by requestId, execute, return the receipt. |
guardian_receipt | Fetch the machine-readable evidence receipts for a request. |
Nothing executes without a Guardian capability — the model's output is a proposal, never an action.
guardian-mcp proxy (0.3)Put Guardian in front of any stdio MCP server you already use, such as WhatsApp, Stripe, Shopify, a filesystem or a database. The client sees the upstream server's tools unchanged, and every call is decided first:
{
"mcpServers": { "whatsapp-governed": { "command": "guardian-mcp", "args": ["proxy", "--", "npx", "-y", "your-whatsapp-mcp-server"], "env": { "GUARDIAN_BASE_URL": "https://guardian-api.odingard.com", "GUARDIAN_AGENT_CREDENTIAL": "gac1.…", "GUARDIAN_CONNECTION_ID": "con_…", "WHATSAPP_TOKEN": "…" } } } }
| Decision | What happens |
|---|---|
| ALLOW | The call is forwarded to the upstream server, then the capability is redeemed and the receipt recorded. |
| ASK | Nothing is forwarded. The exact call is held under a requestId; after a human approves, guardian_claim forwards exactly that call, once. |
| DENY | Nothing is forwarded, ever. The same applies if Guardian is unreachable. |
guardian_claim and guardian_receipt are added to the tool list.GUARDIAN_* settings, so it never sees the agent credential.localEffectRan: true), never as success.GUARDIAN_AUTO_REGISTER=true turns that back on, but it is denied unless the agent's grant pins mcp.install.guardian-mcp --help prints usage. A missing setting prints a one-line message naming it instead of a stack trace.
guardian-mcp toolsBefore putting a server behind the proxy, list its tools along with a suggested Guardian mode for each. This needs no Guardian credential:
npx -y @odingard/guardian-mcp tools -- npx -y @modelcontextprotocol/server-filesystem ./data
Tool Suggested Why
read_file Allow server marks it read-only write_file Ask me first "write" may change something delete_branch Ask me first server marks it destructive createIssue Ask me first "create" may change something ⚠ name not accepted by Guardian
How the suggestions are made:
readOnlyHint, destructiveHint) are used first.get, list and search suggest Allow; everything else suggests Ask.They are suggestions only: you set the real modes in the console. Tool names that break Guardian's naming rule are flagged, because every call to them would be denied. Add --json for machine-readable output.
Apache-2.0. Canonical development happens in the Odingard Guardian monorepo.