About D'AUBE // BRIDGE²
D'AUBE // BRIDGE² is an open-source compiler for portable AI skills, aimed at teams supporting multiple agent ecosystems. It turns one capability specification into integration artifacts and also provides an MCP server and CLI.
Key features
- 01Compile portable skills for multiple targets
- 02Validate skill specifications
- 03Discover supported compilation targets
- 04Generate deterministic MCPB bundles
Use cases
- 01Maintain one capability definition across agents
- 02Generate MCP and provider integration artifacts
- 03Expose compilation operations to other agents
MCP support
Its MCP server exposes tools to discover targets, validate a skill, and compile one in memory. It supports local stdio and an HTTP endpoint.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMED'AUBE // BRIDGE²
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.
External review
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.
Why BRIDGE²
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.
30-second start
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
# http://127.0.0.1:8000/mcp
One-click MCPB
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.
Target matrix
| 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.
Portable skill format
name: My Research Skill
version: 0.1.0
description: Research and compare options.
tools:
- name: compare_options
description: Compare options against explicit criteria.
parameters:
type: object
properties:
options:
type: array
items: {type: string}
required: [options]
MCP 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.
Verify before release
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
Roadmap
- ChatGPT Apps SDK interactive widget target.
npx/ TypeScript compiler parity.- Provider capability detection and compatibility linting.
- Signed bundles and provenance manifests.
- Remote registry + searchable skill catalog.
- One-click adapters for agent IDEs and orchestration frameworks.
- Golden interoperability fixtures across providers.
Project principles
- Portable by default. Prefer MCP and open schemas over provider lock-in.
- Evidence over pretending. Never claim native support that a provider does not have.
- Readable outputs. Generated artifacts stay human-auditable and diffable.
- Safe boundaries. Authentication and sensitive actions remain explicit.
- Fast adoption. A useful first result should take minutes, not a framework migration.
Contributing
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.md
License
MIT © 2026 D'AUBE SONNTAG.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.