Skip to main content

CLI and MCP

Use Phaseo from your terminal with the CLI, or connect an AI client through MCP. Both use Phaseo OAuth, but they are designed for different jobs.

Phaseo CLI

Use the CLI when you need to create or change Phaseo resources, script a workflow, or inspect account data from a shell.

Install and sign in

Interactive terminals use browser OAuth by default. For SSH, CI, and headless environments, use device authorization:

Common workflows

Use --json when another tool or script needs structured output. Secret values are displayed only by commands that explicitly create or reveal them.

Phaseo CLI guide

See authentication options, key management, workspaces, guardrails, and the complete command workflow.

Phaseo MCP

Connect the Phaseo MCP server when you want an AI client to answer questions using live model, pricing, provider, usage, and workspace data.

Server URL

https://mcp.phaseo.app/mcp

Connect from Codex

The login command opens Phaseo OAuth. Choose a workspace and approve the requested read scopes, then confirm the connection:
For another MCP client, add the same URL as a remote Streamable HTTP server. The client must support OAuth discovery, authorization code with S256 PKCE, and the MCP resource parameter.

What the MCP can read

  • models, providers, benchmark rankings, pricing, and cost estimates
  • credits, activity, analytics, request logs, and generation metadata
These tools are read-only. They never return prompts, responses, or secret values.

Manage your account (optional)

To let an agent change your Phaseo workspace, connect with the manage URL instead: https://mcp.phaseo.app/mcp?access=manage
When you sign in, the consent screen lists each permission the connection asks for, such as managing API keys or deleting budgets, and marks it Read, Write, or Delete. Untick any you do not want. The agent only gets tools for the permissions you allow, and Phaseo still checks your workspace role on every change, so a member who is not an owner or admin cannot change admin-only settings this way. If you already connected with the read-only URL, switch the client to the manage URL and sign in again. To go back to read-only access, reconnect with the plain URL or revoke the app under Settings → Connected Apps. Tools that change or delete something are marked as such, so MCP clients that support it ask you before each call. A new API key or webhook signing secret is shown once in the tool result and cannot be shown again. Stored provider keys and destination credentials are never returned. The MCP has no billing, payment, workspace, member, management-key, or OAuth-app tools. Use the dashboard, CLI, or Management API for those.

Docs MCP

The Docs MCP is a separate endpoint for searching and reading Phaseo documentation. It does not access your account or workspace.
Use it when a coding assistant needs current API examples, integration guidance, or feature documentation.

Docs MCP guide

Connect the documentation server to Codex, Claude Code, Cursor, OpenCode, or VS Code.

Phaseo plugin

The Phaseo plugin bundles the Phaseo MCP, the Docs MCP, and the Phaseo agent skills for integration, migration, model selection, usage monitoring, the SDKs, and the CLI. Install it once instead of connecting each piece yourself.

Claude Code

Run /mcp and sign in to plugin:phaseo:phaseo to connect your Phaseo account. Skills load when a request matches them, or you can run one directly, such as /phaseo:phaseo-gateway.

Codex

The last command opens Phaseo OAuth for the Phaseo MCP. Skills load when a request matches them.

Choose the right interface

  • Use the CLI to create keys, change settings, manage workspaces, or automate administrative workflows.
  • Use the Phaseo MCP to give an AI client safe access to live Phaseo data.
  • Use the Docs MCP to give a coding assistant current Phaseo documentation without account access.
  • Use the Phaseo plugin to set up both MCP servers and the Phaseo skills in Claude Code or Codex at once.
Last modified on October 28, 2026