Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Pass the baton between coding agents: convert sessions across Claude Code, OpenCode, Codex & more.
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": {
"baton": {
"command": "npx",
"args": [
"-y",
"@kasabeh/baton-mcp",
"serve"
]
}
}
}Run this in your terminal
claude mcp add baton -- npx -y @kasabeh/baton-mcp servePaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"baton": {
"command": "npx",
"args": [
"-y",
"@kasabeh/baton-mcp",
"serve"
]
}
}
}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": {
"baton": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@kasabeh/baton-mcp",
"serve"
]
}
}
}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 publisher (kasabeh.tech) is not the repo owner (Kaseban); someone else may have listed it
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 0 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.3.0) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Rystic
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.
Start, seed, clock, inspect and diff Rystic API simulators from your agent.
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.
Pass the baton between coding agents.
Convert any coding-agent session to any other. One command. Keep going where you left off.
A passed transcript kept 14/17 concrete facts. A hand-written handoff summary kept 3/17. Benchmark ↓
It's 4 p.m. Claude Code says "usage limit reached — resets at 10 p.m." You're three hours into a session: architecture decided, edge cases mapped, half the diff written.
❌ Without baton — open another agent and start from zero. Re-explain the plan. Re-read the files. Re-litigate every decision you already made.
✅ With baton — pass the session and keep going:
baton convert --from claude-code --to opencode --latest --import
opencode -s ses_8c4c973a521549e2 # same conversation, different runner
Works in every direction: switch agents mid-task, try a second opinion on a hard bug, move a session from your editor agent to a terminal agent, or archive everything in one format.
# zero-install run (downloads prebuilt binary)
npx @kasabeh/baton-mcp --help
baton convert --from claude-code --to opencode --latest --import
baton convert --from claude-code --to opencode --import
baton convert --from claude-code --to opencode --import
baton list
You never have to hunt these down (--latest and the interactive picker find them for you), but for reference — each agent stores its transcripts on disk:
| Agent | Location |
|---|---|
| Claude Code | ~/.claude/projects/ / .jsonl |
| Codex CLI | ~/.codex/sessions/ / / /rollout-*.jsonl |
baton list prints the path of every session it can find, across all agents.
| Agent | Read | Write | Auto-import |
|---|---|---|---|
| Claude Code | ✅ | ✅ | — |
| OpenCode | ✅ | ✅ | ✅ opencode import |
| Codex CLI | ✅ | ✅ | — |
| Gemini CLI | ✅ | ✅ | — |
| Zed | ✅ | ✅ | — |
| Aider | ✅ | ✅ | — |
| Cursor | ✅¹ | —² | — |
| Continue | ✅ | — | — |
| Cline / Roo | ✅ | —² | — |
¹ Cursor reads from exported JSON (sqlite3 state.vscdb "SELECT value FROM ItemTable WHERE key='aiService:chats'")
² Not planned: Cursor and Cline keep session state inside editor databases (SQLite / VS Code globalState) with no file-level import path.
Does carrying the full transcript beat writing a handoff summary for the next agent? We measured both on a real 3.4 MB Claude Code session (same model both arms, only the context differs):
| session size | baton transcript | handoff summary |
|---|---|---|
| sm (93 KB) | 3/3 details recalled | 1/3 |
| md (198 KB) | 6/6 | 1/6 |
| lg (599 KB) | 5/8 | 1/8 |
| total | 14/17 | 3/17 |
The summary lost concrete facts (versions, line counts, MSRV) even on the smallest slice — the receiving agent had to re-read files and re-run commands to rediscover them. Mechanical fidelity: all 896 messages are written to every target; round-trip loss reflects each target format's expressiveness (claude-code 896/896, codex 736, gemini-cli 723, aider 111 — it stores chat text only).
We also measured task continuation: cut the session at three mid-task points, ask a fresh agent to state the task, state, and next steps. Result: parity (baton 10/12, handoff 10/12) — a good summary is enough for *what to do next*; the transcript is what answers the *specific factual questions* the summary's author didn't anticipate. And the summary only exists if an agent spends a full transcript read writing it — baton makes the transfer free.
Full methodology, caveats, and reproduction steps: benchmark/RESULTS.md.
baton is also an MCP server — your agent can pass the baton itself, mid-conversation:
| Tool | Description |
|---|---|
list_sessions | Scan all agents, return a unified list |
convert_session | Convert a session from one format to another |
import_to_target | Convert + run the target agent's import command |
detect_format | Sniff a file/dir and report which agent produced it |
baton install # registers baton in every detected agent's MCP config
baton doctor # verify baton uninstall # remove from all agents
Claude Code session (.jsonl)
│ ▼ baton read ──► canonical Session { messages: [Text, Reasoning, ToolCall, ToolResult] } │ ▼ baton write ──► OpenCode import JSON (SessionV1 schema)
Every agent format is read into a canonical intermediate representation, then written out in the target format. Adding a new format is O(1), not O(N×M) per-pair converters.
# npm (prebuilt binary, no Rust needed)
npm install -g @kasabeh/baton-mcp
brew install kaseban/tap/baton-mcp
cargo binstall baton-mcp
cargo install baton-mcp
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/Kaseban/baton/releases/latest/download/baton-mcp-installer.sh | sh
Or grab a binary from GitHub Releases.
git clone https://github.com/Kaseban/baton.git
cd baton cargo build --release ./target/release/baton --help
Each format lives in src/formats/ .rs and implements the Format trait (read + write). See src/formats/claude_code.rs for a complete reference implementation.
All nine formats have readers; Claude Code, OpenCode, Codex, Zed, Aider, and Gemini CLI also have writers. The most impactful contribution now is a writer for Continue.
The README GIF is scripted with VHS: vhs assets/demo.tape. It records against a sandboxed $HOME (/tmp/demo) populated with fabricated sessions, so no real session data ends up in the GIF.
Don't drop the baton.
Dual-licensed under MIT OR Apache-2.0.