Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Reasoning scaffolding that supercharges your small AI: an argument-mapping MCP server
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": {
"cedrus": {
"command": "uvx",
"args": [
"cedrus-mcp"
]
}
}
}Run this in your terminal
claude mcp add cedrus -- uvx cedrus-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"cedrus": {
"command": "uvx",
"args": [
"cedrus-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": {
"cedrus": {
"type": "stdio",
"command": "uvx",
"args": [
"cedrus-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 cedrus-mcp, 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 (2.0.1) reached the registry 2 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, sync. labs
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.
Lipsync videos, dub them into other languages, make talking videos and open sync. Studio.
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.
Reasoning scaffolding that supercharges your small AI.
CEDRUS gives a local model an argument map to think in: the model lays out claims and the reasons for and against them, and the map keeps everything in place.
- C1 Legalisation of Soft Drugs
This is the outline. The full view the model reads also has every claim and argument in full, and notes which ones nothing has challenged yet.
CEDRUS is started by uv, which downloads and runs it for you.
# macOS and Linux
curl -LsSf https://astral.sh/uv/install.sh | sh
# Windows
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
Each setup below saves your maps to ~/cedrus-maps, a folder in your home directory. Use any folder you like, or leave out --save-dir and its path if you don't want files.
Whichever app you use, the model has to support tool calling.
In the right sidebar, open the Program tab and choose Install → Edit mcp.json. Add CEDRUS under mcpServers:
{
"mcpServers": { "cedrus": { "command": "uvx", "args": ["cedrus-mcp", "--save-dir", "~/cedrus-maps"] } } }
Go to Settings → MCP Servers, click +, and fill in:
| Field | Value |
|---|---|
| Server Name | cedrus |
| Command | uvx |
| Arguments | cedrus-mcp --save-dir ~/cedrus-maps |
For a local model, turn on tool calling in the model's settings (the edit button under Model Capabilities).
Run goose configure, choose Add Extension → Command-line Extension, name it cedrus, and give the command uvx cedrus-mcp --save-dir ~/cedrus-maps. In Goose Desktop, the same is under Extensions → Add custom extension.
Or add it to ~/.config/goose/config.yaml (%APPDATA%\Block\goose\config\config.yaml on Windows) yourself:
extensions:
cedrus: name: cedrus type: stdio cmd: uvx args: [cedrus-mcp, --save-dir, ~/cedrus-maps] enabled: true timeout: 300
Goose can run local models through Ollama, so this is also the way to use CEDRUS with Ollama.
Any client that can start a local (stdio) MCP server works: the command is uvx, the arguments are cedrus-mcp and any options below.
Map the debate on whether cities should ban cars from their centres. Start with the main
claim, then add the strongest arguments on both sides.
Now add an objection to the weakest pro argument.
Which arguments has nobody challenged yet? Add a reply to one of them.
Whenever you want to see the whole map, ask the model to show it.
With --save-dir DIR, CEDRUS writes the map after every change to DIR/ .txt, the readable view, and DIR/ .json. Each time your app starts CEDRUS, it gets a new , so earlier maps are kept. --save-file PATH writes to one fixed file instead, and a new session overwrites it.
When the model starts a new map, the old one is kept beside the live file as .1, then .2, and so on.
| Tool | What it does |
|---|---|
show | Print the whole map. |
add_claim | Add a claim: the statement being debated, or a principle. |
add_argument | Add an argument for or against something already in the map. |
link | Relate two items already in the map, or change how they relate. |
unlink | Remove one relation. |
edit | Change a label or a text. |
delete | Delete an item, optionally with the arguments that respond only to it. |
new_map | Start over with an empty map, for another question. |
An argument can support or attack what it responds to, or undercut another argument: grant its premises, but deny that they lead to its conclusion.
| Option | What it does |
|---|---|
--save-dir DIR | Save each session's map in DIR. Also CEDRUS_SAVE_DIR. |
--save-file PATH | Save the map to one file, PATH and PATH with .txt. Also CEDRUS_SAVE_FILE. |
--max-chars N | Size limit for the map view, default 24000 (roughly 6k tokens). Larger maps are shown shortened. |
--hints | Add a short hint to each tool result. |
Running over HTTP, from a checkout, or under the MCP inspector is covered in docs/ADVANCED.md.
v1-final.GNU Affero General Public License v3.0 or later. See LICENSE.