Bring Your AI
Hand off a local coding session from Claude Code to Codex (or similar harness moves) via Bring Your AI’s no-data MCP bridge.
Overview
ai.bringyour/bringyour is a MCP server for the Build phase that provides a no-data handoff between local Claude Code and Codex harness workflows.
What is this MCP server?
- No-data MCP handoff designed for local Claude Code → Codex harness transitions
- Hosted streamable-http remote at https://bringyour.ai/mcp (schema version 1.1.0)
- $49 lifetime pricing called out in server metadata
- Explicit positioning as harness-move tooling, not a general chat proxy
- Model Context Protocol remote server entry in published server.json-style descriptor
- Server version 1.1.0 in published descriptor
- Remote URL https://bringyour.ai/mcp
- $49 lifetime pricing stated in catalog description
What problem does it solve?
Switching between Claude Code and Codex on the same project forces awkward manual context transfers that break flow.
Who is it for?
Solo builders running Claude Code and Codex locally who want a paid, MCP-native bridge ($49 lifetime) instead of ad-hoc paste workflows.
Skip if: Teams needing centralized chat logging, cloud-only IDEs with no local harnesses, or generic LLM API routing unrelated to harness swaps.
What do I get? / Deliverables
After adding the Bring Your AI MCP remote, you can execute harness moves across local coding agents with the advertised no-data handoff pattern.
- Configured remote MCP connection to https://bringyour.ai/mcp
- Repeatable local harness transitions during active coding sessions
- No-data handoff workflow aligned with Bring Your AI product positioning
Recommended MCP Servers
Journey fit
Agent harness handoffs happen while you are actively building with multiple local AI tools, not during launch or ops monitoring. Bring Your AI is MCP plumbing between coding agents—squarely agent-tooling for multi-harness workflows on your machine.
How it compares
Local multi-harness MCP bridge, not a cloud hosting MCP or browser navigation recipe service.
Common Questions / FAQ
Who is ai.bringyour/bringyour for?
Developers using Claude Code and Codex locally who want MCP-based handoffs between coding harnesses without a data-heavy middleware story.
When should I use ai.bringyour/bringyour?
Use it when you routinely start work in one local agent harness and need to continue in another without rebuilding context manually.
How do I add ai.bringyour/bringyour to my agent?
Register the streamable-http MCP remote `https://bringyour.ai/mcp` in your client per bringyour.ai setup, with local Claude Code and Codex environments ready.