@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 (oz_agent_run, oz_run_list, …) over an HTTP + Server‑Sent‑ Events transport, so any MCP client can launch and inspect Oz runs.

Requirements

• Node.js ≥ 20.19
• The Oz CLI installed and on your PATH (or pointed at via OZ_PATH). Download Warp from https://www.warp.dev/download — the oz command ships with it. Verify with oz --version.

The server only ever shells out to the documented oz CLI; it does not embed, modify, or reverse‑engineer any Warp software.

Quick start

Run the server with npx — no install step needed:

npx @sena-labs/oz-mcp-server

It binds to 127.0.0.1:3847 and prints:

[oz-mcp-server] Listening on http://127.0.0.1:3847
[oz-mcp-server] SSE endpoint : http://127.0.0.1:3847/sse
[oz-mcp-server] Health check : http://127.0.0.1:3847/health
[oz-mcp-server] Press Ctrl+C to stop.

Leave it running, then point your MCP client at the SSE endpoint (http://127.0.0.1:3847/sse) — see MCP client setup (HTTP + SSE).

Pin a port and a bearer token instead of the defaults:

npx @sena-labs/oz-mcp-server --port 3847 --token my-secret

Install it globally if you'd rather not re‑download on each run:

npm install -g @sena-labs/oz-mcp-server
oz-mcp-server --help

Configuration

Settings resolve in this order (highest precedence first):

1. CLI flags
2. Environment variables
3. ./.warp/warp-bridge.yaml (current working directory), then ~/.warp/warp-bridge.yaml
4. Compiled‑in defaults

CLI flags

Environment variables

OZ_PATH=/usr/local/bin/oz \
OZ_MCP_PORT=3847 \
OZ_MCP_TOKEN=my-secret \
npx @sena-labs/oz-mcp-server

On Windows PowerShell, set variables with $env: first:

powershell

$env:OZ_MCP_TOKEN = "my-secret"; npx @sena-labs/oz-mcp-server

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. Use this for Claude Desktop, mcp-proxy, and registry sandboxes (e.g. Glama). No port, no token.
• HTTP + SSE (default) — the server listens on a port; clients connect by URL. Use this for Claude Code, Cursor and Codex.

# stdio (spawned by the host)
npx @sena-labs/oz-mcp-server --stdio

# HTTP + SSE (default)
npx @sena-labs/oz-mcp-server --port 3847

Claude Desktop (stdio)

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "oz-bridge": {
      "command": "npx",
      "args": ["-y", "@sena-labs/oz-mcp-server", "--stdio"]
    }
  }
}

MCP client setup (HTTP + SSE)

For URL-based clients, start the server (above), then add the endpoint to your client. These snippets mirror docs/MCP.md; drop the Authorization header if you didn't set a token.

Claude Code

Add to ~/.claude.json:

{
  "mcpServers": {
    "oz-bridge": {
      "type": "sse",
      "url": "http://127.0.0.1:3847/sse",
      "headers": {
        "Authorization": "Bearer my-secret"
      }
    }
  }
}

Or register it from the CLI:

claude mcp add --transport sse oz-bridge http://127.0.0.1:3847/sse \
  --header "Authorization: Bearer my-secret"

Cursor

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "oz-bridge": {
      "url": "http://127.0.0.1:3847/sse",
      "headers": {
        "Authorization": "Bearer my-secret"
      }
    }
  }
}

Codex CLI

Add to ~/.codex/config.toml:

[[mcp.servers]]
name = "oz-bridge"
url = "http://127.0.0.1:3847/sse"
authorization = "Bearer my-secret"

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:

curl http://127.0.0.1:3847/health

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 / ::1 without --token / OZ_MCP_TOKEN is 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