Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Wraps the AgenticWorkspace CLI as a single generic MCP tool for repo workspace scans.
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": {
"agenticworkspace": {
"command": "uvx",
"args": [
"agenticworkspace-cli",
"agenticworkspace-mcp"
]
}
}
}Run this in your terminal
claude mcp add agenticworkspace -- uvx agenticworkspace-cli agenticworkspace-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"agenticworkspace": {
"command": "uvx",
"args": [
"agenticworkspace-cli",
"agenticworkspace-mcp"
]
}
}
}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": {
"agenticworkspace": {
"type": "stdio",
"command": "uvx",
"args": [
"agenticworkspace-cli",
"agenticworkspace-mcp"
]
}
}
}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 7, 2026
The registry name was verified with the GitHub account RudrenduPaul, 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.4) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Dialyne
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.
Real phone calls in France for AI agents: dial +33 numbers, menus, hold, AI disclosure.
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.
Point it at any repo. It detects the stack, writes a .workspace/ directory with progressive context and session handoffs, and installs a working Claude Code adapter, all in one command.
npx agenticworkspace-cli init
This is a v0.1 release. Zero installs, zero GitHub stars, first release. 99/99 JavaScript tests and 132/132 Python tests pass. It does what's described below and nothing more. There's an honest comparison against the other tools already working in this space further down, so you can decide if AgenticWorkspace is actually worth trying before you run it.
.workspace/ directoryAgenticWorkspace ships two independent, equally first-class packages that implement the same scan/scaffold/adapter pipeline and read/write the same .workspace/ directory shape -- pick whichever fits your toolchain, or install both. Neither is deprecated in favor of the other.
# npm -- JavaScript/TypeScript CLI + library (live today, v0.1.3)
npx agenticworkspace-cli init
# PyPI -- Python CLI + library (live today, v0.1.1)
pip install agenticworkspace-cli agenticworkspace init --path /path/to/your/repo
To install from source instead:
git clone https://github.com/RudrenduPaul/AgenticWorkspace.git
cd AgenticWorkspace/python pip install -e . agenticworkspace init --path /path/to/your/repo
For repeat use with the npm package, install it globally:
npm install -g agenticworkspace-cli
agenticworkspace init
The Python package's CLI entry point is also agenticworkspace (e.g. agenticworkspace init --path ./my-app); see python/README.md and docs/getting-started.md for the Python-specific walkthrough.
To build the TypeScript package from source instead:
git clone https://github.com/RudrenduPaul/AgenticWorkspace.git
cd AgenticWorkspace npm install npm run build node dist/agenticworkspace/cli.js init
Everything below is verified against the actual source in this repo, not aspirational.
src/agenticworkspace/scan/stack-detector.ts).CLAUDE.md, AGENTS.md, .cursor/rules, and .github/copilot-instructions.md and never overwrites them (src/agenticworkspace/scan/config-detector.ts)..serena/ directory, a GitNexus-style config, or repo-harness's own .ai/harness/ directory, reports what it finds, and never reads or writes any of them (src/agenticworkspace/memory-backends/)..workspace/adapters/claude-code/settings.json (src/agenticworkspace/adapters/claude-code/install.ts).init, scan, status, adapter install, and handoff new all support --json, including on error paths (a nonexistent --path, a missing workspace, an unimplemented adapter), so a calling agent never has to parse human-readable text or guess at exit codes.MemoryBackend (src/agenticworkspace/memory-backends/types.ts) and Adapter (src/agenticworkspace/adapters/types.ts). Adding a new tool means implementing one interface and registering it (registry.ts in each folder); no changes to CLI or scan code are required. See Extending AgenticWorkspace below.src/agenticworkspace/util/sanitize.ts), covered by 30 dedicated unit tests (confirmed by running the suite directly, including the parameterized rejection cases).init run is detected and surfaced (interactive repair/reset/abort prompt, or a structured JSON error with a dedicated exit code in --json mode) instead of being silently overwritten or resumed (src/agenticworkspace/state/partial-state.ts).A real run against a small two-file JavaScript repo (target path shortened to /Users/you/my-app for readability, every field value below is the actual output):
$ agenticworkspace init --json --path ./my-app
{ "ok": true, "agenticworkspace_version": "0.1.1", "scanned_at": "2026-08-04T06:18:25.620Z", "target": "/Users/you/my-app", "stack": { "language": "javascript", "package_manager": "npm", "monorepo": false, "packages": 1 }, "existing_config": { "claudeMd": false, "agentsMd": false, "cursorRules": false, "copilotInstructions": false, "anyDetected": false }, "memory_backends": [ { "name": "serena", "detected": false, "description": "Serena memory/context tool (.serena/ directory)" }, { "name": "gitnexus", "detected": false, "description": "GitNexus-style config (.gitnexus/ or gitnexus.config.json)" }, { "name": "repo-harness", "detected": false, "description": "repo-harness (.ai/harness/ directory) -- detected only, never modified" } ], "context": { "root_context_kb": 0.6, "budget_kb": 12, "modules": [] }, "adapters": { "claude_code": { "installed": true, "hook_schema_version": "2026-07-01" } }, "workspace_dir": "/Users/you/my-app/.workspace" }
The agenticworkspace_version field in that output is a version string tracked separately from the package's own npm/PyPI version (they can drift; treat it as an internal schema marker, not the package version you installed).
That single run wrote seven real files on disk:
.workspace/workspace.json
.workspace/context/root-context.md .workspace/adapters/claude-code/settings.json .workspace/adapters/claude-code/adapter-meta.json .workspace/adapters/claude-code/hooks/session-start.sh .workspace/adapters/claude-code/hooks/pre-tool-call.sh .workspace/adapters/claude-code/hooks/session-end-handoff.sh
Drop --json for a human-readable version of the same run:
$ agenticworkspace init --path ./my-app
AgenticWorkspace v0.1 -- Repo-to-Agent-Workspace Converter Target: /Users/you/my-app
Scanning repository... [OK] Stack detected: javascript, npm [--] No existing agent-config files found [--] No memory/context tool detected
Writing .workspace/ scaffold... .workspace/workspace.json created .workspace/context/root-context.md created (0.6KB of 12KB budget) .workspace/handoff/ created (empty, ready for first session)
Installing Claude Code adapter... .workspace/adapters/claude-code/settings.json written .workspace/adapters/claude-code/hooks/session-start.sh written .workspace/adapters/claude-code/hooks/pre-tool-call.sh written .workspace/adapters/claude-code/hooks/session-end-handoff.sh written
Workspace ready. Next Claude Code session in this repo will load root-context.md automatically and write a handoff file on exit.
Checking workspace health and writing a session handoff on that same repo, real output:
$ agenticworkspace status --path ./my-app
AgenticWorkspace status Target: /Users/you/my-app Last scan: 2026-08-04T06:18:25.620Z
Stack: javascript, npm, 1 package(s) Context budget: 0.6KB of 12KB (0 module block(s)) Handoffs: 0 file(s), most recent: none Claude Code adapter: installed, schema 2026-07-01, current Other backends detected: none
$ agenticworkspace handoff new "test session" --path ./my-app
Handoff written: .workspace/handoff/2026-08-04-0618.md
See docs/usage.gif for a recorded run of handoff new and status together.
Everything below is verified against the actual source in this repo, not aspirational.
src/agenticworkspace/scan/stack-detector.ts).CLAUDE.md, AGENTS.md, .cursor/rules, and .github/copilot-instructions.md and never overwrites them (src/agenticworkspace/scan/config-detector.ts)..serena/ directory, a GitNexus-style config, or repo-harness's own .ai/harness/ directory, reports what it finds, and never reads or writes any of them (src/agenticworkspace/memory-backends/)..workspace/adapters/claude-code/settings.json (src/agenticworkspace/adapters/claude-code/install.ts).init, scan, status, adapter install, and handoff new all support --json, including on error paths (a nonexistent --path, a missing workspace, an unimplemented adapter), so a calling agent never has to parse human-readable text or guess at exit codes.MemoryBackend (src/agenticworkspace/memory-backends/types.ts) and Adapter (src/agenticworkspace/adapters/types.ts). Adding a new tool means implementing one interface and registering it (registry.ts in each folder); no changes to CLI or scan code are required. See Extending AgenticWorkspace below.src/agenticworkspace/util/sanitize.ts), covered by 30 dedicated unit tests.init run is detected and surfaced (interactive repair/reset/abort prompt, or a structured JSON error with a dedicated exit code in --json mode) instead of being silently overwritten or resumed (src/agenticworkspace/state/partial-state.ts).Every command accepts -p, --path (defaults to the cur
Only the beginning is shown; read the rest in the repo