quanta-route-geocoder
This MCP/REST server provides India-focused geocoding, DigiPin conversion/validation, administrative boundary lookup, batch operations, autocomplete, and usage/health checks.
Geocode addresses to DigiPin and coordinates (with optional city/state/country/pincode).
Reverse-geocode DigiPin to address and coordinates.
Convert latitude/longitude to DigiPin and validate DigiPin format/existence.
Batch-geocode up to 100 addresses.
Get address autocomplete suggestions (query ≥3 chars, configurable limit).
Look up administrative boundaries (pincode, state, division, locality) from coordinates or DigiPin.
Batch location lookup for up to 100 coordinate- or DigiPin-based locations.
Retrieve API usage/quota, location service statistics, and health status.
Note:
find_nearby_boundariesis exposed but not implemented.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@quanta-route-geocoder geocode 'Rohra Address, New Town, West Bengal'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@quantaroute/mcp-server
MCP server and REST wrapper for the QuantaRoute geocoding API (India). Geocode addresses, reverse-geocode DigiPin, and look up administrative boundaries.
First step: Get an API key at developers.quantaroute.com.
npm |
|
MCP Registry |
Related MCP server: Amap MCP Server
MCP (Claude Desktop, Cursor)
Add to Claude Desktop (claude_desktop_config.json) or Cursor (~/.cursor/mcp.json), then restart. Requires Node.js 18+ and npx.
Local process (MCP stdio):
{
"mcpServers": {
"quantaroute": {
"command": "npx",
"args": ["-y", "@quantaroute/mcp-server"],
"env": {
"QUANTAROUTE_API_KEY": "your-api-key"
}
}
}
}Tools
Tool | What it does |
| Address → DigiPin + coordinates. Optional |
| Address suggestions ( |
| DigiPin → address + coordinates |
| Lat/lng → DigiPin |
| Check DigiPin format / existence |
| Up to 100 addresses |
| Lat/lng → pincode, state, division, locality |
| DigiPin → the same |
| Up to 100 locations (each coords or DigiPin) |
| Quota, coverage stats, health |
find_nearby_boundaries is listed but not implemented. Use geocode or autocomplete with a point for category nearby.
REST
Same host: https://mcp-gc.quantaroute.com/api. Header x-api-key, or QUANTAROUTE_API_KEY on the server. Paths match the tools (POST /api/geocode, GET /api/autocomplete?q=…&lat=&lng=, …). Missing key → 401. Full list: docs/API.md.
Develop
npm install
npm run build
QUANTAROUTE_API_KEY=your-key npm startUpstream API: api.quantaroute.com · Issues: GitHub · License: MIT
Available Tools
13 toolsautocompleteA
Get autocomplete suggestions for addresses (minimum 3 characters).
Inputs: query (required), limit.
batch_geocodeA
Geocode multiple addresses in a single batch request (up to 100 addresses).
Inputs: addresses (required).
batch_location_lookupB
🚀 REVOLUTIONARY: Batch lookup for multiple locations. Each location can be specified by coordinates or DigiPin (up to 100 locations).
Inputs: locations (required).
coordinates_to_digipinA
Convert latitude and longitude coordinates to a DigiPin code.
Inputs: latitude (required), longitude (required).
find_nearby_boundariesA
Find nearby postal boundaries within a specified radius (NOT YET IMPLEMENTED - Coming Soon). The backend endpoint /v1/location/nearby needs to be implemented first.
Inputs: latitude (required), longitude (required), limit, radius_km.
geocodeC
Geocode an address to get DigiPin code and coordinates. Returns location information including latitude, longitude, and DigiPin.
Inputs: address (required), city, state, country, +1 more.
get_healthA
Check API health status and availability.
Inputs: no named parameters.
get_location_statisticsA
Get live statistics about the Location Lookup service (total boundaries, states, divisions, etc.).
Inputs: no named parameters.
get_usageA
Get API usage statistics and quota information.
Inputs: no named parameters.
lookup_location_from_coordinatesC
🚀 REVOLUTIONARY: Get administrative boundaries (pincode, state, division, locality) from coordinates. Provides precision that even government services don't offer.
Inputs: latitude (required), longitude (required).
lookup_location_from_digipinB
🚀 REVOLUTIONARY: Get administrative boundaries from a DigiPin code.
Inputs: digipin (required).
reverse_geocodeB
Reverse geocode a DigiPin code to get coordinates and address information.
Inputs: digipin (required).
validate_digipinC
Validate a DigiPin format and check if it corresponds to a real location.
Inputs: digipin (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 13 tools
Most tools have distinct purposes: geocode handles addresses, reverse_geocode handles DigiPins, and lookup_location_* handles administrative boundaries. Some pairs share inputs (e.g., coordinates_to_digipin vs lookup_location_from_coordinates) and could be confused, but descriptions clarify the different outputs.
The naming mixes verb-first patterns (geocode, validate_digipin, get_usage) with noun-first phrases (coordinates_to_digipin, batch_location_lookup) and varied verbs (get, lookup, find). While readable, the lack of a uniform convention makes the set feel inconsistent.
13 tools is reasonable for a geocoding service covering geocoding, reverse geocoding, batch operations, autocomplete, validation, and administrative boundaries. The count is slightly inflated by the unimplemented find_nearby_boundaries tool and multiple meta endpoints, but overall well-scoped.
The core geocoding/reverse geocoding lifecycle is covered, including batch and autocomplete operations, plus administrative boundary lookups. Minor gaps include the missing nearby-boundaries functionality and no batch reverse geocoding from DigiPins to addresses, but these are workable or explicitly marked.
Maintenance
Related MCP Connectors
Routing, geocoding, places, matrix and map tools for location-aware AI workflows.
Geocode and reverse geocode addresses, road distances and multi-stop routes. $0.001 per lookup.
Geocoding, routing, isochrones, traffic, weather, and place search for AI agents. 19 MCP tools.
Address validation & geocoding for AI agents: 240+ countries, UK PAF, free US/CA enrichment
Related MCP Servers
- AlicenseAqualityDmaintenanceEnhances LLM capabilities with location-based services and geospatial data, enabling users to geocode addresses, find nearby points of interest, get directions, optimize meeting points, and analyze neighborhoods.12237MIT
- FlicenseNot gradedqualityDmaintenanceProvides comprehensive geographic information services and route planning for AI agents via the Amap (Gaode Maps) API. It supports geocoding, multi-modal navigation, POI searches, and administrative region queries.3-

Magic Lane MCP Serverofficial
AlicenseBqualityCmaintenanceEnables AI agents to become geospatially intelligent assistants with tools for location search, smart routing, round trip planning, reverse geocoding, isochrone analysis, route visualization, geofence management, and interactive map display.812 npm8Apache 2.0- AlicenseAqualityDmaintenanceProvides location-based services and geospatial data from OpenStreetMap, enabling geocoding, route directions, nearby place search, and neighborhood analysis through natural language.12MIT