LabscoMCP early access ↗
sena-labsMCP SERVER

OzBridge

Drive Warp's Oz agent from Claude Code, Cursor or Codex — six tools over HTTP+SSE, local runs and cloud runs, with model selection exposed as a tool.

by sena-labs ↗Model Routing, Multi-Model Consultation & Cost ControlCommunity

LABSCO SUMMARY

One agent, reachable from whichever editor you are actually in.

The useful property is that the same six tools are what Copilot sees inside VS Code and what Claude Code or Cursor see over SSE — so switching editors does not mean switching agent setups. Making model selection a tool rather than a settings field is a small thing that matters in practice: the agent can move itself onto a cheaper or stronger model mid-workflow. Keep the local/cloud split in view, since one of those two run tools spends credits and the other does not.

What it is

An MCP server and VS Code extension that exposes Warp's Oz agents to any MCP-compatible client. Inside VS Code, Oz appears as an @oz chat participant and as tools Copilot Agent mode can invoke; outside it, the same toolset is served over HTTP+SSE so other clients drive Oz through it. It is an independent project built on Warp's documented public interfaces — the oz CLI, MCP and an output-format environment variable — and is not affiliated with Warp.

What you get

  • An Oz agent run started locally with a prompt, returning the full run payload — oz_agent_run
  • A cloud run launched, which consumes Warp credits — oz_agent_run_cloud
  • A run's status and output fetched by id, read-only — oz_run_get
  • Recent runs listed, filtered by all, active, completed or a raw status, with a numeric limit — oz_run_list
  • The model ids available to the account and the current default, read-only — oz_list_models
  • The default model set by writing defaultModel into the workspace configuration file, validated against the CLI's own model list — oz_set_default_model
  • Inside VS Code as well: slash commands covering the agent workflow, a sidebar with active runs, history, schedules and environments, and automatic injection of workspace path, active file, selection and diagnostics into every prompt

Requirements

Warp Terminal installed with the oz CLI on PATH, and a Warp account signed in via oz login. The bridge runs either standalone — npx -y @sena-labs/oz-mcp-server — or embedded in VS Code, which needs version 1.96.0 or newer and, to actually invoke @oz, the GitHub Copilot Chat extension. Both listen on http://127.0.0.1:3847/sse by default; setting a bearer token makes clients send an Authorization: Bearer header, and without one you omit the headers block. Published as ozbridge (1.4.0), MIT licensed. Cloud runs consume Warp credits — local runs do not.

Setup effort

One command — npx -y @sena-labs/oz-mcp-server