Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
A typed, policy-controlled OS capability layer for AI agents.
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": {
"osmcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/krushnavardhanreddy/osmcp:latest"
]
}
}
}Run this in your terminal
claude mcp add osmcp -- docker run -i --rm ghcr.io/krushnavardhanreddy/osmcp:latestPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"osmcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/krushnavardhanreddy/osmcp:latest"
]
}
}
}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": {
"osmcp": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/krushnavardhanreddy/osmcp:latest"
]
}
}
}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 8, 2026
The registry name was verified with the GitHub account KrushnaVardhanReddy, 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 (1.0.5) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Tethered Trust
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.
Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.
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.
A typed, policy-controlled OS capability layer for AI agents via the Model Context Protocol (MCP).
osmcp exposes a curated set of safe filesystem, git, and text-processing tools to AI agents — all governed by a strict Policy Engine that enforces path boundaries, tool allowlists, output limits, mutation controls, and an immutable audit trail.
📖 Read the comprehensive [Architecture & Design Document](docs/ARCHITECTURE.md) for a deep dive into the philosophy, safety boundaries, and design decisions behind osmcp.
| Category | Tools | Phase |
|---|---|---|
| 🔍 Search | grep, find | 1 |
| 📁 File Inspection | ls, cat, stat, wc, head, tail | 1 |
| 🌳 Filesystem | tree, du | 1 |
| 🔀 Git Intelligence | git_status, git_diff, git_log | 1 |
| 🔧 Transform | jq, sed, diff | 1 |
| ✍️ File Mutation | write_file, append_file, mkdir, rm, mv, cp, patch | 2 |
| 🚀 Git Mutation | git_add, git_commit, git_checkout, git_branch, git_pull, git_push | 2 |
AI Agent (Claude, GPT, etc.)
│ MCP JSON-RPC (stdio) ▼ osmcp binary ├── Policy Engine ← enforces allowed_root, allowed_tools, limits ├── Audit Logger ← append-only NDJSON log of every invocation ├── Tool Registry ← self-registering tools via RegisterMCP() └── Envelope Builder ← typed {ok, data, error, meta} responses
*A demonstration of Claude Desktop securely editing code via osmcp, safely bounded by a TOML policy engine.*
brew tap KrushnaVardhanReddy/tap
brew install osmcp
*Alternatively, build from source:*
make build
# policy.toml
[policy] allowed_root = "/home/user/myproject" allowed_tools = ["grep", "ls", "cat", "git_status", "git_log"] allow_mutation = false
[limits] timeout_ms = 5000 max_output_bytes = 1048576 max_matches = 100
[audit] destination = "stderr" # or "file" path = "/var/log/osmcp-audit.ndjson"
bin/osmcp --policy policy.toml
The binary communicates over stdio using MCP JSON-RPC. Connect any MCP-compatible client.
Add the following to your claude_desktop_config.json:
{
"mcpServers": { "osmcp": { "command": "osmcp", "args": ["--policy", "/absolute/path/to/policy.toml"] } } }
To install osmcp for Claude Desktop automatically via Smithery:
npx @smithery/cli install osmcp
Integrate osmcp into your enterprise LLM proxy using the LiteLLM MCP Gateway.
make test # unit tests
make e2e # end-to-end tests against real binary make lint # golangci-lint
POLICY_DENIED.tools/list.false, mutating tools (write, delete, git commit) are globally blocked.All tool responses follow a consistent typed envelope:
{
"ok": true, "tool": "grep", "data": { ... }, "error": null, "meta": { "execution_time_ms": 12, "truncated": false } }
MIT
osmcp would not be possible without the incredible open-source libraries it is built upon: