Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Runtime authority for AI agents: credential mediation, spend cap, approval gates, audit log.
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.
MARCHWARD_API_URL, MARCHWARD_API_KEYValues 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": {
"marchward": {
"command": "npx",
"args": [
"-y",
"@marchward/mcp-server"
],
"env": {
"MARCHWARD_API_URL": "your-value",
"MARCHWARD_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add marchward --env MARCHWARD_API_URL=your-value --env MARCHWARD_API_KEY=your-value -- npx -y @marchward/mcp-serverFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"marchward": {
"command": "npx",
"args": [
"-y",
"@marchward/mcp-server"
],
"env": {
"MARCHWARD_API_URL": "your-value",
"MARCHWARD_API_KEY": "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": {
"marchward": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@marchward/mcp-server"
],
"env": {
"MARCHWARD_API_URL": "your-value",
"MARCHWARD_API_KEY": "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.
These 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 against the domain marchward.ai (the registry checks domain ownership)
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: MARCHWARD_API_URL, MARCHWARD_API_KEY
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.2.4) reached the registry 4 months 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, Whisper
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.
One routable IPv6 per AI agent, verifiable from the DNS root. Keyless tools need no signup.
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.
Marchward · runtime authority for AI agents
Govern what your AI agents are allowed to _do_. Marchward is one open layer that sits in front of an agent's tool calls and enforces four controls before any action runs, then writes a tamper-evident record of every decision. Self-hostable, Apache-2.0, framework-agnostic.
Most tools in this space cover one of these. Marchward brings all four together in one place, open and self-hostable.
Output guardrails check what an agent _says_ (toxicity, PII, topic). Marchward governs what an agent _does_ (spend, delete, act). A check on the agent's output cannot stop an agent that still holds the keys and can make a different call. Marchward governs the action itself.
Built for teams already running agents in production (LangGraph, LangChain, raw SDKs, any MCP server, or one HTTP call from any runtime) who need an agent to be autonomous without being able to drain a budget, take an irreversible action unattended, or act without an audit trail.
marchward-proxy wraps any MCP server as a child process and evaluates every tools/call against your policy before it runs (block, allow, or pause for human approval), entirely on your machine, with your own credentials.
# Write a policy (escalate anything destructive, allow the rest)
cat > policy.json <<'EOF' { "rules": [ { "match": { "toolPattern": "*delete*" }, "decision": "ESCALATE" }, { "match": { "toolPattern": "*" }, "decision": "ALLOW" } ]} EOF
npx -p @marchward/proxy marchward-proxy \ --command "node my-mcp-server.js" \ --policy-file ./policy.json \ --local
Every tool call your agent makes now passes through policy first, and lands in a local tamper-evident (hash-chained) audit log you can verify offline. No account, no network call to us.
Prefer the SDK? pip install marchward and wrap calls with marchward.execute(). Point it at your own self-hosted setup, or at the managed plane (below).
The open packages in this repo are a fully functional self-host governor. Some operational features need shared state and run on the hosted plane (free tier, no card):
| Open (self-host, this repo) | Hosted plane (Marchward Cloud) | |
|---|---|---|
| Execution control: allow / block / escalate tool calls by policy | yes | yes |
| Local governor (MCP/HTTP intercept, your own credentials) | yes | yes |
| Tamper-evident audit: hash-chain primitive + offline verify | yes | retained, queryable, monitored |
| Approval-gate decision | yes | + managed workflow (notify, approve, resume) |
| Inference cost cap | local accounting | enforced (rolling-window spend) |
| Credential mediation (agent holds one key, real cred injected, the agent never sees it) | yes, from your own local secret store | yes, managed vault |
| Managed credential vault, multi-tenancy, SSO/RBAC | no | yes |
So: self-host this for execution control, credential mediation from your own local store, a local cost cap, and a local audit log; add the free hosted tier for the managed credential vault (rotation, team sharing), approval workflows, retained audit-as-a-service, and cross-agent enforcement. Same engine underneath. The proxy's --remote mode just points at the plane.
DELETE, a flagged destructive POST) is gated regardless of what the tool is _named_, so a custom-named destructive tool cannot slip past.--local or --remote.CONTRIBUTING.md (DCO sign-off, git commit -s)SECURITY.md · Conduct: CODE_OF_CONDUCT.md · Governance: GOVERNANCE.mdTRADEMARK.md. The code is open (Apache-2.0); the name is not.OPEN-VS-COMMERCIAL.md · our licensing commitment (the engine stays open, no relicensing rug-pull).