Mapbox MCP Server

Created By
AidenYangXa year ago
MCP Server for the Mapbox API.
Overview

what is Mapbox MCP Server?

Mapbox MCP Server is a server designed to interface with the Mapbox API, providing various navigation and search tools for developers.

how to use Mapbox MCP Server?

To use the Mapbox MCP Server, set up the server with Node.js, configure it with your Mapbox API key, and utilize the provided API endpoints for navigation and geocoding functionalities.

key features of Mapbox MCP Server?

  • Navigation tools for getting directions and calculating travel times.
  • Geocoding capabilities to convert addresses into coordinates.
  • Comprehensive error handling for API requests.
  • Rate limit management for efficient API usage.

use cases of Mapbox MCP Server?

  1. Integrating navigation features into web or mobile applications.
  2. Building location-based services that require address search and routing.
  3. Analyzing travel times and distances for logistics and planning.

FAQ from Mapbox MCP Server?

  • What are the prerequisites for using the server?

You need Node.js 16 or higher, TypeScript 4.5 or higher, and a valid Mapbox API key.

  • How do I obtain a Mapbox API key?

You can get a Mapbox API key by following the instructions on the Mapbox account access tokens page.

  • What are the rate limits for the APIs?

The Directions API allows 300 requests per minute, while the Geocoding API allows 600 requests per minute.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
AidenYangX
Star
-
Language
-
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