Skip to main content
Connect Claude, Cursor, ChatGPT, or Devin to Ornn Compute over MCP Ornn runs a hosted Model Context Protocol server for finding capacity, managing reservations, following telemetry and logs, managing Kubernetes or Slurm, reselling, and billing. Use the tools returned by your connected server; availability depends on your organization and role. Open a shell with the CLI: ornn connect <machine-id>.

Connect

Add this server URL to your MCP client’s configuration:
Your client will prompt you to sign in with your Ornn account via OAuth and approve the connection on the consent screen. You can revoke access at any time from Connected agents. If you change the login email on your Ornn account, existing MCP tokens and pending authorization codes are revoked automatically. Restart any unfinished connection and reconnect the agent after the email change completes. This also applies to authorization or refresh requests that overlap the change.

Verify and reconnect

After connecting, ask your client to list the available tools and call identity_whoami. Confirm that it returns your Ornn account and organization, then try the relevant read tool, such as ornn_reservations_list. If your client reports that authorization is required or cannot refresh its login, reconnect the Ornn server through the client’s sign-in flow. Codex users can run codex mcp login ornn. Reload the connection or start a fresh chat after approving access so the client discovers the current tools. The server’s health page alone does not verify your connection. Never paste an access token into a chat or troubleshooting report.

Tools

Prices in market tools are integer micro-USD per GPU-hour: 2500000 is $2.50. Down payments are integer cents. Tools that spend money, mutate a bid, offer, purchase, relist, reservation, or access state, or issue a non-GET ornn_api call require an explicit confirm: true argument; without it, they return a preview of what would happen instead of executing. Market results never include who supplies or relisted the capacity. See Spot, Reserve, the Market, and Relist capacity for how each market works.

Custom OAuth clients

Send OAuth query parameters with a URL encoder. The callback returns the same decoded state value when you approve or decline the connection, including spaces, +, and other reserved characters. Compare the decoded callback value with the original state to verify the connection request.