# How to connect Mapbox to OpenClaw (paste one key, 32 tools) > Connect Mapbox to OpenClaw with ClawLink: paste your Mapbox key once and 32 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/mapbox The usual route to Mapbox access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Mapbox setup: install one ClawHub skill, connect Mapbox in the browser, and OpenClaw can call real Mapbox actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Mapbox. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Mapbox** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect mapbox # connect Mapbox (browser OAuth) npx -y @useclawlink/cli actions mapbox # list available actions npx -y @useclawlink/cli run mapbox --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Mapbox in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Mapbox API key once. Verify the connection by asking OpenClaw: > Use Mapbox to geocode batch v6 and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Mapbox is connected in the dashboard, that agent calls the same 32 Mapbox tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Mapbox MCP for OpenClaw Looking for a Mapbox MCP server for OpenClaw? ClawLink connects Mapbox to OpenClaw and exposes 32 Mapbox tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Mapbox integration](https://claw-link.dev/hermes/mapbox) works the same way. ## What the OpenClaw Mapbox integration can do 32 Mapbox tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 32. ### 30 of 32 Mapbox tools for OpenClaw | Tool | What it does | |---|---| | **Geocode batch v6** `mapbox_geocode_batch_v6` | Perform batch geocoding with up to 1000 queries in a single request | | **Geocode forward v5** `mapbox_geocode_forward_v5` | Search for places by name or address using Mapbox Geocoding v5 API (forward geocoding) | | **Geocoding batch** `mapbox_geocoding_batch` | Perform batch forward or reverse geocoding for multiple locations | | **Geocoding forward** `mapbox_geocoding_forward` | Convert free-form or structured address into geographic coordinates and place features | | **Geocoding permanent forward** `mapbox_geocoding_permanent_forward` | Perform permanent forward geocoding | | **Geocoding permanent reverse** `mapbox_geocoding_permanent_reverse` | Perform permanent reverse geocoding | | **Geocoding reverse** `mapbox_geocoding_reverse` | Reverse geocode coordinates into place names | | **Get access token** `mapbox_get_access_token` | Extract and validate Mapbox access token from connection metadata | | **Get isochrone** `mapbox_get_isochrone` | Calculate areas reachable within a specified amount of time or distance from a location | | **Get map matching** `mapbox_get_map_matching` | Snap fuzzy GPS traces to roads on the road network | | **Get optimization v1** `mapbox_get_optimization_v1` | Calculate optimal driving routes and trips that visit a set of waypoints | | **Get sprite** `mapbox_get_sprite` | Retrieve a sprite image or its JSON document from a Mapbox style | | **Get static image** `mapbox_get_static_image` | Request a static map image from a Mapbox Studio style | | **Get static tiles** `mapbox_get_static_tiles` | Retrieve raster tiles from a Mapbox Studio style | | **Get token** `mapbox_get_token` | Retrieve information about a Mapbox access token and validate its status | | **Get vector tiles** `mapbox_get_vector_tiles` | Retrieve vector tiles from Mapbox-hosted vector tilesets | | **Post map matching** `mapbox_post_map_matching` | Snap GPS coordinates to the road network using POST method for longer coordinate lists | | **Query tile features** `mapbox_query_tile_features` | Retrieve data about specific features from vector tilesets based on a location | | **Request style embed HTML** `mapbox_request_style_embed_html` | Retrieve embeddable HTML for a Mapbox style that can be embedded in an iframe | | **Retrieve directions** `mapbox_retrieve_directions` | Retrieve directions between waypoints | | **Retrieve font glyph ranges** `mapbox_retrieve_font_glyph_ranges` | Retrieve font glyph ranges as PBF tiles | | **Retrieve marker** `mapbox_retrieve_marker` | Retrieve a standalone marker image without any background map | | **Retrieve matrix** `mapbox_retrieve_matrix` | Retrieve a travel time and distance matrix between multiple locations | | **Retrieve searchbox place** `mapbox_retrieve_searchbox_place` | Retrieve full details for a specific place by its Mapbox ID | | **Retrieve style** `mapbox_retrieve_style` | Retrieves the complete Mapbox style specification as JSON, including all layers, sources | | **Retrieve style wmts** `mapbox_retrieve_style_wmts` | Retrieve a WMTS (Web Map Tile Service) capabilities document for a Mapbox style | | **Retrieve tileset metadata** `mapbox_retrieve_tileset_metadata` | Retrieve metadata for a Mapbox tileset | | **Reverse geocode v6** `mapbox_reverse_geocode_v6` | Convert geographic coordinates to place names using Geocoding v6 API | | **Reverse searchbox** `mapbox_reverse_searchbox` | Convert coordinates to places using the Search Box API (reverse geocoding) | | **Search box forward** `mapbox_search_box_forward` | Search for places by name or address using the Search Box API | ## Example prompts **Geocode Batch V6** > Use Mapbox to geocode batch v6 and walk me through the result in plain English. **Geocode Forward V5** > Use Mapbox to geocode forward v5 and walk me through the result in plain English. **Geocoding Batch** > Use Mapbox to geocoding batch and walk me through the result in plain English. **Geocoding Forward** > Use Mapbox to geocoding forward and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Mapbox working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Mapbox API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Mapbox account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Mapbox. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Mapbox actions to the runtime in a format your agent can reliably use. | 32 tools for Mapbox are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Mapbox to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Mapbox in the browser, and the 32 tools above work from chat. There is no SDK and no config file, and the Mapbox key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Mapbox skill but can't call the tools The ClawHub skill teaches OpenClaw about Mapbox, but the calls run through the ClawLink plugin and your connected account. Make sure Mapbox is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Mapbox from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Mapbox tools Mapbox tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Mapbox call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Mapbox returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Mapbox has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Mapbox integration? Yes. ClawLink is the fastest way to connect OpenClaw to Mapbox: link your Mapbox account once in the browser and OpenClaw can call the Mapbox API through 32 ready-made tools — no custom code or token handling. ### How do I add Mapbox to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Mapbox skill from ClawHub, then you click Connect in the dashboard to authorize Mapbox. OpenClaw calls the tools from the next message — no config files, and the Mapbox key you paste is stored server-side instead of in your environment. ### How long does it take to connect Mapbox to OpenClaw? About two minutes. Sign in, click Connect next to Mapbox in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Mapbox up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Mapbox working from chat. ### OpenClaw installed the Mapbox skill but can't call the tools The ClawHub skill teaches OpenClaw about Mapbox, but the calls run through the ClawLink plugin and your connected account. Make sure Mapbox is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [GitHub](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [Connect SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.