Skip to content
Reoclo Reoclo Reoclo Docs

MCP Server Setup

The Reoclo CLI ships with a built-in Model Context Protocol server. Any MCP-compatible client (Claude Code, Cursor, VS Code, Zed, JetBrains AI, Cline, etc.) can drive Reoclo through it — servers, applications, deployments, domains, logs, monitors, status pages, scheduled operations.

There are no API keys to mint or paste. Authentication is handled by reoclo login (OAuth device flow); the MCP server reads the resulting credentials from your CLI profile each time it starts.

Prerequisites

Section titled “Prerequisites”
  1. Reoclo CLI — install it once:
    Terminal window
    npm i -g @reoclo/cli
    # or use npx and skip the global install
  2. Authenticate — runs an OAuth device flow in your browser:
    Terminal window
    reoclo login
    See CLI Authentication for profile management and headless options.
  3. Node.js 18+ — required to run the CLI via npx.

Once reoclo whoami confirms you are authenticated, you are ready to wire up your editor.

Claude Code

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

This registers the server immediately. Restart Claude Code to pick it up.

Config file

Section titled “Config file”

Add to .mcp.json in your project root (or ~/.claude/mcp.json for global access):

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

Verify

Section titled “Verify”

In Claude Code, type:

/mcp

You should see reoclo listed with its tools. Try asking: “List my servers” or “Show recent deployments”.

Cursor

Section titled “Cursor”

Add to .cursor/mcp.json in your project root:

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

Restart Cursor. The MCP server appears in Settings > MCP once connected.

Windsurf

Section titled “Windsurf”

Add to ~/.codeium/windsurf/mcp_config.json:

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

Restart Windsurf. Cascade picks up the server and lists available tools automatically.

VS Code (GitHub Copilot)

Section titled “VS Code (GitHub Copilot)”

VS Code supports MCP servers through GitHub Copilot Chat (agent mode). Add to .vscode/mcp.json in your project root:

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

After saving, open Copilot Chat in agent mode — the Reoclo tools become available.

Zed

Section titled “Zed”

Add to your Zed settings (~/.config/zed/settings.json):

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

Restart Zed. The server appears in the Assistant panel’s context server list.

JetBrains (IntelliJ, WebStorm, PyCharm, etc.)

Section titled “JetBrains (IntelliJ, WebStorm, PyCharm, etc.)”

JetBrains IDEs support MCP through AI Assistant. Add to .idea/mcp.json in your project root:

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

Restart the IDE. The MCP server appears in the AI Assistant tool window.

Cline

Section titled “Cline”

Add via the Cline MCP settings UI (Cline > MCP Servers > Add), or edit ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json (macOS) directly:

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

After saving, Cline shows a connection indicator next to the server name. Click it to verify the tools loaded.

Other MCP clients

Section titled “Other MCP clients”

Any MCP-compatible client can use the server. Run it directly:

Terminal window
npx -y @reoclo/cli mcp

The server communicates over stdio. Point your client at this command and it discovers tools automatically.

Available tools

Section titled “Available tools”

The MCP server exposes the same surface as the CLI. Permissions match the OAuth-authenticated user’s tenant role — a viewer role will only see read tools, a developer role gets read + write, etc.

CategoryTools
Serverslist_servers, get_server, get_server_metrics, get_server_health, check_server_health, list_containers, inspect_container, restart_container, port_scan
Applicationslist_applications, get_application, get_app_config, update_app_config, trigger_deploy
Deploymentslist_deployments, get_deployment, get_deployment_logs, get_deployment_stages, get_deployment_build_log
Domainslist_domains, get_domain, get_dns_overview, check_domain_health, add_domain, verify_domain
Logssearch_logs, live_logs, get_system_logs, get_log_usage, get_server_log_sources, get_log_stats
Monitorslist_monitors, get_monitor, create_monitor, update_monitor
Status Pageslist_status_pages, get_status_page, create_incident, update_incident
Scheduled Opslist_scheduled_operations, get_scheduled_operation, create_scheduled_operation, trigger_scheduled_operation
Otherwhoami, list_repositories, list_env_vars, set_env_var, get_dashboard, get_audit_log

Configuration

Section titled “Configuration”

The MCP server reads its configuration from your CLI profile. Optional overrides:

VariableDescription
REOCLO_PROFILEUse a specific CLI profile (defaults to the active one)
REOCLO_API_URLOverride the API endpoint (defaults to the profile’s api_url)

There is no REOCLO_API_KEY variable — credentials come from reoclo login, not env vars.

Troubleshooting

Section titled “Troubleshooting”

Server not appearing

Section titled “Server not appearing”
  • Verify Node.js 18+ is installed: node --version
  • Test the server manually: npx -y @reoclo/cli mcp (it should print MCP protocol JSON on stdin/stdout)
  • Make sure your editor restarted after config changes

”Not authenticated” error

Section titled “”Not authenticated” error”

Run reoclo whoami. If it errors, run reoclo login to refresh credentials.

Wrong tenant

Section titled “Wrong tenant”

If you belong to multiple tenants, the MCP server uses the profile’s active tenant. Either:

  • Set REOCLO_PROFILE in the MCP env block to a profile that points at the right tenant, or
  • Run reoclo profile use <name> to change the default profile.

No tools listed

Section titled “No tools listed”

The tool set is filtered by the OAuth-authenticated user’s role. Confirm with reoclo whoami that the active profile is on the expected tenant with the expected role.

Token refresh failed

Section titled “Token refresh failed”

OAuth tokens refresh automatically. If you see a session-expired error, run reoclo login once to restart the device flow.

Next steps

Section titled “Next steps”