by mapbox
Mapbox: Geospatial intelligence — fast geocoding API, POI search API, routing API and isochrones for location-aware apps
Connects AI applications to Mapbox's location services for geocoding, routing, POI search, and spatial analysis. Requires a Mapbox access token.
Mapbox is an official MCP server published by mapbox that provides AI assistants with tools and capabilities via the Model Context Protocol. Mapbox: Geospatial intelligence — fast geocoding API, POI search API, routing API and isochrones for location-aware apps It is categorized under developer tools.
You can install Mapbox in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server supports remote connections over HTTP, so no local installation is required.
MIT
Mapbox is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
We wired Mapbox into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Mapbox has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
I recommend Mapbox for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Mapbox reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Strong directory entry: Mapbox surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Mapbox is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Mapbox is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Useful MCP listing: Mapbox is the kind of server we cite when onboarding engineers to host + tool permissions.
Mapbox has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
According to our notes, Mapbox benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
showing 1-10 of 73
Node.js server implementing Model Context Protocol (MCP) for Mapbox APIs.
The Mapbox MCP Server transforms any AI agent or application into a geospatially-aware system by providing seamless access to Mapbox's comprehensive location intelligence platform. With this server, your AI can understand and reason about places, navigate the physical world, and access rich geospatial data including:
Whether you're building an AI travel assistant, logistics optimizer, location-based recommender, or any application that needs to understand "where", the Mapbox MCP Server provides the spatial intelligence to make it possible. You can also enable it on popular clients like Claude Desktop and VS Code. See below for details

A Mapbox access token is required to use this MCP server.
For quick access, you can use our hosted MCP endpoint:
Endpoint: https://mcp.mapbox.com/mcp
For detailed setup instructions for different clients and API usage, see the Hosted MCP Server Guide.
To get a Mapbox access token:
For more information about Mapbox access tokens, see the Mapbox documentation on access tokens.
For detailed setup instructions for different integrations, refer to the following guides:
Try these prompts with Claude Desktop or other MCP clients after setup:
Detailed examples: See examples/search-along-route.md for comprehensive examples of the search-along-route prompt with different use cases and MCP Inspector testing instructions.
The MCP server exposes static reference data as MCP resources. Resources provide read-only access to data that clients can reference directly without making tool calls.
URI Pattern: mapbox://categories or mapbox://categories/{language}
Access the complete list of available category IDs for use with the category search tool. Categories can be used to filter search results by type (e.g., "restaurant", "hotel", "gas_station").
Examples:
mapbox://categories - Default (English) category listmapbox://categories/ja - Japanese category namesmapbox://categories/es - Spanish category namesAccessing Resources:
resources/read MCP protocol methodresource_reader_tool with the resource URIThe static_map_image_tool provides an interactive map preview panel in compatible clients, in addition to the base64 image that all clients receive.
This server implements the MCP Apps protocol (@modelcontextprotocol/ext-apps), which renders a self-contained HTML app panel directly inside the chat. Supported clients show an interactive map with a Fullscreen toggle:
All clients receive the base64-encoded map image regardless of protocol support — interactive previews are a progressive enhancement on top of the standard image response.
This server also retains support for MCP-UI (@mcp-ui/server), an earlier open specification for embedded iframe previews. MCP Apps is the recommended protocol; MCP-UI support is kept for backwards compatibility.
MCP-UI is enabled by default. To disable it, pass --disable-mcp-ui as a command-line flag or set ENABLE_MCP_UI=false. See the MCP-UI documentation for details.
Resource Fallback Tools (Opt-In for Non-Compliant Clients)
Resources are a core MCP feature supported by most clients (Claude Desktop, VS Code, MCP Inspector, etc.). However, some clients (like smolagents) don't support resources at all. For these clients, the server can provide "resource fallback tools" that deliver the same content as resources but via tool calls.
Fallback Tools:
resource_reader_tool - Generic fallback for reading any resource by URIcategory_list_tool - Provides access to category list (mapbox://categories)By default, these tools are NOT included (assumes your client supports resources). If your client doesn't support resources, enable the fallback tools:
export CLIENT_NEEDS_RESOURCE_FALLBACK=true
When to set this:
true if using smolagents or other clients without resource supportProvides access to MCP resources for clients that don't support the native MCP resource API. Use this tool to read resources like the category list.
Parameters:
uri: The resource URI to read (e.g., mapbox://categories, mapbox://categories/ja)Example Usage:
{"uri": "mapbox://categories"}{"uri": "mapbox://categories/ja"}Note: If your MCP client supports native resources, prefer using the resource API directly for better performance.
These tools perform geospatial calculations completely offline without requiring Mapbox API calls. Th
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.