Exascale MCP MCP server

An MCP server providing verifiable, source-cited US data on power infrastructure, AI hardware supply chains, robotics adoption, and satellite licensing. It allows agents to query interconnection queues, construction spending, chip imports, and FCC filings with hash-verified citations.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Exascale

MCP endpoint (Streamable HTTP)

https://api.exascale.build/mcp

Vendor documentation

What you can do with it

Query US ISO interconnection queues and power capacity
Track AI infrastructure construction and chip imports
Analyze robotics adoption and industrial robot trade
Retrieve FCC satellite licensing docket and notices

Tools advertised by the last live check:

list_capabilities_v1
get_source_evidence_v1
describe_capability_v1
query_capability_v1
describe_power_capacity_v1
query_power_capacity_v1
describe_power_generation_v1
query_power_generation_v1
describe_power_asset_ownership_v1
query_power_asset_ownership_v1
describe_power_fuel_cost_v1
query_power_fuel_cost_v1
describe_power_plant_costs_v1
query_power_plant_costs_v1
describe_natural_gas_prices_v1
query_natural_gas_prices_v1
describe_power_demand_v1
query_power_demand_v1
describe_power_demand_rollup_v1
query_power_demand_rollup_v1
describe_power_retail_sales_v1
query_power_retail_sales_v1
describe_power_interconnection_queue_v1
query_power_interconnection_queue_v1
describe_power_interconnection_queue_pjm_v1
query_power_interconnection_queue_pjm_v1
describe_power_interconnection_queue_pjm_cycle_v1
query_power_interconnection_queue_pjm_cycle_v1
describe_power_interconnection_queue_caiso_v1
query_power_interconnection_queue_caiso_v1
describe_power_interconnection_queue_nyiso_v1
query_power_interconnection_queue_nyiso_v1
describe_power_interconnection_queue_isone_v1
query_power_interconnection_queue_isone_v1
describe_power_interconnection_queue_ercot_v1
query_power_interconnection_queue_ercot_v1
describe_power_interconnection_queue_spp_v1
query_power_interconnection_queue_spp_v1
describe_power_price_ercot_v1
query_power_price_ercot_v1
describe_power_capacity_accreditation_pjm_v1
query_power_capacity_accreditation_pjm_v1
describe_power_capacity_market_pjm_v1
query_power_capacity_market_pjm_v1
describe_power_capacity_accreditation_miso_v1
query_power_capacity_accreditation_miso_v1
describe_power_capacity_market_miso_v1
query_power_capacity_market_miso_v1
describe_ai_infrastructure_construction_v1
query_ai_infrastructure_construction_v1
describe_ai_infrastructure_trade_v1
query_ai_infrastructure_trade_v1
describe_ai_infrastructure_equipment_trade_v1
query_ai_infrastructure_equipment_trade_v1
describe_ai_infrastructure_production_v1
query_ai_infrastructure_production_v1
describe_robotics_trade_v1
query_robotics_trade_v1
describe_robotics_adoption_v1
query_robotics_adoption_v1
describe_space_satellite_filings_v1
query_space_satellite_filings_v1
describe_space_satellite_notices_v1
query_space_satellite_notices_v1
describe_capacity_factor_v1
query_capacity_factor_v1

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http exascale-mcp https://api.exascale.build/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add exascale-mcp --url https://api.exascale.build/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable exascale-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "exascale-mcp": {
      "url": "https://api.exascale.build/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "exascale-mcp": {
      "type": "streamableHttp",
      "url": "https://api.exascale.build/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start exascale-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "exascale-mcp": {
      "type": "http",
      "url": "https://api.exascale.build/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http exascale-mcp https://api.exascale.build/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "exascale-mcp": {
      "url": "https://api.exascale.build/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "exascale-mcp": {
      "serverUrl": "https://api.exascale.build/mcp"
    }
  }
}

See all 1,583

Do you run Exascale MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing