io.github.sathya-sankaran/bharatlas-mcp

Optional: create a collect map programmatically. Most maps are made online at collect.bharatlas.com (no key needed) — prefer that and register_map the link. This path needs COLLECT_API_KEY (the request-only anti-abuse gate) and auto-registers the new admin link.

Edit a collect map's settings: name/description/purpose/category/data_year/basemap (needs the admin link). Licence can only change while the map has no records.

Get full metadata for a single layer: download URLs (parquet, pmtiles, geojson, kml, shapefile), attribution, license, feature count, and level metadata.

Get column names, types, and sample values for a layer. Use BEFORE querying to discover what columns exist and what values they contain. Essential for knowing the right column names for filters.

A collect map's metadata + record counts, plus a link to open it in collect. Any registered scope.

A collect map's records as a GeoJSON FeatureCollection — for reading, analysis, or backup/export. view and collect scope return published points; admin can also read pending/rejected via status.

Bulk-import points you already hold into a collect map (needs the admin link). NOT for synthetic data. Requires a named source + rights confirmation; each row lands with that source as its provenance.

List all data categories with layer counts.

List available geo layers. Use to discover what data bharatlas has. Returns layer IDs, names, row counts, categories, and download formats. Filter by category (boundaries, city-wards, environment, water, agriculture, transport, etc.), admin level (state, district, block, village, etc.), source, or text search.

List the collect maps you have registered here (local store), each with its scope.

List community-submitted geo layers. These are user-contributed datasets under open licenses. Filter by category or search by name.

Given a latitude/longitude, find which administrative boundaries, zones, and regions contain that point. Returns state, district, subdistrict, block, parliament/assembly constituency, pincode, seismic zone, high court jurisdiction, the municipal ward (for the ~30 cities with ward data), and more. The 'where am I?' tool. Also accepts specific layer IDs to check.

Approve or reject one pending point (needs the admin link). Pass the map id it belongs to.

Find features from a layer that are near a given point, nearest first, within radius_km. Reads the layer's parquet bounding boxes and ranks features by distance to their centres; works for points, polygons and lines. Returns the true count within the radius plus the nearest `limit`. Example: 'reservoirs near Bengaluru' -> layer_id: 'wris_reservoirs', lat: 12.97, lng: 77.59, radius_km: 50.

Submit a collect map's approved points to the bharatlas catalog for review (needs the admin link). Nothing goes live automatically — a maintainer approves the submission first; the response status is 'pending' until then. Once approved it is queryable via list_submissions / query_layer / locate above.

Query a layer's data with filters and grouping. Reads the parquet file at runtime. Supports: select specific columns, filter by column values, group by a column to get counts, and sum numeric columns per group (e.g. roll block areas up to district totals). Use get_layer_schema first to discover column names. Examples: 'airports in Karnataka' -> where: {state: 'KA'}, 'forest types' -> group_by: 'type', 'health facilities in Bihar' -> where: {state: 'BIHAR'}, select: ['name', 'type'].

Register a collect map so this server can act on it. Paste the whole share link (e.g. https://collect.bharatlas.com/c/<id>/admin#<token>). The token in the #fragment sets your scope: admin = full control, collect = add points, view = read published. New maps are created online at collect.bharatlas.com first (no account or key needed); this registers one you already made.