Local stdio server

The hosted OAuth connection is the easiest starting point. Local stdio is available when you have access to the Uno repository. The MCP packages are private workspace packages; do not assume they are published on npm.

BuildCopy Anchor Link

Use Node.js 24 or newer and pnpm 11.1.2. From the repository root:

pnpm install --frozen-lockfile
pnpm mcp:build

Sign inCopy Anchor Link

For an email/password account:

UNO_API_URL=https://api.uno.engineering pnpm --filter @daytona-uno/uno-mcp start login

The CLI prompts for your credentials. It does not store the password. It saves a refreshable session at ~/.config/uno/uno-mcp-session.json with owner-only permissions. UNO_SESSION_FILE selects another file.

The CLI does not open browser OAuth for provider-only accounts. An existing user access token can be supplied as UNO_ACCESS_TOKEN; it takes precedence over the saved session and needs replacement when it expires. Never supply a service-role key.

Configure your clientCopy Anchor Link

{
  "mcpServers": {
    "uno": {
      "command": "node",
      "args": ["/absolute/path/to/uno/packages/uno-mcp/dist/src/cli.js"],
      "env": { "UNO_API_URL": "https://api.uno.engineering" }
    }
  }
}

Use get_workspaces to discover your workspaces. Local stdio has the shared v1 catalog; the uno_* convenience aliases are hosted-only.

TroubleshootCopy Anchor Link

Read the server's stderr log in your client. If the session expired, run login again. If it belongs to another backend, sign in against the configured UNO_API_URL. Remote origins require HTTPS; HTTP is allowed only for localhost.

The default local API origin is http://localhost:3000. Responses and timeouts are bounded; use pagination for large results.