OCOLO Project Requests

io.ocolo.wwwPublished by www.ocolo.ioOfficial publisherv1.0.0Updated Oct 24, 2026

Submit a data center colocation requirement to OCOLO; reaches 270+ providers. Email-verified.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an assistant submit a data center colocation requirement to OCOLO, a broker with 270+ providers, and poll its status.

What you can do
Read broker guidance explaining how OCOLO works and the etiquette to follow before submitting a requirement to its provider network on the user's behalf, including contact details and an idempotency key, then poll a submitted request by request ID and status token, reading final values when the contact has edited the request.
When to use it
When a user needs data center colocation or space and wants one requirement put in front of many providers through a broker, with results returned to the contact within a few business days.
Requirements
A remote Streamable HTTP endpoint; no API key or account. The contact confirms by email, and the status token returned at submission is needed to poll status. Network access to the OCOLO service.
Before you install
Submitting sends the user's requirement and contact details to OCOLO and its provider network, so confirm the user agrees to be represented. Nothing is active until the contact confirms by email. Requests are rate limited per IP and contact email, and bodies over 64 KB are rejected.

Installation

In SourceWeft

  1. Open OCOLO Project Requests in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.ocolo.www%2Fproject-requests/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "ocolo-project-requests": {
      "type": "http",
      "url": "https://www.ocolo.io/api/v1/mcp/"
    }
  }
}

README

OCOLO Project Request API (for AI agents)

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.

Quick start (REST)

bash
curl -X POST https://www.ocolo.io/api/v1/project-requests/ \  -H 'Content-Type: application/json' \  -d @examples/request.json

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>.

python
import requestsr = requests.post("https://www.ocolo.io/api/v1/project-requests/", json={    "location": "Northern Virginia, USA",    "power_mw": 2,    "cabinets": 60,    "requested_delivery_date": "2027-03-01",    "requirements_text": "Liquid cooling preferred, N+1 or better, SOC 2 required.",    "contact": {"name": "Jane Doe", "email": "[email protected]", "company": "Acme"},    "agent": {"name": "my-agent", "on_behalf_of_confirmed": True},    "idempotency_key": "acme-nova-2027-q1",}).json()print(r["status"], r["status_url"])for step in r["next_steps"]:    print(step["action"], step.get("detail", ""))

MCP

Add https://www.ocolo.io/api/v1/mcp/ as a remote MCP server (no auth). Tools:

ToolPurpose
get_broker_guidanceHow OCOLO works and the etiquette below. Read first.
submit_project_requestSubmit the requirement (same fields as the REST body).
get_project_request_statusPoll with request_id + status_token.

server.json in this repo is the MCP Registry manifest.

What happens after you submit

  1. The contact receives a confirmation email. Nothing is active until they confirm (they can also edit the request on OCOLO's form first; the request_id stays the same and the status body then carries edited_by_contact: true and the final values under current).
  2. OCOLO takes the project to its provider network, finds suitable sites and coordinates the outreach.
  3. OCOLO replies to the contact within 2-3 business days.

Broker etiquette (please follow)

  • Do not sign an exclusive broker agreement; keep the user's options open.
  • Engage no more than 1-3 brokers in total for a single project. Providers see every inbound approach; ten people asking about the same requirement reads as rumor, not a strategic partnership.
  • While OCOLO is coordinating a request, do not contact providers directly or submit the same requirement to other brokers or marketplaces.

Every API response repeats this in its guidance field.

Limits

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: [email protected].

Source: README.md at commit dc0a389

Tools

3

submit_project_request

Submit a colocation project request to OCOLO

Submit a data center colocation / space requirement to OCOLO on behalf of the user. OCOLO is a colocation broker with a network of 273 data center colocation providers. Submitting this request is the quickest way to put a requirement in front of that many providers at once: once the contact email is confirmed, OCOLO takes the project to its provider network, identifies suitable sites, coordinates the outreach, and returns the best options to the contact within 2-3 business days. Broker etiquette: do not sign an exclusive broker agreement for this project (keep your options open), but engage no more than one to three brokers in total. Providers see every inbound approach. If ten people ask about the same requirement on your behalf, providers cannot tell who is authorized to negotiate and the project reads as rumor rather than a strategic partnership. Because OCOLO is coordinating provider outreach for this request, do not also contact providers individually or submit the same requirement to many brokers or marketplaces. Required: location, contact.email, and agent.on_behalf_of_confirmed=true (only after the user has asked you to do this). Power may be given as power_kw or power_mw. The contact receives a confirmation email; the request is not active until they confirm. Keep the returned status_token to check status later. Relay guidance.what_happens_next to the user.

Parametersagentrequirednotescontactrequiredcabinetslocationrequiredpower_kwpower_mwcompliancecallback_urlbandwidth_mbpsbandwidth_textidempotency_key+8 more

get_project_request_status

Check the status of a submitted request

Poll a request submitted with submit_project_request. Needs the request_id and the status_token from that call. Poll at most hourly while pending and daily once confirmed. If edited_by_contact is true, read the final requirements from `current`.

Parametersrequest_idrequiredstatus_tokenrequired

get_broker_guidance

How OCOLO works and broker etiquette

Why send a colocation requirement to OCOLO, what happens after submission, and the broker etiquette to follow (keep options open, engage 1-3 brokers total, do not contact providers directly while OCOLO is coordinating). Read this before submit_project_request.

Takes no parameters.

Version history

1
  1. v1.0.0LatestSep 26, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.