Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Local-first file-organization tools for your AI agent: tag, query, and digest a folder. No cloud.
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.
CAIRN_WORKSPACEYou 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": {
"cairn": {
"command": "uvx",
"args": [
"cairn-mcp-server"
],
"env": {
"CAIRN_WORKSPACE": "your-value"
}
}
}
}Run this in your terminal
claude mcp add cairn --env CAIRN_WORKSPACE=your-value -- uvx cairn-mcp-serverFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"cairn": {
"command": "uvx",
"args": [
"cairn-mcp-server"
],
"env": {
"CAIRN_WORKSPACE": "your-value"
}
}
}
}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": {
"cairn": {
"type": "stdio",
"command": "uvx",
"args": [
"cairn-mcp-server"
],
"env": {
"CAIRN_WORKSPACE": "your-value"
}
}
}
}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.
CAIRN_WORKSPACE envThese 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 luckyjackluo, 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.2.0) reached the registry 4 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, Foliosio
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.
Read your support inbox, tag conversations and save draft replies from your AI agent. Never sends.
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 local-first, open-source harness for organizing your files with an AI agent.
Point Claude Code, Codex, Cursor — any MCP client — at a folder, and your agent gains a full file-organization toolset: list, read, search, grep, edit, move, tag, import documents, and semantically retrieve. No account, no cloud, no UI required. Your files never leave your machine.
claude mcp add cairn -- uvx cairn-mcp-server --workspace ~/Documents/notes
Then ask your agent to *"organize this folder and tag everything"* — it will, using tools that run locally over your own files.
A cairn is a stack of stones that marks a trail. This one keeps your files in
order and shows the way through them.
If you use Claude Code, setup is one command — the only prerequisite is uv, which provides uvx:
# 1. Install uv if you don't have it (provides uvx)
curl -LsSf https://astral.sh/uv/install.sh | sh
claude mcp add cairn -- uvx cairn-mcp-server --workspace ~/Documents/notes
Reopen Claude Code and ask:
*"Organize this folder and tag everything."*
Cairn's tools run locally over your files — reads happen freely, and any move/rename/edit asks for confirmation first. The first run auto-downloads the package (~5s); no clone, no build, no account.
[!TIP]
Point
--workspaceat a copy of some notes for your first run — Cairn can
move, rename, and edit files.
Using Codex? Same one-command flow (then run /mcp in a session to confirm):
codex mcp add cairn -- uvx cairn-mcp-server --workspace ~/Documents/notes
Using Cursor or another MCP client? Same package, JSON config:
{ "mcpServers": { "cairn": { "command": "uvx",
"args": ["cairn-mcp-server", "--workspace", "~/Documents/notes"] } } }
~ is expanded by Cairn, so ~/Documents/notes works in the CLI and in config files alike.
Just want to poke at it, no agent?
uvx cairn-cli --workspace ~/Documents/notes tree
The agent-harness ecosystem converged on a clear pattern: the model and the agent loop are commodities supplied by the client (Claude Code, Codex, OpenCode). The durable value is the tools and the local data. So Cairn ships *tools, not an agent* — the client provides the loop, the approval prompts (driven by our tool annotations), and the chat. Cairn is just the local file-organization toolset that snaps into whatever harness you already use.
Everything is a thin adapter over one standard-library core, so the faces can never drift.
core/ cairn-core — the engine (stdlib only): the .uni document format,
file operations, tags, retrieval; optional document ingestion (docx/pdf/pptx/xlsx/md) and embeddings-based search. mcp-server/ cairn-mcp-server — MCP server: 26 tools with read-only/destructive annotations, resources, and prompts. ← the flagship cli/ cairn-cli — scriptable CLI, a local HTTP API (serve), and an mcp launcher. web/ cairn-web — optional zero-build local web UI (browse / edit / view / tag / search).
In Claude Code / Codex / Cursor (primary):
claude mcp add cairn -- uvx cairn-mcp-server --workspace ~/Documents/notes
The server exposes read-only tools (list, read, search, grep, retrieve) that the client runs freely, and destructive tools (move, delete, edit) that it confirms first — driven by MCP tool annotations, so you get approval prompts with no UI of ours.
As a CLI:
uvx cairn-cli --workspace ~/Documents/notes tree
uvx cairn-cli --workspace ~/Documents/notes retrieve "budget planning"
With the optional web UI:
pip install cairn-cli cairn-web
cairn --workspace ~/Documents/notes serve # → http://127.0.0.1:4177/
.uni formatA .uni file is a small JSON document — { uuid, content: " ", metadata, tags } — with tags stored *in the file*. A workspace is just a directory: fully portable, no external database. Source documents (docx/pdf/pptx/…) import into editable .uni docs; the originals are kept by default.
/.cairn/ and never leave your machine.Cairn is young. Rough direction, and where help is most welcome:
.cairn/views/*.md).Have a use case that doesn't fit? Open an issue or start a discussion.
Contributions of every size are welcome — see CONTRIBUTING.md for the project layout, dev setup, and how to add a tool. Good first issues are labeled good first issue.
make setup # uv venv (3.11) + editable install of all packages + extras
make test # run the suite make serve WORKSPACE=~/Documents/notes # web UI
MIT — see LICENSE.