OCOLO Project Requests MCP Server

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.

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

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.