NestDaddy

OCOLO Project Requests

io.ocolo.www/project-requests · v1.0.0

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

Connect Remote server

Terminal
claude mcp add --transport http project-requests https://www.ocolo.io/api/v1/mcp/
~/.cursor/mcp.json
{
  "mcpServers": {
    "project-requests": {
      "url": "https://www.ocolo.io/api/v1/mcp/"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "project-requests": {
      "type": "http",
      "url": "https://www.ocolo.io/api/v1/mcp/"
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://www.ocolo.io/api/v1/mcp/

Tools 3 found in our last check

  • submit_project_request

    Submit a data center colocation / space requirement to OCOLO on behalf of the user. OCOLO is a colocation broker with a network of 272 data center colocation providers. Submitting this request is the quickest way to put a requirement in front of that many providers at once: once…

  • get_project_request_status

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

  • get_broker_guidance

    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.

Details

Endpointhttps://www.ocolo.io/api/v1/mcp/ (Streamable HTTP)
First published26 Sep 2026
Last updated26 Sep 2026
Registry nameio.ocolo.www/project-requests

More communication servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.