ORC8R Cloud speaks the Model Context Protocol (MCP), so an AI client — a claude.ai connector, Claude Code, Codex, Claude Desktop — can read and operate your organizations for you. The client acts as you: it sees what you can see, and anything your roles do not allow it is refused exactly as it would be in the web app. This page covers connecting a client, what it may do, and how to disconnect it.

The connector URL

The MCP endpoint is the address you sign in at, followed by /mcp. For ORC8R Cloud that is:

https://orc8r.com/mcp

There is no key to copy. The first time a client connects, it sends you to ORC8R to sign in and approve it, and from then on it holds its own revocable grant.

Add a claude.ai connector

In claude.ai, open Settings → Connectors, choose Add custom connector, and paste the connector URL. claude.ai sends you to ORC8R to sign in and approve it; once approved, the connector is available in your chats.

Connect Claude Code

Add the server once, then approve it:

claude mcp add --transport http orc8r https://orc8r.com/mcp

Run /mcp inside Claude Code, pick orc8r, and choose to authenticate. A browser window opens on ORC8R's approval page; sign in if you are not already, choose the scopes, and approve.

Connect Claude Desktop

In Claude Desktop, add the connector URL under Settings → Connectors → Add custom connector, the same way as in claude.ai. Alternatively, run a small local bridge by adding this to its configuration file (Settings → Developer → Edit Config) and restarting it:

{
  "mcpServers": {
    "orc8r": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://orc8r.com/mcp"]
    }
  }
}

Either way, the first connection opens ORC8R's approval page in your browser.

Connect Codex

Add the server to Codex (the CLI and the IDE extension share ~/.codex/config.toml):

codex mcp add orc8r --url https://orc8r.com/mcp

Codex sees that the server signs clients in with OAuth and opens ORC8R's approval page straight away; sign in if you are not already, choose the scopes, and approve. If you close that page, run codex mcp login orc8r later.

Codex identifies itself with a client document published on chatgpt.com, which ORC8R fetches the first time. A server that cannot reach chatgpt.com can have Codex register itself instead:

codex mcp login orc8r --oauth-client-registration dcr

Scopes

The approval page asks what the client may attempt:

Scope	Lets the client	Offered to
orc:read	read nodes, pools, projects, organizations, billing accounts, invoices and everything else you can read	everyone; always granted
orc:write	create, change and delete what your roles allow — pools, projects, members, budgets, the billing account, support requests	everyone; unticked until you tick it
orc:admin	zone-operator acts such as pricing and invoice corrections	ORC8R staff only

A scope never grants more than you already hold: with orc:write, a change your roles forbid is still refused, and reading an organization's bill needs the billing permission in that organization.

Some operations are never available to a client, whatever it was granted: creating or deleting API keys and agent tokens, listing or revoking connected apps, sign-in, agent enrollment, checkout and the payment portal, terminal sessions, and the live log and error streams.

What the client can do

A client is offered these tools:

Tool	Does
search_operations	Finds the API operations this connection may call, by keyword
describe_operation	Shows one operation's parameters and request body
call_read_operation	Performs a read
call_write_operation	Performs a change; offered only with orc:write
list_nodes, get_node	Read the nodes you can see, or one of them
read_node_logs	Reads up to 500 lines (64 KiB) of one node's logs, oldest first, and stops — it never follows the log
get_org_usage	Reads an organization's bill so far this period: the upcoming invoice and its lines

Reads and changes are separate tools, so you can let a client read freely and still have it ask before it changes anything. Every operation it calls is one of the API reference's; the billing ones are described in Billing.

Disconnect a client

Every client you approved is listed under Connected apps on your Profile page, with its scopes and when it was last used. Revoke disconnects it at once: its next request is refused. Approving the same client again replaces its scopes and ends its earlier tokens, and changing or resetting your password disconnects every client you connected.

ORC8R's administrators can also revoke a client you connected — for instance if its access looks compromised. It then disappears from your Connected apps just as if you had revoked it.

A client that stays connected refreshes its access on its own. If it goes unused for 30 days, or 90 days pass since you approved it, you approve it again.

Privacy and terms

What a connected client reads through ORC8R is handled as described in the privacy policy, and using the endpoint is covered by the terms of service. What the client itself does with it is covered by that client's own terms.

Related pages

• API reference — every operation a client can call.
• API keys — for scripts and pipelines rather than AI clients.
• Billing — plans, invoices and what get_org_usage reads.