Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Universal AI skill compiler and MCP bridge. Write once, run across agents.
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.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
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.
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 daubesonntag-dotcom, 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.3) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Systemdox
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.
Your architecture in your agents' context: checks, specs, ADRs and docs over MCP, at write time.
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.
Write once. Run across agents.
D'AUBE // BRIDGE² is an open-source universal AI skill compiler and MCP bridge. Define one portable capability spec, then compile it into integration artifacts for ChatGPT/Codex, Claude, Gemini, DeepSeek, Meta/Llama, MCP hosts, and Chromium browsers.
On 2026-09-18, the BRIDGE² deployment record was AI Deploy Network Approved after review of the submitted implementation evidence. This means the deployment record passed AI Deploy Network review; it is not a client-confirmed commercial outcome or a guarantee of production performance.
The canonical publication narrative is maintained in docs/AI_DEPLOY_CASE_STUDY.md. The reviewed case study is now publicly available on AI Deploy Network.
AI tooling is fragmented. The same capability is repeatedly rewritten as MCP tools, provider function schemas, skills, plugins, and browser configuration. BRIDGE² treats those surfaces as compiler targets while keeping capability logic provider-neutral.
skill.yaml
| +-- MCP tool schema +-- OpenAI / ChatGPT / Codex artifacts +-- Claude plugin + SKILL.md +-- Gemini SKILL.md + MCP config +-- DeepSeek tool schemas +-- Meta/Llama function schemas +-- Chromium extension manifest
Current release: 7 target families, 15 deterministic artifacts, one MCP server.
git clone https://github.com/daubesonntag-dotcom/daube-agent-bridge.git
cd daube-agent-bridge python -m pip install -e ".[dev]" daube-bridge validate examples/skill.yaml daube-bridge compile examples/skill.yaml -o build/sample
Install the verified v0.1.3 wheel directly from GitHub Releases:
python -m pip install https://github.com/daubesonntag-dotcom/daube-agent-bridge/releases/download/v0.1.3/daube_agent_bridge-0.1.3-py3-none-any.whl
python -m daube_bridge doctor
python -m daube_bridge ... is the shim-free CLI path for Windows environments where Application Control blocks generated console-script executables.
Run BRIDGE² as a local stdio MCP server:
python -m daube_bridge.server
Or expose the HTTP MCP endpoint for remote/local integrations:
daube-bridge serve
BRIDGE² ships an MCPB v0.4 bundle definition using the cross-platform uv runtime. Build the deterministic bundle with:
python scripts/build_mcpb.py
The build is reproducible: identical source produces an identical archive hash. Official MCP Registry metadata lives in server.json.
| Surface | Output | Strategy |
|---|---|---|
| MCP hosts | MCP server + tool schemas | Shared transport/tool backbone |
| OpenAI / ChatGPT / Codex | SKILL.md, MCP descriptor, function schemas | Skills + MCP/tool calling |
| Claude | .claude-plugin/plugin.json, .mcp.json, SKILL.md | Plugin + portable skill + MCP |
| Gemini / Google agents | SKILL.md, MCP config | Portable skill + MCP |
| DeepSeek | OpenAI-style tools.json | Function/tool calling adapter |
| Meta / Llama | neutral tools.json | Application/router function schema |
| Chromium browsers | Manifest V3 side panel | Endpoint/config control surface |
This matrix describes integration artifacts BRIDGE² generates. It does not invent provider capabilities that do not exist.
name: My Research Skill
version: 0.1.0 description: Research and compare options. tools:
The bundled server exposes three small primitives:
bridge_targets — discover supported compilation targets.validate_skill — validate a portable skill object.compile_skill — compile a skill in-memory for another agent or tool.That makes BRIDGE² usable both as a CLI and as infrastructure callable by other agents.
python scripts/verify.py
python scripts/build_mcpb.py .tools/mcp-publisher.exe validate
The verification gate covers tests, Ruff, target discovery, sample compilation, wheel creation, deterministic MCPB creation, and official MCP Registry metadata validation.
After publishing a GitHub Release, smoke-test the public wheel in an isolated environment:
python scripts/smoke_release.py 0.1.3
npx / TypeScript compiler parity.Issues, adapters, compatibility fixtures, docs, and provider integrations are welcome. Provider-format changes should include a link to authoritative documentation and a minimal reproducible fixture.
Useful starting points:
CONTRIBUTING.mdCHANGELOG.mdGOVERNANCE.mddocs/PROVIDER_COMPATIBILITY.mddocs/20K_STAR_PLAYBOOK.mddocs/CODEX_FOR_OSS.mddocs/OPEN_SOURCE_FUND.mddocs/DISTRIBUTION.mddocs/PERFORMANCE_EVIDENCE.mddocs/THREAT_MODEL.mddocs/AI_DEPLOY_NETWORK.mddocs/LAUNCH_KIT.mdSECURITY.mdMIT © 2026 D'AUBE SONNTAG.