Mapbox MCP can send addresses, coordinates, routes, POI searches, GPS traces, travel-time matrices, and map-rendering requests to Mapbox APIs., API-backed tools can consume Mapbox quota or create billing activity; restrict autonomous routing, matrix, map matching, and static map loops., Location workflows can affect navigation, logistics, delivery planning, and accessibility decisions; verify critical routes and travel-time results outside the model., Static map and MCP Apps preview tools can create visual outputs that include user-supplied coordinates, markers, routes, and geographic data., Use `--enable-tools` or `--disable-tools` to limit high-impact tools such as static map generation, matrix calculations, route optimization, and map matching when needed.
Privacy notes
Mapbox receives access tokens, geocoding queries, addresses, place names, coordinates, routes, GPS traces, POI searches, request parameters, and usage metadata., MCP clients and logs can retain location questions, returned coordinates, route summaries, travel-time matrices, static map image data, and embedded map-preview context., Hosted MCP connections may use OAuth or bearer-token authentication; avoid exposing tokens in client configs, browser history, server logs, proxies, or screenshots., Location data can reveal home, workplace, customer, route, delivery, mobility, or sensitive site information.
Author
Mapbox
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
5 safety and 4 privacy notes across 4 risk areas. Review closely: credentials & tokens, network access.
4 areas
SafetyNetwork accessMapbox MCP can send addresses, coordinates, routes, POI searches, GPS traces, travel-time matrices, and map-rendering requests to Mapbox APIs.
SafetyGeneralAPI-backed tools can consume Mapbox quota or create billing activity; restrict autonomous routing, matrix, map matching, and static map loops.
SafetyData retentionLocation workflows can affect navigation, logistics, delivery planning, and accessibility decisions; verify critical routes and travel-time results outside the model.
SafetyGeneralStatic map and MCP Apps preview tools can create visual outputs that include user-supplied coordinates, markers, routes, and geographic data.
SafetyGeneralUse `--enable-tools` or `--disable-tools` to limit high-impact tools such as static map generation, matrix calculations, route optimization, and map matching when needed.
PrivacyCredentials & tokensMapbox receives access tokens, geocoding queries, addresses, place names, coordinates, routes, GPS traces, POI searches, request parameters, and usage metadata.
PrivacyData retentionMCP clients and logs can retain location questions, returned coordinates, route summaries, travel-time matrices, static map image data, and embedded map-preview context.
PrivacyCredentials & tokensHosted MCP connections may use OAuth or bearer-token authentication; avoid exposing tokens in client configs, browser history, server logs, proxies, or screenshots.
PrivacyGeneralLocation data can reveal home, workplace, customer, route, delivery, mobility, or sensitive site information.
Disclosure: MIT-licensed official Mapbox MCP server published as the `@mapbox/mcp-server` npm package, with a hosted streamable HTTP endpoint and a local stdio package path. This entry is separate from generic mapping or geospatial libraries because it exposes Mapbox APIs, MCP resources, prompts, and MCP Apps previews directly to MCP clients.
Safety notes
Mapbox MCP can send addresses, coordinates, routes, POI searches, GPS traces, travel-time matrices, and map-rendering requests to Mapbox APIs.
API-backed tools can consume Mapbox quota or create billing activity; restrict autonomous routing, matrix, map matching, and static map loops.
Location workflows can affect navigation, logistics, delivery planning, and accessibility decisions; verify critical routes and travel-time results outside the model.
Static map and MCP Apps preview tools can create visual outputs that include user-supplied coordinates, markers, routes, and geographic data.
Use `--enable-tools` or `--disable-tools` to limit high-impact tools such as static map generation, matrix calculations, route optimization, and map matching when needed.
Privacy notes
Mapbox receives access tokens, geocoding queries, addresses, place names, coordinates, routes, GPS traces, POI searches, request parameters, and usage metadata.
MCP clients and logs can retain location questions, returned coordinates, route summaries, travel-time matrices, static map image data, and embedded map-preview context.
Hosted MCP connections may use OAuth or bearer-token authentication; avoid exposing tokens in client configs, browser history, server logs, proxies, or screenshots.
Location data can reveal home, workplace, customer, route, delivery, mobility, or sensitive site information.
Prerequisites
Node.js and npm or another runtime capable of running `npx -y @mapbox/mcp-server`.
A Mapbox access token with the scopes needed for the APIs and endpoints you plan to expose.
Review of Mapbox pricing, rate limits, token scopes, geocoding rules, routing behavior, and static map usage.
Optional hosted MCP setup review if connecting to `https://mcp.mapbox.com/mcp` through OAuth or bearer-token authentication.
Optional tool allowlist or denylist planning with `--enable-tools` or `--disable-tools`.
Schema details
Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
10 minutes
Difficulty
intermediate
Tool listing metadata
Disclosure
MIT-licensed official Mapbox MCP server published as the `@mapbox/mcp-server` npm package, with a hosted streamable HTTP endpoint and a local stdio package path. This entry is separate from generic mapping or geospatial libraries because it exposes Mapbox APIs, MCP resources, prompts, and MCP Apps previews directly to MCP clients.
Mapbox MCP Server connects Claude and other MCP clients to Mapbox location
intelligence. It can geocode addresses, reverse geocode coordinates, search for
points of interest, get directions, calculate travel-time matrices, match GPS
traces to roads, generate isochrones, render static maps, and run offline
geospatial calculations with Turf.js.
Use it when a Claude workflow needs location-aware reasoning, travel planning,
logistics analysis, route optimization, or map visualization backed by Mapbox.
It supports a local npx stdio install path and a hosted streamable HTTP
endpoint for clients that can connect to remote MCP servers.
These sources were reviewed on 2026-06-06. Prefer the live repository,
README, npm metadata, license, package metadata, server manifest, tool
configuration guide, hosted MCP guide, and server entry point for current setup
and operating details.
Features
Convert addresses and place names to coordinates with forward geocoding.
Convert coordinates back into human-readable places with reverse geocoding.
Search for places, points of interest, brands, chains, categories, and nearby
locations.
Get driving, walking, or cycling directions with Mapbox routing data.
Calculate travel-time matrices between multiple origins and destinations.
Optimize multi-stop routes for delivery, travel, and field-service planning.
Snap noisy GPS traces to road networks with map matching.
Generate isochrones for reachable-area analysis.
Render static map images with routes, markers, and geographic data.
Run offline calculations for distance, area, bearing, centroid, midpoint,
bounding boxes, buffers, intersections, and point-in-polygon checks.
Expose category-list MCP resources and optional fallback resource tools.
Provide MCP Apps and MCP-UI map previews in compatible clients.
Limit the tool surface at startup with --enable-tools or --disable-tools.
Installation
Set a Mapbox access token and run the npm package:
claude mcp add --transport http mapbox-mcp-production https://mcp.mapbox.com/mcp
Use Cases
Ask Claude for directions between named locations or coordinates.
Search for restaurants, hotels, stores, gas stations, landmarks, or other POI
categories near a route or place.
Build logistics and delivery workflows that compare travel times across
multiple stops.
Visualize a route, service area, neighborhood, or set of points with a static
map image.
Clean up GPS traces before reviewing rides, drives, or field-service routes.
Calculate geospatial relationships such as distance, area, bearing, centroid,
midpoint, or point-in-polygon checks.
Use the hosted Mapbox MCP endpoint for clients that support remote MCP
servers and authentication flows.
Safety and Privacy
Mapbox MCP handles location data. Addresses, coordinates, routes, place names,
GPS traces, and map images can reveal homes, workplaces, customer sites,
delivery routes, protected facilities, or sensitive travel patterns. Limit the
tools available to the model, avoid sending location data that is not approved
for Mapbox processing, and keep access tokens out of logs and screenshots.
Routing, traffic, matrix, and optimization results are planning aids rather
than guarantees. Verify critical navigation, safety, emergency, legal,
accessibility, and logistics decisions with authoritative systems and current
local conditions.
Duplicate Notes
Existing catalog entries cover general map search, web search, and geospatial
data tools. This entry covers the official mapbox/mcp-server repository and
@mapbox/mcp-server package, including Mapbox API-backed tools, MCP resources,
prompts, hosted MCP setup, and MCP Apps map previews.
Show that Mapbox MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/mapbox-mcp-server)
How it compares
Mapbox MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
Official Agentset MCP server that lets Claude retrieve cited knowledge-base results from an Agentset namespace through the `knowledge-base-retrieve` tool, with optional tenant scoping and custom tool descriptions.
MCP server for Anki flashcards that lets Claude review cards, manage decks, create and update notes, handle tags and media, inspect stats, and drive Anki desktop GUI workflows.
✓Mapbox MCP can send addresses, coordinates, routes, POI searches, GPS traces, travel-time matrices, and map-rendering requests to Mapbox APIs.
API-backed tools can consume Mapbox quota or create billing activity; restrict autonomous routing, matrix, map matching, and static map loops.
Location workflows can affect navigation, logistics, delivery planning, and accessibility decisions; verify critical routes and travel-time results outside the model.
Static map and MCP Apps preview tools can create visual outputs that include user-supplied coordinates, markers, routes, and geographic data.
Use `--enable-tools` or `--disable-tools` to limit high-impact tools such as static map generation, matrix calculations, route optimization, and map matching when needed.
✓The MCP server sends Claude's retrieval queries to the Agentset API using the configured API key and namespace.
The `knowledge-base-retrieve` tool can return up to 100 results per call and can rerank results by relevance.
Namespace and tenant selection control which indexed documents are searchable; review them before connecting a shared agent.
API keys should be scoped, rotated, and stored only in the MCP server environment or a secret manager.
Custom tool descriptions can influence when the model calls the retrieval tool, so review them before use in production workflows.
✓AI Game Developer can create, move, copy, modify, and delete Unity assets, scenes, GameObjects, components, scripts, packages, and generated project files.
Tools include dynamic C# script execution, C# reflection method lookup and calls, package installation/removal, Unity test execution, editor state changes, play mode control, screenshots, and profiler access.
The MCP server supports streamable HTTP and stdio; HTTP deployments should require a bearer token and stay bound to trusted interfaces.
Server variables include optional authorization and webhook settings; webhook endpoints can receive tool, prompt, resource, connection, and authorization events.
Unity runtime connections can expose compiled game state or in-game behavior to an MCP client, not just editor-only project data.
Use source control, backups, tool filtering, and explicit review before allowing destructive tools such as asset deletion, package removal, script execution, or reflection calls.
✓Anki MCP Server can create, update, delete, move, tag, rate, and sync cards and notes through AnkiConnect.
Destructive tools include note deletion, media deletion, unused-tag clearing, deck moves, tag replacement, model styling changes, and review rating actions that affect scheduling.
The server supports read-only mode that blocks exposed write actions, but users should still review tool calls before enabling unrestricted study or collection-management workflows.
Media tools can store files from local paths, URLs, or base64 data and can retrieve media as base64 content.
GUI tools can open Anki windows, select cards, edit notes, show answers, and undo the last Anki action.
Remote tunnel or ngrok-style setups expose local Anki to cloud-hosted AI clients and require careful authentication, origin, and URL-sharing controls.
Privacy notes
✓Mapbox receives access tokens, geocoding queries, addresses, place names, coordinates, routes, GPS traces, POI searches, request parameters, and usage metadata.
MCP clients and logs can retain location questions, returned coordinates, route summaries, travel-time matrices, static map image data, and embedded map-preview context.
Hosted MCP connections may use OAuth or bearer-token authentication; avoid exposing tokens in client configs, browser history, server logs, proxies, or screenshots.
Location data can reveal home, workplace, customer, route, delivery, mobility, or sensitive site information.
✓Retrieved chunks can include private documents, product specs, policies, support content, internal procedures, historical project information, or customer-specific data.
Retrieval queries, namespace IDs, tenant IDs, document chunks, citations, and tool outputs may be visible to the MCP client, model provider, Agentset logs, and application telemetry.
Tenant IDs are useful for data segregation, but incorrect tenant or namespace configuration can expose the wrong knowledge base.
Do not paste API keys, namespace IDs, tenant IDs, or retrieved private chunks into shared issue reports, screenshots, or repository files.
✓Tool calls may expose Unity project paths, asset names, scene hierarchy, serialized object data, scripts, logs, screenshots, profiler metrics, test output, package metadata, and runtime state.
MCP config files and Unity plugin config can contain server URLs, connection modes, bearer tokens, authorization settings, enabled tool IDs, and cloud or local endpoint details.
Optional webhooks can receive tool, prompt, resource, connection, authorization, and token-bearing request data.
Screenshots from Game View, Scene View, cameras, or isolated GameObjects may include proprietary artwork, level design, UI, debug overlays, or unreleased game content.
Generated skills and AI-client configuration files can reveal available tools, project structure, installed packages, and local workflow assumptions.
✓Tool calls can expose deck names, note fields, card contents, tags, review history, media filenames, base64 media, selected notes, collection stats, scheduling metadata, and AnkiConnect errors.
Flashcards may contain medical, language-learning, school, work, personal, customer, or confidential study material.
Sync can send Anki collection changes to AnkiWeb according to the user's Anki account and sync settings.
Local media file paths, URLs imported into cards, and GUI-selected note IDs can enter MCP client context and model logs.
Remote tunnel providers and hosted clients may process connection metadata or traffic according to their own policies.
Prerequisites
Node.js and npm or another runtime capable of running `npx -y @mapbox/mcp-server`.
A Mapbox access token with the scopes needed for the APIs and endpoints you plan to expose.
Review of Mapbox pricing, rate limits, token scopes, geocoding rules, routing behavior, and static map usage.
Optional hosted MCP setup review if connecting to `https://mcp.mapbox.com/mcp` through OAuth or bearer-token authentication.
Agentset account or self-hosted Agentset deployment with a populated namespace.
Agentset API key with access to the namespace Claude should query.
Node.js 18.17 or newer for running the `@agentset/mcp` package.
Namespace ID selected with `--ns` or `AGENTSET_NAMESPACE_ID`.
Unity project using Unity 2022.3 or newer for the current package metadata.
Unity Hub or a local Unity Editor installation.
Node.js 20.19 or newer, or Node.js 22.12 or newer, for `unity-mcp-cli`.
An MCP client such as Claude Code, Claude Desktop, Codex, Cursor, Gemini CLI, GitHub Copilot, Cline, or another supported client.
Anki Desktop installed and running.
The AnkiConnect add-on installed in Anki.
Node.js 22.12 or newer for the npm package path.
Review of which decks, cards, tags, media files, and note types the MCP client may access.
Install
npx -y @mapbox/mcp-server
Run `npx @agentset/mcp --ns <namespace-id>` with `AGENTSET_API_KEY` set in the MCP server environment.