
Mcp Mapmyindia
io.github.bhuvnshPublished by GitHub account bhuvnshv0.1.0Updated Oct 24, 2026
MCP server for India maps - place search, nearby discovery, & directions powered by the Mappls API.
Overview
Local MCP server that exposes Mappls / MapMyIndia mapping APIs so an assistant can geocode, search places, find nearby spots and get directions in India.
- What you can do
- Convert addresses or place names to coordinates and coordinates back to readable addresses (geocode, reverse_geocode). Search and autocomplete places by query, and fetch details for a place by its Mappls eLoc ID. Discover nearby places by keyword around a reference location. Get turn-by-turn directions between two points, with waypoint support. Compute travel distance and time across multiple origins and destinations.
- When to use it
- Useful when an assistant needs India-focused location work: resolving Indian addresses to coordinates, finding places or businesses nearby, or planning routes and travel times between points.
- Requirements
- Runs locally via npx, so Node.js 18 or newer is needed. A Mappls account is required, configured either with an API key in MAPPLS_API_KEY or with OAuth credentials in MAPPLS_CLIENT_ID and MAPPLS_CLIENT_SECRET. Network access to the Mappls APIs is required.
Installation
In SourceWeft
- Open Mcp Mapmyindia in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
mcp-mapmyindia
MCP Server for Mappls / MapMyIndia APIs
[CI] [npm version] [License: MIT]
An MCP (Model Context Protocol) server that exposes Mappls / MapMyIndia APIs as tools for AI assistants like Claude. Enables geocoding, reverse geocoding, place search, nearby discovery, routing, and distance calculations — all focused on India's mapping data.
Tools
Setup
Get API credentials
Register at https://apis.mappls.com to get either:
- An API key (simpler, for personal/testing use)
- OAuth client credentials (recommended for production)
Authentication
Set one of the following in your environment:
Option A — OAuth (Client Credentials): RECOMMENDED
Option B — API Key:
Usage with Claude Desktop
Add to your claude_desktop_config.json:
Or with API key:
Config file location:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Development
Requirements
- Node.js >= 18
- A Mappls API key or OAuth client credentials
Contributing
Contributions are welcome. Please open an issue first to discuss what you'd like to change. Pull requests should include tests.
License
Source: README.md at commit 84ab874
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts