
CEDRUS
io.github.cedrus-mcpPublished by GitHub account cedrus-mcpv2.0.1Updated Oct 24, 2026
Reasoning scaffolding that supercharges your small AI: an argument-mapping MCP server
Overview
A local argument-mapping MCP server that gives small models a structured map of claims and supporting or attacking reasons to reason through debates.
- What you can do
- Build and extend an argument map: add claims and arguments for or against them, link or unlink relations, edit labels and text, and delete items or their dependent replies. Start a fresh map for a new question. Show the whole map, including which items nothing has challenged yet. Save maps as readable text and JSON files, with earlier sessions kept.
- When to use it
- Useful when running a small local model that struggles to hold a multi-step debate in context, or when you want the model's reasoning laid out in a readable, checkable structure you can question and extend.
- Requirements
- Runs as a local stdio process started with uvx (uv must be installed). The model must support tool calling. Optional --save-dir or --save-file (or CEDRUS_SAVE_DIR / CEDRUS_SAVE_FILE) to persist maps; without them no files are written.
Installation
In SourceWeft
- Open CEDRUS in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
CEDRUS
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.
- A scaffold, not a scratchpad. The map records which reason answers which claim, so the model doesn't have to hold it in its head, and a small model can work through a debate that would otherwise swamp it.
- Structure is checked for the model. IDs, sides and placement are worked out by the server. A move that doesn't fit is refused with an explanation, so mistakes get fixed instead of piling up.
- You see the reasoning. Every step lands in a map you can read, question and extend: "add an objection to A3", "what supports A7?".
- Local and private. Made for small models on your own machine, with maps saved as plain text and JSON.
What a map looks like
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.
Quick start
1. Install uv
CEDRUS is started by uv, which downloads and runs it for you.
2. Add CEDRUS to your app
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.
LM Studio
In the right sidebar, open the Program tab and choose Install → Edit mcp.json. Add
CEDRUS under mcpServers:
Jan
Go to Settings → MCP Servers, click +, and fill in:
For a local model, turn on tool calling in the model's settings (the edit button under Model Capabilities).
Goose
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:
Goose can run local models through Ollama, so this is also the way to use CEDRUS with Ollama.
Other MCP clients
Any client that can start a local (stdio) MCP server works: the command is uvx, the
arguments are cedrus-mcp and any options below.
Try it
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.
Saving your maps
With --save-dir DIR, CEDRUS writes the map after every change to DIR/<id>.txt, the
readable view, and DIR/<id>.json. Each time your app starts CEDRUS, it gets a new <id>,
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.
What the model can do
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.
Options
Running over HTTP, from a checkout, or under the MCP inspector is covered in docs/ADVANCED.md.
More
- docs/ADVANCED.md: running from source, HTTP, the file format, context pruning, development.
- docs/PLAN.md: the design.
- Version 1 is a separate code base, tagged
v1-final.
Licence
GNU Affero General Public License v3.0 or later. See LICENSE.
Source: README.md at commit bce1fa4
Tools
0Version history
1- v2.0.1LatestSep 18, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts