Mapbox MCP Server

Created By
mapboxa year ago
Mapbox Model Context Protocol (MCP) server
Overview

what is Mapbox MCP Server?

Mapbox MCP Server is a Node.js server that implements the Model Context Protocol (MCP) for Mapbox APIs, enabling developers to integrate various Mapbox services into their applications.

how to use Mapbox MCP Server?

To use the MCP server, you need a Mapbox access token. Sign up for a free Mapbox account, create a token, and follow the integration guides provided in the documentation.

key features of Mapbox MCP Server?

  • Implements Model Context Protocol for seamless integration with Mapbox APIs.
  • Supports various tools for routing, geocoding, and map image generation.
  • Provides detailed integration guides for different development environments.

use cases of Mapbox MCP Server?

  1. Integrating Mapbox APIs into web and mobile applications.
  2. Calculating travel times and distances for logistics applications.
  3. Generating static map images for reporting and visualization.

FAQ from Mapbox MCP Server?

  • What is required to use the MCP server?

A Mapbox access token is required to access the server's features.

  • Can I use the MCP server for free?

Yes, you can sign up for a free Mapbox account to obtain an access token.

  • What programming languages are supported?

The server is built with Node.js, but it can be integrated with applications in various programming languages.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mapbox
Star
0
Language
TypeScript
License
View license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago