# OneOver MCP Server

Connect AI agents to OneOver via the [Model Context Protocol](https://modelcontextprotocol.io/) (MCP). The server is remote HTTP. There is no package to install. It exposes the same Business API as tools — chat, image, video, audio, models, usage, apps, assets, jobs, and billing.

## Endpoint

```
https://api.oneover.com/functions/v1/mcp
```

**Transport:** Streamable HTTP (JSON-RPC 2.0)

**Auth:** `Authorization: Bearer oo_live_<secret>` (same API key as the REST API)

## Tools

| Tool | Scope | Description |
|------|-------|-------------|
| chat | chat | Stateless chat completion |
| generate_image | images | Generate an image from a prompt |
| generate_video | video | Submit async video job (returns request_id) |
| check_video | video | Poll video job status |
| generate_audio | audio | Speech or music generation |
| list_models | usage | List org-visible models |
| get_usage | usage | Balance or usage reporting |
| run_app | apps | Run a Play app |
| list_assets | assets | List library assets |
| get_job | jobs | Poll a generation job |
| build_create | code | Start a Code Studio build from a prompt (returns build_id, build_project_id) |
| build_iterate | code | Follow-up instruction on an existing build |
| build_status | code | running, complete, failed, or stopped, plus files and share link |
| build_get_files | code | Read build files |
| build_stop | code | Stop a running build, keeping written files |
| build_publish | code | Unlisted share link at oneover.com/p/<slug> |
| create_topup | billing | Stripe Checkout URL |

Builds are async like video: call `build_create`, then poll `build_status` until it is `complete` or `failed`. The key needs the `code` scope. Credits are charged to the key's org. Finished builds are saved to the account library, so they survive anything that happens to a chat thread.

Video is async: call `generate_video`, then poll with `check_video` or `get_job` until status is `complete` or `failed`.

Protocol: `2025-03-26` with negotiation for `2024-11-05`.

## Cursor

Add to your MCP config (`.cursor/mcp.json` or Cursor Settings → MCP):

```json
{
  "mcpServers": {
    "oneover": {
      "url": "https://api.oneover.com/functions/v1/mcp",
      "headers": {
        "Authorization": "Bearer oo_live_YOUR_KEY"
      }
    }
  }
}
```

## Claude Desktop

Add to `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS):

```json
{
  "mcpServers": {
    "oneover": {
      "url": "https://api.oneover.com/functions/v1/mcp",
      "headers": {
        "Authorization": "Bearer oo_live_YOUR_KEY"
      }
    }
  }
}
```

## ChatGPT

If your ChatGPT plan supports custom MCP connectors, add the same URL and Authorization header in Settings → Connectors.

## Claude Code

```
claude mcp add --transport http oneover https://api.oneover.com/functions/v1/mcp --header "Authorization: Bearer oo_live_YOUR_KEY"
```

## Get a key

Mint at https://oneover.com/developers/dashboard — a personal org is created automatically. New keys include the scopes these tools need.

## REST

For REST integration without MCP, start at https://oneover.com/developers/quickstart.md or https://oneover.com/openapi.json.