This guide explains how to configure VS Code for use with the Mapbox MCP Server.
- VS Code installed and configured with copilot
- Mapbox MCP Server built locally
# from repository root:
# using node
npm install
npm run build
# note your absolute path to node, you will need it for MCP config
# For Mac/Linux
which node
# For Windows
where node
# or alternatively, using docker
docker build -t mapbox-mcp-server .- Go to your
settings.json - At the top level add MCP config, for example:
- NPM version
"mcp": { "servers": { "MapboxServer": { "type": "stdio", "command": <PATH_TO_YOUR_NPX>, "args": ["-y", "@mapbox/mcp-server"], "env": { "MAPBOX_ACCESS_TOKEN": <YOUR_TOKEN> } } }, },
- Docker version
"mcp": { "servers": { "MapboxServer": { "type": "stdio", "command": "docker", "args": [ "run", "-i", "--rm", "mapbox-mcp-server" ], "env": { "MAPBOX_ACCESS_TOKEN": "YOUR_TOKEN" } } }, },
- Node version
"mcp": { "servers": { "MapboxServer": { "type": "stdio", "command": <PATH_TO_YOUR_NODE>, "args": [ "/YOUR_PATH_TO_GIT_REPOSITORY/dist/esm/index.js" ], "env": { "MAPBOX_ACCESS_TOKEN": "YOUR_TOKEN" } } }, },
- NPM version
You might need to restart VS Code. You should see Mapbox Server appear in tools menu.
Note, the results can vary based on current traffic conditions and exact values of parameters used.
VS Code does not currently support the MCP-UI specification for embedded interactive elements. When you use tools like static_map_image_tool, you'll receive:
- ✅ Base64-encoded map images that VS Code can display
- ❌ Interactive iframe embeds (not supported by VS Code)
The server is fully backwards compatible - all tools work normally, you just won't see interactive map embeds. For more information about MCP-UI support in this server, see the MCP-UI documentation.

