GPUQuant AI Infrastructure — Claude Code MCP server: what it does
Wires an agent into GPUQuant's records on data centres and companies: search sites, read facility facts, trace company links. Read-only.
claude mcp add --transport http infrastructure https://gpuquant.com/api/mcpWhat GPUQuant AI Infrastructure does
Three tools come with the server. search_infrastructure looks up records by name or location and pages through results; get_facility returns a site's public facts alongside its sources; get_company covers a company and the relationships documented for it. Pull the exact input schemas with tools/list.
The endpoint sits at https://gpuquant.com/api/mcp and speaks Streamable HTTP. Nothing to authenticate — this service is open to anyone. Add that URL in your client's remote-server settings; each client formats its config differently. Both the current MCP protocol and older clients using the 2025 initialization handshake are accepted.
What lives in the repository is connection docs, a registry manifest and an HTTP smoke test. The database itself stays on GPUQuant's side, so cloning gets you no local copy. Running the smoke test needs Node.js 20 or newer; it pulls in no third-party packages and asks for no credentials. This first release covers infrastructure records and company relationships — licensed Ornn and Silicon Data feeds, trading accounts, orders, imagery and building geometry are outside it. Dates attached to answers describe the record or its source, not a fresh check of the fact, and anything missing stays unknown.
What it helps with
- find infrastructure records for a city and pull their sources
- check who operates a facility, its status and when it was verified
- separate documented supply-chain links from merely reported ones
- flag stale or unknown facts before writing a company summary
- gather data-centre context for a research note
Example prompts for the agent
- Search GPUQuant for infrastructure records near Copenhagen and list the sources for each.
- Show this company's supply-chain relationships and mark which ones are only reported.
How to install GPUQuant AI Infrastructure
Platform CLI: remote server
claude mcp add --transport http infrastructure https://gpuquant.com/api/mcpPlatform CLI: remote server
codex mcp add gpuquant-ai-infrastructure --url https://gpuquant.com/api/mcpConfig file
{
"mcpServers": {
"gpuquant-ai-infrastructure": {
"url": "https://gpuquant.com/api/mcp"
}
}
}Config file
{
"servers": {
"gpuquant-ai-infrastructure": {
"type": "http",
"url": "https://gpuquant.com/api/mcp"
}
}
}Platform CLI: remote server
gemini mcp add -t http gpuquant-ai-infrastructure https://gpuquant.com/api/mcpStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about GPUQuant AI Infrastructure
How do I install GPUQuant AI Infrastructure in Claude Code?
Run claude mcp add --transport http gpuquant-ai-infrastructure https://gpuquant.com/api/mcp. No API key is involved.
What does GPUQuant AI Infrastructure do?
It gives an agent read access to GPUQuant's infrastructure and company records. You can search sites, read facility facts and trace company relationships, with links back to sources.
Can I self-host the GPUQuant database from this repository?
No. The repo holds connection instructions, a registry manifest and a smoke test; the database runs on GPUQuant's servers.
