bharatlas-mcp
Related Servers
Alternatives to bharatlas-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables natural-language access to India's Open Government Data platform, letting users discover datasets, inspect schemas, and query live data from data.gov.in.4MIT
- AlicenseAqualityBmaintenanceEnables LLMs to search and query India's Open Government Data platform, including catalog search, dataset schemas, filtered rows, and tidy time series for GDP, trade, agriculture, and other published datasets.4MIT
- AlicenseNot gradedqualityDmaintenanceEnables natural language and geospatial queries on PostGIS databases, with 32 tools for spatial analysis, geometry operations, and database management.5MIT
- FlicenseBqualityDmaintenanceProvides read-only query tools over OpenStreetMap data in PostGIS, enabling natural language queries for features, categories, and spatial analysis.7-
- FlicenseNot gradedqualityBmaintenanceEnables conversational spatial SQL queries in plain English, turning natural language questions into validated PostGIS operations and rendering results as GeoJSON on an interactive map.-
- AlicenseNot gradedqualityBmaintenanceMCP server to access India Open Government Data (data.gov.in) resources via natural language queries.92 npm1MIT
TDQS
Scored across 17 tools
The set cleanly splits into catalog/query tools (list_layers, query_layer, locate, nearby) and collect-map management tools (register_map, get_map, moderate_record, publish), and most boundaries are clear from the descriptions. Minor overlap remains between list_layers and get_layer_detail (both report row counts and formats) and between list_layers and list_submissions, which an agent could pick incorrectly when looking for a specific layer.
Nearly all tools follow a snake_case verb_noun pattern: list_layers, get_layer_schema, query_layer, register_map, edit_map, import_points, moderate_record. A few deviate with bare verbs or adjectives (locate, nearby, publish), which are readable and contextual but break the otherwise predictable pattern.
17 tools is slightly above the ideal range, but the server legitimately spans two surfaces (data catalog querying plus user map administration), and each tool maps to a distinct operation with no filler. The only near-duplicates are list_layers vs get_layer_detail vs list_categories, which could plausibly be folded together.
The map lifecycle is well covered end to end: create/register, list, inspect, read records, moderate, import, edit, publish. The catalog side covers discovery, schema, filtered queries, point-in-polygon lookup and proximity search, but lacks any bounding-box or polygon-area query for layers, and there is no delete operation for registered maps or individual records — gaps an agent would hit in real workflows.