OzBridge MCP Server

Standalone MCP server bringing Warp™ Oz™ agents to Claude Code, Cursor, Codex and any MCP client — no VS Code required. Independent project, not

Local serverstdio

What is the OzBridge MCP Server?

Standalone MCP server bringing Warp™ Oz™ agents to Claude Code, Cursor, Codex and any MCP client — no VS Code required. Independent project, not affiliated with

The short version

Run it embedded in VS Code — where Oz shows up natively as the @oz Chat Participant and as Agent-Native Language Model Tools that Copilot Agent mode invokes autonomously — or expose the same Oz toolset over HTTP+SSE so Claude Code, Cursor and Codex drive Oz too. No editor at all? Ship the standalone @sena-labs/oz-mcp-server and point any MCP client at it.

  • @oz Chat Participant — — interact with Warp Oz agents from the VS Code chat panel
  • Agent-Native Language Model Tools — — Copilot Agent mode can invoke Warp Oz directly, without typing @oz
  • One-click model selection — — pick the Oz model from a QuickPick (OzBridge: Select Model), the $(sparkle) status-bar indicator, or @oz /models — no hand-typing an id into settings. Agents switch it via the MCP tools oz_list_models / oz_set_default_model
  • Warp sidebar + status bar — — Activity Bar view with Active Runs, History, Schedules, Environments, MCP Servers and Secrets, plus a $(cloud) Warp: N active indicator and a $(sparkle) model indicator (click to switch)
  • Context variables & Warp handoff — — inline #warp.env, #warp.profile, #warp.model, #oz.history and #oz.run/ tokens expanded into any /run or /cloud prompt, plus a one-click handoff to an actual Warp terminal
  • 9 slash commands — covering the full agent workflow: /run, /cloud, /status, /history, /schedule, /models, /mcp, /config, /init

What it needs from you

  • VS Code ≥ 1.96.0 (the @oz participant requires the stable Chat Participant API; LM Tools additionally require vscode.lm.registerTool). - Warp Terminal installed, with the oz CLI accessible in PATH. - A Warp account, signed in via oz login. - GitHub Copilot Chat extension (optional but required to actually invoke @oz or use Agent mode tools).

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
oz_run_local#ozRunLocal
oz_run_cloud#ozRunCloud
oz_get_run#ozGetRun
oz_list_runs#ozListRuns
oz_agent_runRun oz agent run locally with a prompt. Returns the full run payload.
oz_agent_run_cloudLaunch a cloud run. **Consumes Warp credits.**
oz_run_getFetch a run's status and output by id. Read-only.
oz_run_listList recent runs; filter by all / active / completed / raw status, plus a numeric limit.
oz_list_modelsList the AI model ids available to the account and report the current default. Read-only.
oz_set_default_modelSet the default Oz model by writing defaultModel into the workspace .warp/warp-bridge.yaml.

How to install the OzBridge MCP Server

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

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • VS Code ≥ 1.96.0 (the @oz participant requires the stable Chat Participant API; LM Tools additionally require vscode.lm.registerTool). - Warp Terminal installed, with the oz CLI accessible in PATH. - A Warp account, signed in via oz login. - GitHub Copilot Chat extension (optional but required to actually invoke @oz or use Agent mode tools).

Example prompts to try

  • “Use OzBridge to oz run local.”
  • “Use OzBridge to oz run cloud.”
  • “Use OzBridge to oz get run.”

Frequently asked questions

Standalone MCP server bringing Warp™ Oz™ agents to Claude Code, Cursor, Codex and any MCP client — no VS Code required. Independent project, not affiliated with Confirm the tools offered by your installed version in the connected client. Tool availability and permissions depend on the server and account configuration.