Oz MCP Server

What sena-labs/oz-mcp-server MCP server does

The sena-labs/oz-mcp-server MCP server connects MCP clients to Warp Oz through the documented oz command-line interface. It supports both local execution in the current workspace and cloud execution through Warp Oz. The server returns structured run information so an agent can start work, inspect progress or output later, and review recent activity.

The standalone package provides the MCP portion of the broader OzBridge project. OzBridge also includes a VS Code extension with an @oz chat participant and Copilot Agent tools, but those editor features are separate from the standalone MCP server.

How it works

For local runs, the server invokes oz agent run with the supplied prompt and returns the complete run payload. Cloud runs are launched through Oz and consume Warp credits. Run identifiers can then be passed to the read-only status tool to retrieve status and output.

The server also exposes account model information. Clients can list model IDs and see the current default, then change the default by writing defaultModel to the workspace file .warp/warp-bridge.yaml.

The bridge communicates with MCP clients over HTTP and Server-Sent Events when started as the standalone package. The default endpoint is http://127.0.0.1:3847/sse. The same toolset can also be provided by the embedded server in the VS Code extension.

Setup and configuration

Install and start the standalone package with:

npx -y @sena-labs/oz-mcp-server

Warp Terminal must be installed, the oz executable must be on PATH, and the user must be signed in with oz login. These prerequisites apply because the bridge delegates execution to Warp’s CLI and documented interfaces.

An MCP client should connect to the local SSE endpoint. The README provides configurations for Claude Code and Cursor, and identifies Codex CLI as another supported client. The server can require a bearer token through the OzBridge mcpBearerToken setting; clients then send an Authorization: Bearer <token> header. The material does not specify an environment variable-based configuration for this setting.

Tools and capabilities

The six exposed MCP tools are:

• oz_agent_run: run a local Oz agent with a prompt and return its full payload.
• oz_agent_run_cloud: launch a cloud agent run.
• oz_run_get: retrieve a run’s status and output by ID.
• oz_run_list: list recent runs, filtering by all, active, completed, or a raw status, with a numeric limit.
• oz_list_models: list model IDs available to the account and report the default.
• oz_set_default_model: update the workspace default model in .warp/warp-bridge.yaml.

The sena-labs/oz-mcp-server MCP server therefore fits workflows that need both agent execution and basic run or model administration from an MCP client.

Limitations and notes

Cloud runs use Warp credits. The project is independent of Warp and is not affiliated with, endorsed by, or sponsored by Warp, Inc. It relies on Warp’s documented public interfaces, including the oz CLI, MCP, and WARP_OUTPUT_FORMAT; it does not modify or reverse-engineer Warp.

The server does not replace the Warp CLI or provide an independent agent runtime. Local execution depends on the installed CLI, while cloud execution depends on a signed-in Warp account and available credits. The supplied material does not establish support for every MCP client, so clients without documented configuration should be validated against the server’s SSE endpoint.