
Warp Ozbridge
io.github.sena-labsPublished by GitHub account sena-labsv2.0.0Updated Oct 29, 2026
OzBridge: run Warp Oz agents from any MCP client — Claude Code, Cursor, Codex, VS Code.
Overview
MCP server that lets any MCP client launch and inspect Warp Oz agent runs by shelling out to the local oz CLI.
- What you can do
- Run Oz agents locally with a prompt and get the full run payload back
- Launch cloud Oz runs and list, filter or fetch runs by id
- List available AI model ids and the current default
- Set the default Oz model by writing it into the workspace bridge config
- Serve the same six tools over stdio or Streamable HTTP, with a health route
- When to use it
- Use it when you already work with Warp Oz and want to start, monitor and configure Oz agent runs from Claude Code, Cursor, Codex, Windsurf or another MCP client without the VS Code extension.
- Requirements
- Node.js 22.12 or newer; the Oz CLI installed and on PATH or pointed at via OZ_PATH; a one-time oz login in a terminal. Runs locally via npx, either spawned over stdio or listening on 127.0.0.1:3847 by default. Optional settings include OZ_MCP_PORT, OZ_MCP_BIND, OZ_MCP_TOKEN, OZ_DEFAULT_MODEL, OZ_DEFAULT_PROFILE, OZ_DEFAULT_ENV, OZ_TIMEOUT_MS and OZ_IDLE_TIMEOUT_MS.
Installation
In SourceWeft
- Open Warp Ozbridge in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@sena-labs/oz-mcp-server
Standalone Model Context Protocol server for Warp™ Oz™ agents — no VS Code required. Run it from a terminal and drive Oz from Claude Code, Cursor, Codex, or any MCP client.
OzBridge is an independent project and is not affiliated with, endorsed by, or sponsored by Warp. "Warp" and "Oz" are trademarks of Warp, Inc., used here nominatively — solely to describe interoperability. See Trademarks & disclaimer below.
This package is the VS Code‑free sibling of the
OzBridge extension. It exposes the same
MCP tool surface (six tools: oz_agent_run, oz_run_list, …) over stdio or
Streamable HTTP, so any MCP client can launch and inspect Oz runs.
Requirements
- Node.js ≥ 22.12
- The Oz CLI installed and on your
PATH(or pointed at viaOZ_PATH). Download Warp from https://www.warp.dev/download — theozcommand ships with it (on Linux typically~/.warp/bin/oz). Verify withoz --version. - Signed in to Warp: run
oz loginonce in a terminal.
The server only ever shells out to the documented oz CLI; it does not embed,
modify, or reverse‑engineer any Warp software.
Quick start (stdio — recommended)
Let your MCP client spawn the server over stdio — no install step, no port, no token, and no terminal to keep open.
Claude Code:
Codex CLI — add to ~/.codex/config.toml:
Cursor / Windsurf / Claude Desktop — add to ~/.cursor/mcp.json (Cursor),
~/.codeium/windsurf/mcp_config.json (Windsurf) or
claude_desktop_config.json (Claude Desktop):
HTTP mode
To run a long-lived server that clients reach by URL instead:
It binds to 127.0.0.1:3847. Leave it running, then point your MCP client at
the Streamable HTTP endpoint http://127.0.0.1:3847/mcp — see
MCP client setup (HTTP). The legacy HTTP+SSE endpoint
/sse is still served but deprecated.
Pin a port and a bearer token instead of the defaults:
Install it globally if you'd rather not re‑download on each run:
Configuration
Settings resolve in this order (highest precedence first):
- CLI flags
- Environment variables
./.warp/warp-bridge.yaml(current working directory), then~/.warp/warp-bridge.yaml- Compiled‑in defaults
CLI flags
Environment variables
On Windows PowerShell, set variables with
$env:first:
Transports
The server speaks MCP over two transports:
- stdio (
--stdio) — the host spawns the server as a child process and exchanges JSON-RPC over stdin/stdout. Recommended for Claude Code, Codex, Cursor, Windsurf, Claude Desktop,mcp-proxy, and registry sandboxes (e.g. Glama). No port, no token. See Quick start. - Streamable HTTP (default when
--stdiois not passed) — the server listens on a port and clients connect by URL to/mcp. The older HTTP + SSE transport (/sse+/messages) is still served for legacy clients but is deprecated.
MCP client setup (HTTP)
For URL-based clients, start the server in HTTP mode (above), then add the
endpoint to your client. These snippets mirror
docs/MCP.md.
Claude Code
Cursor / Windsurf
Add to ~/.cursor/mcp.json (or ~/.codeium/windsurf/mcp_config.json):
Codex CLI
Add to ~/.codex/config.toml:
If you set a token
With --token / OZ_MCP_TOKEN, every request needs an
Authorization: Bearer <token> header:
- Claude Code: append
--header "Authorization: Bearer <token>"toclaude mcp add. - Cursor / Windsurf: add
"headers": { "Authorization": "Bearer <token>" }next to"url". - Codex: add
http_headers = { "Authorization" = "Bearer <token>" }under[mcp_servers.oz].
Tools exposed
The full JSON inputSchema for each tool is emitted verbatim by tools/list.
See docs/MCP.md
for the protocol details, raw‑curl cheatsheet, and endpoint reference.
Endpoints
Quick health check:
Security
- Loopback by default. The server binds to
127.0.0.1; no traffic leaves the machine unless you opt in. - Non‑loopback requires a token. Binding to anything other than
127.0.0.1/::1without--token/OZ_MCP_TOKENis refused — the MCP tool surface can spawn the Oz CLI, so an unauthenticated public bind is never allowed. - Bearer auth covers every route (including
/health) when a token is set; comparison is constant‑time. - No persistence. Prompt content and run output are forwarded to the Oz CLI, never stored by the server.
There is no TLS termination — put the server behind an authenticated reverse proxy if you need HTTPS.
Trademarks & disclaimer
OzBridge is an independent project developed by Ivan Sena under the Sena Labs name. It is not affiliated with, endorsed by, sponsored by, or officially associated with Warp, Inc., Microsoft, GitHub, or the Visual Studio Code project.
Warp™ and Oz™ are trademarks of Warp, Inc. These names are used in this project nominatively — solely to describe that OzBridge interoperates with Warp Oz — and not to imply any sponsorship, endorsement, or affiliation.
OzBridge uses only Warp's documented, public interfaces — the oz
command‑line tool and the Model Context Protocol transport. It does not
modify, reverse‑engineer, embed, or create a derivative work of Warp's software,
and it is a complementary integration, not a competing product or service.
This software is provided "as is", without warranty of any kind. Use it at your
own risk. See
DISCLAIMER.md
for the full text.
License
MIT © Sena Labs
Source: packages/oz-mcp-server/README.md at commit e1707c3
Tools
0Version history
2- v2.0.0LatestOct 29, 2026
- v1.4.0Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
