Supports configuration of API credentials and service parameters through environment variables loaded from a .env file.
Enables installation of the MCP server from source code via GitHub repository cloning.
Provides access to GrabMaps services through AWS Location Service, including Places API (geocoding, place details), Maps API (tiles, styles, glyphs, sprites), and Routes API (route calculation and matrix routing).
Enables visualization of GrabMaps data through MapLibre GL, with support for rendering map tiles, styles, sprites, and glyphs from the GrabMaps service.
Provides installation through NPM package registry and usage of NPM scripts for development, building, and deployment workflows.
GrabMaps MCP Server
A Model Context Protocol (MCP) server for GrabMaps API integration, providing access to GrabMaps services through AWS Location Service.
Do note that this MCP server is NOT officially affiliated with Grab, GrabMaps, or AWS Location Service.
Important: GrabMaps only supports eight countries in Southeast Asia.
- 🇲🇾 Malaysia (MYS)
- 🇸🇬 Singapore (SGP)
- 🇹🇭 Thailand (THA)
- 🇲🇲 Myanmar (MMR)
- 🇰🇭 Cambodia (KHM)
- 🇻🇳 Vietnam (VNM)
- 🇵🇭 Philippines (PHL)
- 🇮🇩 Indonesia (IDN)
Search requests outside these countries will not return accurate results.
Features
This MCP server provides access to GrabMaps functionality through two main categories:
Places Actions (Available via MCP)
- SearchPlaceIndexForText: Forward geocoding to find places by name or address
- SearchPlaceIndexForPosition: Reverse geocoding to find places by coordinates
- SearchPlaceIndexForSuggestions: Get place suggestions as you type
- GetPlace: Retrieve detailed information about a specific place
Routes Actions (Available via MCP)
- CalculateRoute: Calculate routes between points with waypoints
- CalculateRouteMatrix: Calculate a matrix of routes between multiple origins and destinations
Maps Functionality (Requires AWS Console)
Note: Map rendering functionality is not directly available through the MCP server. To view and use maps:
- Go to the AWS Location Service console
- Look for the Maps section and click the "Try it" button
- Ensure "Grab" is selected as the provider
To explore GrabMaps data coverage and see the maps in action without logging in to AWS, visit: https://grabmaps.grab.com/explore-data-coverage
Installation
From NPM
From Source
Configuration
Create a .env
file in the root directory with the following variables:
Usage
Running Locally
Using with Smithery
Testing in Smithery Playground
For the best experience testing Places and Routes APIs, we recommend using the Smithery playground:
- Start your MCP server locally:
npm run dev
- Open the Smithery playground at: https://smithery.ai/playground
- Connect to your local MCP server:
http://localhost:3000
- Test Places and Routes API calls using the provided examples in SMITHERY_TESTING.md
Important Notes for AI Models
Supported Countries
GrabMaps ONLY supports the following eight countries in Southeast Asia:
- Malaysia (MYS)
- Singapore (SGP)
- Thailand (THA)
- Myanmar (MMR)
- Cambodia (KHM)
- Vietnam (VNM)
- Philippines (PHL)
- Indonesia (IDN)
AI models should not attempt to use GrabMaps for locations outside these countries as results will be inaccurate or non-existent.
Country Code Requirements
When using the Places API functions, AI models MUST analyze the user's query to determine the appropriate country and include the three-letter ISO country code in all requests:
Examples of country codes:
- Singapore: SGP
- Malaysia: MYS
- Thailand: THA
- Indonesia: IDN
- Philippines: PHL
- Vietnam: VNM
Including the country code is critical for returning accurate search results.
This approach allows you to test the Places and Routes functionality without needing to set up map visualization components.
Example API Calls
Forward Geocoding
Calculate Route
Integrating with AI Models
This MCP server can be integrated with AI models that support the Model Context Protocol. Example integration with an AI model:
AWS Location Service Setup
Before using this MCP server, you need to set up the following resources in AWS Location Service:
- Create a Place Index with GrabMaps as the data provider
- Create a Map with GrabMaps as the data provider
- Create a Route Calculator with GrabMaps as the data provider
Map Component Limitations and Recommended Approach
The Maps API components have certain limitations when used through the MCP server:
- Map tiles returned by the
getMapTile
endpoint are binary data encoded as base64 strings - Font stacks for
getMapGlyphs
must match those supported by GrabMaps via AWS Location Service - Sprite filenames for
getMapSprites
must follow specific regex patterns - Maximum zoom levels are restricted (typically max zoom 14)
Recommended Approach:
- For Maps: Use direct integration with GrabMaps via MapLibre GL and AWS Location Service as shown in the official demo
- For Places and Routes: Use the MCP server through the Smithery playground or direct API calls
This separation allows for optimal performance and visualization while still leveraging the MCP server for Places and Routes functionality.
Official GrabMaps MapLibre GL Demo
A comprehensive demo using the official GrabMaps integration with MapLibre GL is included in the examples/official-map-demo
directory. This demo provides a complete testing interface for all GrabMaps components:
- Places API: Forward/reverse geocoding and place details
- Maps API: Map tiles, style descriptors, sprites, and glyphs
- Routes API: Route calculation and route matrix
The demo features a tabbed interface for easy testing of different components and provides detailed feedback for each API call.
Key Features
- Interactive map using official GrabMaps map tiles via MapLibre GL
- Tabbed interface for testing different GrabMaps components
- Comprehensive testing of all API endpoints
- Configurable API key, region, and resource names
- Visual display of routes, search results, and map components
To run the demo:
See the Official Map Demo README for setup and usage instructions.
Testing
A comprehensive test suite is included in the tests
directory to verify all endpoints are working correctly. For detailed testing instructions, examples, and troubleshooting tips, please refer to the TESTING.md file.
To run the tests:
License
This project is licensed under the MIT License - see the LICENSE file for details.
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
This server cannot be installed
hybrid server
The server is able to function both locally and remotely, depending on the configuration or use case.
Provides access to GrabMaps services (Places, Maps, Routes) through AWS Location Service using the Model Context Protocol.
Related MCP Servers
- AsecurityAlicenseAqualityA Model Context Protocol server that provides Google Maps API integration, allowing users to search locations, get place details, geocode addresses, calculate distances, obtain directions, and retrieve elevation data through LLM processing capabilities.Last updated -781760TypeScriptMIT License
- AsecurityAlicenseAqualityProvides access to Google Maps API functionality including geocoding, place search, direction routing, and distance calculations through a structured MCP interface.Last updated -45JavaScriptMIT License
- AsecurityAlicenseAqualityNon-official Model Context Protocol server that enables interaction with AMap's location services through clients like Cursor, Claude Desktop, Cline, and Windsurf.Last updated -11PythonMIT License
- AsecurityFlicenseAqualityEnables users to access Naver Maps API functionality including directions, place search, geocoding, and reverse geocoding through a Model Context Protocol server.Last updated -4JavaScript