Skip to content
Reoclo Reoclo Reoclo Docs

MCP server (embedded in the CLI)

The Reoclo CLI ships with an embedded Model Context Protocol server. Running reoclo mcp starts the server over stdio. It uses the OAuth credentials from your active CLI profile (populated by reoclo login) — there are no API keys to manage.

Quick start

Section titled “Quick start”
Terminal window
reoclo login
reoclo mcp

The server reads MCP requests from stdin and writes responses to stdout.

Editor configuration

Section titled “Editor configuration”

The full set of editor-specific snippets lives in the MCP Server Setup guide. The common shape is:

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

If you have the CLI installed globally (npm i -g @reoclo/cli), you can use:

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

Claude Code

Section titled “Claude Code”
Terminal window
claude mcp add reoclo -- npx -y @reoclo/cli mcp

Profiles

Section titled “Profiles”

The server uses your active profile by default. To target a different tenant from a specific editor without changing the global default:

Terminal window
reoclo mcp --profile staging

Or set REOCLO_PROFILE in the editor’s env block.

Tools available

Section titled “Tools available”

reoclo mcp exposes tenant-scoped tools for servers, applications, deployments, domains, logs, monitors, status pages, and scheduled operations. The visible tool set is filtered by the OAuth-authenticated user’s role. See MCP Server Setup for the full catalog.