Spatial India MCP MCP server

An official MCP server provided by Spatial India that connects AI agents to cleaned, crosswalked Indian district-level data from official sources like Census and NFHS. It enables agents to rank districts, resolve ambiguous place names, and compare socioeconomic indicators across regions without requiring authentication or API keys.

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 Spatial India

MCP endpoint (Streamable HTTP)

https://api.spatialindia.com/mcp

Vendor documentation

What you can do with it

Rank districts by specific socioeconomic indicators like child stunting
Resolve ambiguous place names by distinguishing districts with identical names
Compare demographic and economic data across different Indian districts

Tools advertised by the last live check:

find_indicator
get_district
compare_districts
rank_districts
get_methodology
build_map_link

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 spatial-india-mcp https://api.spatialindia.com/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 spatial-india-mcp --url https://api.spatialindia.com/mcp

Cursor

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

Cursor configuration

{
  "mcpServers": {
    "spatial-india-mcp": {
      "url": "https://api.spatialindia.com/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": {
    "spatial-india-mcp": {
      "type": "streamableHttp",
      "url": "https://api.spatialindia.com/mcp",
      "disabled": false
    }
  }
}

VS Code

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

VS Code configuration

{
  "servers": {
    "spatial-india-mcp": {
      "type": "http",
      "url": "https://api.spatialindia.com/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 spatial-india-mcp https://api.spatialindia.com/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": {
    "spatial-india-mcp": {
      "url": "https://api.spatialindia.com/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": {
    "spatial-india-mcp": {
      "serverUrl": "https://api.spatialindia.com/mcp"
    }
  }
}

See all 1,583

Do you run Spatial India 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