Index / MCP servers / OCOLO Project Requests

OCOLO Project Requests MCP server

Connect OCOLO Project Requests and your agent gets 3 tools, among them get_broker_guidance, get_project_request_status, submit_project_request. It answers at https://www.ocolo.io/api/v1/mcp/ over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 27 September 2026; the last check, on 11 November 2026, succeeded.

Status
Answering
Tools
3
Official
yes, served from ocolo.io
Reliability
4 of 4 checks
Response time
394 ms
Transport
streamable HTTP
Last checked
11 November 2026

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

Description as the publisher wrote it.

The 3 tools OCOLO Project Requests offers

ToolWhat it does
get_broker_guidanceWhy 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 sub
get_project_request_statusPoll 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 `curr
Inputs: request_id, status_token
submit_project_requestSubmit 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 fro
Inputs: location, power_kw, power_mw, power_per_cabinet_kw, cabinets, bandwidth_mbps

Add OCOLO Project Requests to your AI client

Every block below points at https://www.ocolo.io/api/v1/mcp/. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http ocolo-project-requests https://www.ocolo.io/api/v1/mcp/
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "ocolo-project-requests": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://www.ocolo.io/api/v1/mcp/"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "ocolo-project-requests": {
      "url": "https://www.ocolo.io/api/v1/mcp/"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "ocolo-project-requests": {
      "type": "http",
      "url": "https://www.ocolo.io/api/v1/mcp/"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "ocolo-project-requests": {
      "url": "https://www.ocolo.io/api/v1/mcp/"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "ocolo-project-requests": {
      "serverUrl": "https://www.ocolo.io/api/v1/mcp/"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "ocolo-project-requests": {
      "url": "https://www.ocolo.io/api/v1/mcp/"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: OCOLO Project Requests
version: 0.0.1
schema: v1
mcpServers:
  - name: OCOLO Project Requests
    type: streamable-http
    url: https://www.ocolo.io/api/v1/mcp/
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "ocolo-project-requests": {
      "httpUrl": "https://www.ocolo.io/api/v1/mcp/"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "ocolo-project-requests": {
      "type": "http",
      "url": "https://www.ocolo.io/api/v1/mcp/"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "ocolo-project-requests": {
      "url": "https://www.ocolo.io/api/v1/mcp/"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fwww.ocolo.io%2Fapi%2Fv1%2Fmcp%2F&type=streamable_http&id=ocolo-project-requests&name=OCOLO%20Project%20Requests

Is OCOLO Project Requests up right now?

It answered our last check on 11 November 2026 in 394 ms. Over 4 checks since 27 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to OCOLO Project Requests

Questions about OCOLO Project Requests

Is there an official OCOLO Project Requests MCP server?

Yes. It is published by ocolo.io and served from www.ocolo.io, the vendor's own domain: https://www.ocolo.io/api/v1/mcp/.

How many tools does OCOLO Project Requests have?

3, as returned by the server's own tools/list on 16 November 2026: get_broker_guidance, get_project_request_status, submit_project_request.

Is OCOLO Project Requests down?

It answered our last check on 11 November 2026 in 394 ms. Over 4 checks since 27 September 2026 it answered 4.

How do I add OCOLO Project Requests to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://www.ocolo.io/api/v1/mcp/. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does OCOLO Project Requests need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.ocolo.www. Endpoint host: www.ocolo.io. ARD identifier: urn:air:io.ocolo.www:mcp:project-requests. First indexed 26 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.