MCP over HTTP
Infrastructure your agents can operate
90+ MCP tools across the lifecycle. Every call runs the same ownership checks and audit trail as the dashboard.
Keys and OAuth on every plan once approved.
claude code · terminal
$ claude mcp add cloud-claude \ --transport http https://api.cloud-claude.com/mcp \ --header "Authorization: Bearer cc_tenant_…"
ServerMCP endpoint
- Endpoint
- https://api.cloud-claude.com/mcp
- Transport
- HTTP · JSON-RPC 2.0 · MCP
- Auth
- Bearer key or OAuth 2.1
Connect
Connect any MCP client
Point Claude Code, Claude Desktop, or your own client at one endpoint.
Claude Code
HTTP transport with a tenant key.Claude Desktop
Custom Connector over browser OAuth 2.1.Any MCP client
Authenticate with a bearer key or OAuth 2.1.
Tool surface
Operate the full lifecycle over MCP.
Every dashboard action is also an MCP tool. 90+ of them, one per verb.
Full lifecycle
Create, deploy, add domains, roll back.Three recipes
full_deploy, clone_to_staging, promote_to_production.Health you can poll
Component health, latency, and 90-day history.https://status.cloud-claude.com/api/status.json
Give your agents production infrastructure
Join the waitlist. Keys and OAuth on every plan. No card, no trial clock.