Koskamo

Datacommons MCP

The Datacommons MCP server provides access to harmonized public statistics from Google Data Commons. It allows AI agents to find place IDs, search statistical variables, retrieve observation values for specific places and dates, and compare data across child places, enabling comprehensive geographic and demographic data analysis.

Endpoint and access

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

Datacommons MCP logo, by PipeworxNo sign-inEndpoint checked 2026-10-19Operated by Pipeworx
MCP endpoint (Streamable HTTP)
https://gateway.pipeworx.io/datacommons/mcp
Vendor documentation

What you can do with it

  • Find Google Data Commons place IDs for geographic names
  • Search for statistical variables by plain-language indicators
  • Retrieve latest or historical statistical values for a place
  • Compare statistical variables across child places of a parent region
Tools advertised by the last live check:
  • ask_pipeworx
  • ask_pipeworx_beta
  • ask_pipeworx_grounded
  • search_within
  • deep_research
  • discover_tools
  • resolve_entity
  • compare_entities
  • subscribe
  • unsubscribe
  • list_subscriptions
  • recent_alerts
  • entity_profile
  • recent_changes
  • validate_claim
  • company_facts
  • company_register_search
  • scan_dependency
  • bet_research
  • polymarket_arbitrage
  • polymarket_edges
  • polymarket_kalshi_spread
  • polymarket_fill_risk
  • polymarket_edge_tracker
  • kalshi_weather_edge
  • resolution_audit
  • resolution_diff
  • release_calendar_markets
  • archive_evidence
  • archive_compare
  • research_row
  • classify_row
  • pipeworx_trending
  • suggest_questions
  • generate_llms_txt
  • ai_visibility_check
  • scan_competitor_ai_presence
  • pipeworx_feedback
  • remember
  • recall
  • forget
  • datacommons_find_place
  • datacommons_find_variable
  • datacommons_observation
  • datacommons_child_places

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 datacommons-mcp https://gateway.pipeworx.io/datacommons/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 datacommons-mcp --url https://gateway.pipeworx.io/datacommons/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable datacommons-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "datacommons-mcp": {
      "url": "https://gateway.pipeworx.io/datacommons/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": {
    "datacommons-mcp": {
      "type": "streamableHttp",
      "url": "https://gateway.pipeworx.io/datacommons/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start datacommons-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "datacommons-mcp": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/datacommons/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 datacommons-mcp https://gateway.pipeworx.io/datacommons/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": {
    "datacommons-mcp": {
      "url": "https://gateway.pipeworx.io/datacommons/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": {
    "datacommons-mcp": {
      "serverUrl": "https://gateway.pipeworx.io/datacommons/mcp"
    }
  }
}

Do you run Datacommons 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