reoclo mcp

reoclo mcp [options]

Starts the Model Context Protocol server embedded in the CLI binary. Reads MCP requests from stdin and writes responses to stdout. Uses OAuth credentials from your active CLI profile (populated by reoclo login). No API key required.

Options

Flag	Default	Description
--profile <name>	active profile	Use a specific profile’s stored credentials.

REOCLO_PROFILE is honored as an env-var equivalent of --profile.

Examples

Run the server with the active profile:

reoclo mcp

Use a non-default profile (handy when an editor’s MCP config targets a different tenant):

reoclo mcp --profile staging

Editor configuration

Add this to your editor’s MCP config (.mcp.json, .cursor/mcp.json, .vscode/mcp.json, etc.):

{
  "mcpServers": {
    "reoclo": {
      "command": "npx",
      "args": ["-y", "@reoclo/cli", "mcp"]
    }
  }
}

If @reoclo/cli is installed globally, you can drop the npx -y wrapper:

{
  "mcpServers": {
    "reoclo": {
      "command": "reoclo",
      "args": ["mcp"]
    }
  }
}

To target a specific profile from the editor config, add env:

{
  "mcpServers": {
    "reoclo": {
      "command": "npx",
      "args": ["-y", "@reoclo/cli", "mcp"],
      "env": { "REOCLO_PROFILE": "staging" }
    }
  }
}

See MCP server (embedded in the CLI) and MCP Server Setup for editor-by-editor instructions and the full tool catalog.

Tools available

The server exposes tenant-scoped tools for servers, applications, deployments, domains, logs, monitors, status pages, and scheduled operations. Tool visibility is filtered by the OAuth-authenticated user’s tenant role.

Exit codes

Code	Meaning
0	Server exited cleanly (e.g. client closed stdin)
1	Bootstrap failure (no active profile, network error contacting /auth/me)
3	Authentication failure (token refresh failed; re-run reoclo login)

Related

• MCP server overview — why this exists and how it integrates with the CLI
• MCP Server Setup — editor-by-editor instructions
• CLI Authentication — reoclo login and profile management