MapmyIndia Mappls MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mappls_geocodeA | Geocode an address or location text to retrieve latitude, longitude, eLoc code, and standardized address details in India. |
| mappls_reverse_geocodeA | Reverse geocode a pair of geographic coordinates (latitude and longitude) to get the corresponding formatted address and administrative details. |
| mappls_autosuggestA | Auto-suggest location search predictions for user input as text is typed. Returns ranked place recommendations. |
| mappls_get_directionsB | Get driving, walking, biking, or trucking navigation directions between origin and destination coordinates/eLocs in India. |
| mappls_distance_matrixA | Calculate travel distances and durations matrix between multiple origin and destination points in India. |
| mappls_snap_to_roadA | Snap raw GPS coordinates trace to the nearest road network segments to smooth GPS noise. |
| mappls_search_nearbyA | Search points of interest (POIs) such as restaurants, fuel stations, ATMs, EV chargers, hospitals, hotels near given coordinates. |
| mappls_place_detailsB | Retrieve rich location attributes and details for a location using its 6-character Mappls eLoc code. |
| mappls_text_searchB | Perform smart text search across place entities with auto-correction for spelling variations. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| plan_itinerary | Prompt template to guide the LLM in constructing a detailed travel itinerary in India. |
| optimize_logistics_hub | Prompt template to select the optimal distribution hub from a list of candidates. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool maps to a distinct location API operation: geocoding, reverse geocoding, typeahead suggestions, routing, distance matrix, road snapping, nearby POI search, place details, and text search. The only real overlap is between autosuggest and text_search, but their descriptions clarify the intended use cases.
All tools share a consistent mappls_ prefix and snake_case format. Most names follow a verb-plus-object style like get_directions or search_nearby, though a few are bare nouns such as distance_matrix and place_details, so the pattern is clean but not perfectly uniform.
Nine tools is well-scoped for a location/mapping server. Each tool covers a distinct workflow with no obvious redundancy, and the count is within the ideal range for an MCP toolset.
The server covers the core read-only location lifecycle well: geocode and reverse geocode, place search and details, directions, distance matrix, and map matching. Advanced features like static map rendering or route optimization are absent, but common mapping workflows have no critical gaps.