The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the OCOLO Project Requests listing page.
Submit a data center colocation requirement to OCOLO on behalf of a human, from any AI agent. OCOLO is a colocation broker with a network of 270+ data center providers; one submission puts the requirement in front of all of them, and OCOLO returns the best options to the contact within 2-3 business days. No API key, no account: the contact confirms by email.
openapi.json, refreshed with ./sync-spec.sh; the live document is canonical)https://www.ocolo.io/api/v1/mcp/Response (201): request_id, status: pending_confirmation, status_url, a status_token
to keep, machine-readable next_steps, and a guidance object. Poll status with
Authorization: Bearer <status_token>.
Add https://www.ocolo.io/api/v1/mcp/ as a remote MCP server (no auth). Tools:
| Tool | Purpose |
|---|---|
get_broker_guidance | How OCOLO works and the etiquette below. Read first. |
submit_project_request | Submit the requirement (same fields as the REST body). |
get_project_request_status | Poll with request_id + status_token. |
server.json in this repo is the MCP Registry manifest.
request_id stays the same and the status
body then carries edited_by_contact: true and the final values under current).Every API response repeats this in its guidance field.
Rate limited per IP and per contact email; honour Retry-After and use idempotency_key
for safe retries. Bodies over 64 KB are rejected. Questions: info@ocolo.io.