Skip to main content
Glama
sena-labs

OzBridge

by sena-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
oz_agent_runA

Run a Warp Oz AI agent locally in the host workspace and return its full output synchronously. Runs oz agent run with your prompt and blocks until the agent finishes. Use for local coding tasks — refactor, write/run tests, debug, explain code — that should NOT consume cloud credits; for cloud execution call oz_agent_run_cloud instead. NOT read-only: the agent may create or modify files in the workspace. Requires the oz CLI on PATH (install Warp).

oz_agent_run_cloudA

Launch a Warp Oz AI agent in Warp's cloud (not on the local machine). ⚠️ CONSUMES WARP CREDITS — confirm with the user before calling. Returns the run id immediately WITHOUT waiting for completion; poll the terminal status and output with oz_run_get, or find the run later via oz_run_list. Requires the oz CLI on PATH and a Warp account with cloud credits.

oz_run_getA

Fetch the current status and output of a single Warp Oz run by its id. Read-only and idempotent — safe to call repeatedly while polling a cloud run to completion (SUCCEEDED / FAILED). Typically called after oz_agent_run_cloud, which returns the run id; ids also come from oz_run_list.

oz_run_listA

List recent Warp Oz runs (id, status, timing), newest first. Read-only. Use to discover run ids to pass to oz_run_get, or to review recent agent activity.

oz_list_modelsA

List the AI model ids available to the connected Warp Oz account (from oz model list) and report the current default. Read-only; takes no arguments. Call this first to discover valid ids before passing model to oz_agent_run / oz_agent_run_cloud, or before oz_set_default_model.

oz_set_default_modelA

Set the default Oz model for every OzBridge surface by writing defaultModel into the workspace .warp/warp-bridge.yaml (the highest-precedence config source). Persistent side effect: edits that file on disk. The id is validated against oz model list when reachable. Requires a workspace root (an extension workspace, or --cwd for the standalone server).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a distinct purpose: local vs cloud execution, listing models, fetching run status, listing runs, setting default model. No ambiguity between tools.

Naming Consistency5/5

All tools use consistent snake_case naming with 'oz_' prefix and clear verb_noun pattern (e.g., oz_agent_run, oz_list_models, oz_run_get).

Tool Count5/5

6 tools cover the core workflow of running AI agents (local/cloud, model discovery, status polling, configuration) without being too many or too few.

Completeness4/5

Covers all essential operations: run locally, run in cloud, list models, check status, list runs, set default. Lacks a cancel/abort for cloud runs, which is a minor gap.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive

Resources