@uno4/mcp — Uno for your agent

MCP server that gives an AI agent hands on Uno: create boxes, run commands in them, deploy from git, read deploy logs, reveal database DSNs.

A thin wrapper over the public API (https://console.uno4.dev/api/v1/openapi.yaml) — 15 curated tools, not a dump of every endpoint.

Setup

You need an API key: console.uno4.dev → Account → API key.

Claude Code

claude mcp add uno --env UNO_API_KEY=YOUR_KEY -- npx -y @uno4/mcp

Claude Desktop / Cursor (mcpServers in the config file):

{
  "mcpServers": {
    "uno": {
      "command": "npx",
      "args": ["-y", "@uno4/mcp"],
      "env": { "UNO_API_KEY": "YOUR_KEY" }
    }
  }
}

Then just talk: "spin up a 1 GB box and run my scraper there every time I say go" — the agent calls create_box, box_run, get_run itself.

Tools

| Tool | What it does | |---|---| | get_catalog | Plans, box templates, prices — source of truth for slugs | | account_overview | Balance, subscription, pool usage | | list_boxes / get_box / create_box | Box CRUD | | box_action | start / stop / reboot / sleep / wake / archive / unarchive | | box_run / get_run | Run a command in a box (wakes it, sleep policy after; async via wait_s + polling) | | list_databases / get_database_dsn | Managed Postgres; DSN reveal is audit-logged | | list_git_services / trigger_deploy / deployment_logs | Git deploy | | list_ssh_keys / add_ssh_key | Account SSH keys (boxes are key-only) | | search_api / api_call | Escape hatch: search the full API (~200 ops) by keyword and call anything — snapshots, domains, DNS, secrets, buckets, scheduled tasks… |

The 15 dedicated tools cover the everyday 90%; search_api + api_call cover the rest without dumping 200 tool schemas into the agent's context.

Env

• UNO_API_KEY — required
• UNO_API_BASE — override API base (default https://console.uno4.dev)

Development

npm install
UNO_API_KEY=... npm run smoke   # live read-only checks against prod

Adding a tool? Check the OpenAPI spec, not your memory: https://console.uno4.dev/api/v1/openapi.yaml.