MCP server (embedded in the CLI)

Reoclo speaks the Model Context Protocol in two ways: a hosted server at https://mcp.reoclo.com/mcp, and a local server embedded in the CLI. Both expose the same tenant-scoped tools with the same permissions and audit trail.

Hosted server (remote connector)

Point a remote MCP client at https://mcp.reoclo.com/mcp. The server uses OAuth: the client registers itself, then sends you through the Reoclo login and consent flow, where you select the organizations to grant.

In Claude, open Settings → Connectors → Add custom connector and enter the URL. In other MCP clients, add a remote server with Streamable HTTP transport and the same URL. No API key or manual client registration is needed.

The hosted server holds no credentials. It forwards each tool call to the Reoclo API with your own OAuth token, so your role and organization grants apply unchanged.

Working across organizations

The hosted server can act on every organization you selected when you authorized the connector. It never assumes one: every tool call names its organization.

1. Call whoami. The accessible_tenants list shows each organization’s slug and id.
2. Pass organization (the slug or the id) on every other tool call, for example list_servers with organization: "dortdash".

If a call omits organization, the tool returns an error that tells you to call whoami. If you name an organization the connector was not authorized for, re-authorize the Reoclo connector and select it during consent.

The local server (reoclo mcp) works differently: it is bound to one organization for the life of the process, chosen by reoclo init, --org or $REOCLO_ORG, and its tools take no organization argument.

Local server (CLI, stdio)

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

reoclo login
reoclo mcp

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

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

claude mcp add reoclo -- npx -y @reoclo/cli mcp

Profiles

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

reoclo mcp --profile staging

Or set REOCLO_PROFILE in the editor’s env block.

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.

Machine-readable manifest

A server manifest in the MCP registry server.json format is published at https://reoclo.com/.well-known/mcp.json. Agent tooling can read it to discover the hosted endpoint (remotes), the npm package name, the transports, and the launch arguments without parsing this page.