mappls-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAPPLS_API_KEY | Yes | Your Mappls API static key |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| geocodeA | Convert an Indian address or place name into latitude/longitude coordinates. Works with full addresses, landmarks, cities, and pincodes. |
| reverse_geocodeA | Convert latitude/longitude coordinates into a human-readable Indian address. |
| autosuggestA | Get autocomplete suggestions for an address or place as the user types. Returns a list of matching places with their eLoc codes. |
| text_searchC | Search for places in India by keyword, category, or brand name (e.g. 'Starbucks Delhi', 'petrol pump Mumbai'). |
| nearby_searchA | Find points of interest near a location in India — hospitals, ATMs, restaurants, petrol pumps, schools, etc. |
| place_detailsA | Get full details (name, address, category, contact, hours) for a place using its Mappls eLoc code. eLoc codes are returned by autosuggest, nearby_search, and text_search. |
| address_analyticsA | Analyze and standardize an Indian address — breaks it into structured components (house number, street, locality, district, state, pincode). |
| get_directionsA | Get turn-by-turn driving/biking/walking directions between two points in India, including distance, duration, and step-by-step instructions. |
| get_directions_with_trafficA | Get directions with real-time traffic-aware ETA. Returns predictive travel time based on current traffic conditions. |
| distance_matrixA | Calculate distances and travel times between multiple points. First coordinate is the origin; all others are destinations. Returns a matrix of distances and durations. |
| distance_matrix_with_trafficB | Calculate distances and traffic-aware ETAs between multiple points using real-time traffic data. |
| poi_along_routeA | Find points of interest along a route — useful for finding fuel stations, restaurants, or ATMs on the way from A to B. Requires the encoded polyline from get_directions. |
| snap_to_roadA | Snap a series of GPS coordinates to the nearest road. Useful for cleaning up raw GPS traces from a device. |
| elevationA | Get the elevation (altitude above sea level in metres) for one or more lat/lng points. |
| aerial_distanceA | Get the straight-line (crow-fly) distance between two geographic points. Faster than routing for simple distance checks. |
| still_map_imageA | Generate a static map image URL centered on a location. Returns a URL to a PNG map image — useful for embedding maps in reports or sending via WhatsApp/email. |
| validate_pincodeA | Validate an Indian 6-digit pincode and get the associated district, city, and state information. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Each tool has a distinct purpose: geocoding, search, directions, traffic, elevation, static maps, etc. No two tools overlap in functionality.
All tool names use snake_case and are mostly descriptive, but some are verb_noun (get_directions) while others are single words (geocode, elevation). 'still_map_image' is slightly awkward but still clear.
17 tools cover a comprehensive set of location-based services without being excessive. Each tool earns its place.
Covers core location needs: geocoding, search, routing, traffic, elevation, maps, pincode validation. Missing features like isochrones or place reviews are minor gaps.