Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
76% fewer MCP tokens in our standard benchmark. Same upstream call. Exact recovery.
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.
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": {
"slim-guard": {
"command": "npx",
"args": [
"-y",
"mcp-slim-guard"
]
}
}
}Run this in your terminal
claude mcp add slim-guard -- npx -y mcp-slim-guardPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"slim-guard": {
"command": "npx",
"args": [
"-y",
"mcp-slim-guard"
]
}
}
}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": {
"slim-guard": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-slim-guard"
]
}
}
}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 9, 2026
The registry name was verified with the GitHub account lennney, 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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.1.1-alpha.1) reached the registry 3 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, phylokit-mcp
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ 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.
Phylogenetic inference via IQ-TREE 3 — never returns a topology without its support
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 Slim Guard gives a host one deliberate way to reach authorized upstream tools. It keeps input schemas intact, validates calls before the upstream is invoked, and can recover an oversized result exactly without repeating that invocation.
| Mode | What the host sees | Best fit |
|---|---|---|
| Native | Authorized original tool names and full schemas, plus read_result | Hosts that work well with a normal MCP catalog, including Codex |
| Compact | find_tool, call_tool, and read_result; discovery returns each match's full original schema | A small, predictable host surface |
| Extreme | The Compact tool surface and schemas; only sufficiently large results receive a shorter recoverable first delivery | Context-sensitive hosts where a smaller first result is valuable |
Compact is the default for start. Native is the default installation plan for Codex. Compact is the default for Claude Code; Claude Code supports Compact and Extreme installation plans, not Native.
All modes apply the same allow/deny authorization. Compact and Extreme return at most three discovery matches, each with the original required fields, enums, and nested schema. A call is validated against that original schema before the upstream server is contacted.
find_tool rejects unknown fields and queries longer than 256 Unicode code points locally. It searches only the current authorized catalog and never falls back to an unauthorized entry.
0.1.1-alpha.2 is a source candidate and is not published to npm yet. From a reviewed checkout of this candidate:
npm ci
npm run build npm link cd /path/to/project-with-mcp-config mcp-slim-guard init mcp-slim-guard validate
mcp-slim-guard start
init writes mcp-slim-guard.yml with version 2. The file contains upstream and security settings only. Select a mode in the host command, not in YAML.
# Inspect a host-specific plan without changing host files.
mcp-slim-guard plan --host codex mcp-slim-guard plan --host claude-code --mode extreme
mcp-slim-guard verify --host codex
mcp-slim-guard install --host codex --mode native
For Codex, use Native when you want the normal authorized MCP catalog:
[mcp_servers.slim_guard]
command = "mcp-slim-guard" args = ["start", "--mode", "native"] cwd = "/absolute/path/to/project"
For Claude Code, use Compact by default:
{
"mcpServers": { "slim-guard": { "command": "mcp-slim-guard", "args": ["start", "--mode", "compact"], "cwd": "/absolute/path/to/project" } } }
See host setup for the full configuration and verification steps.
version: 2
tools: allow:
ssrf: mode: block block_private_ips: true allow_domains: [] block_domains: [] rate_limit: default: "60/min" injection_detection: enabled: true sensitivity: medium mode: block audit: output: file filePath: mcp-slim-guard-audit.log servers: upstream: command: npx args: ["-y", "@your/mcp-server"]
Version 1 configuration is intentionally unsupported. The removed compressor section is rejected rather than migrated automatically.
If arguments do not match an authorized tool's original schema, Slim Guard returns a normal MCP tool error with structuredContent that identifies the schema failure and confirms that the upstream tool was not invoked. Correct the arguments and retry; submitted argument values are not echoed in that error.
When a response needs recoverable delivery, the first response includes a result_ref. Use read_result with query to locate up to three bounded local fragments, or omit query and follow next_cursor to recover the exact snapshot. Both paths use the same immutable capture and never invoke the upstream tool again. Do not combine query with cursor. Native and Compact use the standard delivery boundary. Extreme uses a smaller boundary only when the initial delivered response is at least half the size of the exact response; otherwise it passes the exact response through unchanged.
The repository includes a 24-task mode comparison, result-recovery fixtures, and a 100-tool / 8,000-row stress fixture. Run the current artifacts with:
npm run build
npm run bench:task npm run bench:compression npm run bench:stress npm run bench:compression:verify
Their reports are mode-specific and are generated locally; do not treat older alpha benchmark figures as claims for this product line.
npm run build
npm run typecheck npm run lint npm test npm run verify:package-boundary npm run smoke:package
This project is an alpha. Review authorization patterns and upstream settings before using it with privileged tools.