# How to integrate Mapbox MCP with Mastra AI ```json { "title": "How to integrate Mapbox MCP with Mastra AI", "toolkit": "Mapbox", "toolkit_slug": "mapbox", "framework": "Mastra AI", "framework_slug": "mastra-ai", "url": "https://composio.dev/toolkits/mapbox/framework/mastra-ai", "markdown_url": "https://composio.dev/toolkits/mapbox/framework/mastra-ai.md", "updated_at": "2026-05-12T10:18:31.242Z" } ``` ## Introduction This guide walks you through connecting Mapbox to Mastra AI using the Composio tool router. By the end, you'll have a working Mapbox agent that can batch geocode these 10 addresses, get directions from times square to jfk, reverse geocode this latitude and longitude through natural language commands. This guide will help you understand how to give your Mastra AI agent real control over a Mapbox account through Composio's Mapbox MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Mapbox with - [OpenAI Agents SDK](https://composio.dev/toolkits/mapbox/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/mapbox/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/mapbox/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/mapbox/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/mapbox/framework/codex) - [OpenClaw](https://composio.dev/toolkits/mapbox/framework/openclaw) - [Hermes](https://composio.dev/toolkits/mapbox/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/mapbox/framework/cli) - [Google ADK](https://composio.dev/toolkits/mapbox/framework/google-adk) - [LangChain](https://composio.dev/toolkits/mapbox/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/mapbox/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/mapbox/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/mapbox/framework/crew-ai) ## TL;DR Here's what you'll learn: - Set up your environment so Mastra, OpenAI, and Composio work together - Create a Tool Router session in Composio that exposes Mapbox tools - Connect Mastra's MCP client to the Composio generated MCP URL - Fetch Mapbox tool definitions and attach them as a toolset - Build a Mastra agent that can reason, call tools, and return structured results - Run an interactive CLI where you can chat with your Mapbox agent ## What is Mastra AI? Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP. Key features include: - MCP Client: Built-in support for Model Context Protocol servers - Toolsets: Organize tools into logical groups - Step Callbacks: Monitor and debug agent execution - OpenAI Integration: Works with OpenAI models via @ai-sdk/openai ## What is the Mapbox MCP server, and what's possible with it? The Mapbox MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Mapbox account. It provides structured and secure access to your mapping and location data, so your agent can perform actions like geocoding addresses, calculating travel routes, retrieving map embeds, and analyzing travel matrices on your behalf. - Batch and individual geocoding: Instantly convert addresses or place names to geographic coordinates—or reverse geocode coordinates to place names—using both batch and individual tools. - Route and directions retrieval: Let your agent fetch optimized driving, walking, or cycling directions between waypoints, including turn-by-turn instructions when needed. - Distance and travel time analysis: Have the agent generate travel time and distance matrices to compare routes or plan logistics across multiple locations. - Map style embed generation: Retrieve ready-to-use embeddable HTML for your custom Mapbox map styles, perfect for sharing or displaying maps in web apps. - Permanent geocoding and font data retrieval: Access enterprise-grade, cacheable geocoding data or fetch font glyph ranges for custom rendering and advanced mapping use cases. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `MAPBOX_GEOCODE_BATCH_V6` | Batch Geocode V6 | Tool to perform batch geocoding with up to 1000 queries in a single request. Use when you need to geocode multiple locations efficiently (forward, reverse, or structured). Supports mixing query types in the same batch. | | `MAPBOX_GEOCODE_FORWARD_V5` | Forward Geocode V5 | Tool to search for places by name or address using Mapbox Geocoding v5 API (forward geocoding). Use when you need to convert place names or addresses to geographic coordinates using the v5 endpoint. | | `MAPBOX_GEOCODING_BATCH` | Batch Geocoding | Tool to perform batch forward or reverse geocoding for multiple locations. Use when you need consistent geocoding of up to 50 queries in one call. | | `MAPBOX_GEOCODING_FORWARD` | Forward Geocoding | Tool to convert free-form or structured address into geographic coordinates and place features. Use when you need forward geocoding from text or address components. | | `MAPBOX_GEOCODING_PERMANENT_FORWARD` | Permanent Forward Geocoding | Tool to perform permanent forward geocoding. Use when you need enterprise-grade permanent geocoding after confirming account privileges. | | `MAPBOX_GEOCODING_PERMANENT_REVERSE` | Permanent Reverse Geocoding | Tool to perform permanent reverse geocoding. Use after obtaining coordinates to get cacheable place data. Example: lon=-73.989, lat=40.733 | | `MAPBOX_GEOCODING_REVERSE` | Reverse Geocoding | Tool to reverse geocode coordinates into place names. Use after obtaining coordinates. | | `MAPBOX_GET_ACCESS_TOKEN` | Get Access Token | Tool to extract and validate Mapbox access token from connection metadata. Use when you need a valid token for downstream actions. | | `MAPBOX_GET_ISOCHRONE` | Get Isochrone | Tool to calculate areas reachable within a specified amount of time or distance from a location. Use when you need to visualize travel time or distance zones for routing analysis. | | `MAPBOX_GET_MAP_MATCHING` | Get Map Matching | Tool to snap fuzzy GPS traces to roads on the road network. Use when you need to clean up inaccurate location traces for display or analysis. | | `MAPBOX_GET_OPTIMIZATION_V1` | Get Optimization V1 | Tool to calculate optimal driving routes and trips that visit a set of waypoints. Use when you need to find the best order to visit multiple locations with optimized routing. | | `MAPBOX_GET_SPRITE` | Get Sprite | Tool to retrieve a sprite image or its JSON document from a Mapbox style. Use when you need sprite assets for rendering map icons. Sprites are collections of small icons used in map styles. The JSON format returns metadata about icon positions and dimensions within the sprite sheet, while the PNG format returns the actual image. Sprite sheets optimize performance by combining multiple icons into a single image. | | `MAPBOX_GET_STATIC_IMAGE` | Get Static Image | Request a static map image from a Mapbox Studio style. Returns a PNG or JPEG image of the specified map area with customizable parameters including location, zoom level, camera angle, and optional overlays like markers or GeoJSON features. Use when you need to generate static map images for embedding in documents, emails, or web pages without interactive map functionality. | | `MAPBOX_GET_STATIC_TILES` | Get Static Tiles | Tool to retrieve raster tiles from a Mapbox Studio style. Use when you need map tiles for specific coordinates and zoom levels. Returns PNG or JPG raster tiles that can be assembled to create map visualizations. Tiles follow the XYZ tiling scheme where the world is divided into a grid at each zoom level. Supports retina/high-DPI displays via the @2x suffix. | | `MAPBOX_GET_TOKEN` | Get Token Information | Tool to retrieve information about a Mapbox access token and validate its status. Use when you need to check token validity or retrieve token metadata. | | `MAPBOX_GET_VECTOR_TILES` | Get Vector Tiles | Tool to retrieve vector tiles from Mapbox-hosted vector tilesets. Use when you need tile data for mapping applications at specific zoom levels and coordinates. | | `MAPBOX_POST_MAP_MATCHING` | Map Matching (POST) | Tool to snap GPS coordinates to the road network using POST method for longer coordinate lists. Use when you have GPS traces to match to roads (2-100 coordinates). | | `MAPBOX_QUERY_TILE_FEATURES` | Query Tile Features | Tool to retrieve data about specific features from vector tilesets based on a location. Use when you need to query tileset features at a geographic point, such as finding buildings, roads, or points of interest near coordinates. | | `MAPBOX_REQUEST_STYLE_EMBED_HTML` | Request Style Embed HTML | Retrieve embeddable HTML for a Mapbox style that can be embedded in an iframe. Returns a complete HTML document with Mapbox GL JS code that renders an interactive map with the specified style. Useful for quickly embedding Mapbox maps into web pages without custom JavaScript code. | | `MAPBOX_RETRIEVE_DIRECTIONS` | Retrieve Directions | Tool to retrieve directions between waypoints. Use when you need navigation routes with optional turn-by-turn instructions after confirming origin and destination. | | `MAPBOX_RETRIEVE_FONT_GLYPH_RANGES` | Retrieve Font Glyph Ranges | Tool to retrieve font glyph ranges as PBF tiles. Use when you have confirmed the font name, codepoint range, and valid token. | | `MAPBOX_RETRIEVE_MARKER` | Retrieve Marker | Tool to retrieve a standalone marker image without any background map. Returns a PNG image file of the specified marker type. Use when you need to obtain marker icons for display or reference purposes. | | `MAPBOX_RETRIEVE_MATRIX` | Retrieve Matrix | Retrieve a travel time and distance matrix between multiple locations. Use this tool when you need to calculate travel times and/or distances between many origin-destination pairs efficiently (e.g., comparing routes from multiple starting points to multiple destinations, finding the nearest location from a set, or optimizing multi-stop routing). Returns matrices showing durations (in seconds) and distances (in meters) between all coordinate pairs. | | `MAPBOX_RETRIEVE_SEARCHBOX_PLACE` | Retrieve Searchbox Place Details | Tool to retrieve full details for a specific place by its Mapbox ID. Use when you have a mapbox_id from a search suggestion and need complete place information. | | `MAPBOX_RETRIEVE_STYLE` | Retrieve Style | Retrieves the complete Mapbox style specification as JSON, including all layers, sources, sprites, and configuration. A Mapbox style defines how a map is rendered, including data sources, layer styling, fonts, and sprites. This action returns the full style specification conforming to the Mapbox Style Specification, which can be used with Mapbox GL JS, mobile SDKs, or for analyzing map configurations. Use this action when you need to: - Inspect or analyze a map style's configuration - Retrieve style definitions for programmatic rendering - Examine layers, sources, and styling rules - Get complete style specifications for custom map implementations | | `MAPBOX_RETRIEVE_STYLE_WMTS` | Retrieve Style WMTS | Retrieve a WMTS (Web Map Tile Service) capabilities document for a Mapbox style. This action returns an OGC-compliant WMTS XML document that describes how to access map tiles for the specified style. The document includes tile matrix sets, supported coordinate systems (EPSG:3857), and tile URL templates. Use this when integrating Mapbox styles with desktop GIS applications (ArcGIS, QGIS, CARTO, Tableau) or any WMTS-compliant mapping client. The WMTS endpoint works with both Mapbox's official styles (e.g., streets-v12, satellite-v9) and custom styles created in Mapbox Studio. | | `MAPBOX_RETRIEVE_TILESET_METADATA` | Retrieve Tileset Metadata | Tool to retrieve metadata for a Mapbox tileset. Use when you need TileJSON details including bounds, zooms, and layer info. | | `MAPBOX_REVERSE_GEOCODE_V6` | Reverse Geocoding V6 | Tool to convert geographic coordinates to place names using Geocoding v6 API. Use when you need to perform reverse geocoding from latitude/longitude coordinates. | | `MAPBOX_REVERSE_SEARCHBOX` | Search Box Reverse Geocoding | Tool to convert coordinates to places using the Search Box API (reverse geocoding). Use when you need to find place names, addresses, or points of interest for given coordinates. | | `MAPBOX_SEARCH_BOX_FORWARD` | Search Box Forward | Tool to search for places by name or address using the Search Box API. Use when you need to find locations, addresses, or points of interest based on a text query. | | `MAPBOX_SEARCH_CATEGORY` | Search by Category | Tool to search for places by category (e.g., restaurants, hotels, coffee shops). Use when you need to find POIs in a specific category, optionally filtered by location, bounding box, or proximity. | | `MAPBOX_SUGGEST_SEARCHBOX` | Search Box Suggest | Tool to get autocomplete suggestions for a partial search query. Use when you need address or place suggestions as users type, before retrieving full details. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Mapbox MCP server is an implementation of the Model Context Protocol that connects your AI agent to Mapbox. It provides structured and secure access so your agent can perform Mapbox operations on your behalf through a secure, permission-based interface. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites Before starting, make sure you have: - Node.js 18 or higher - A Composio account with an active API key - An OpenAI API key - Basic familiarity with TypeScript ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. - You need credits or a connected billing setup to use the models. - Store the key somewhere safe. Composio API Key - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Go to Settings and copy your API key. - This key lets your Mastra agent talk to Composio and reach Mapbox through MCP. ### 2. Install dependencies Install the required packages. What's happening: - @composio/core is the Composio SDK for creating MCP sessions - @mastra/core provides the Agent class - @mastra/mcp is Mastra's MCP client - @ai-sdk/openai is the model wrapper for OpenAI - dotenv loads environment variables from .env ```bash npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's happening: - COMPOSIO_API_KEY authenticates your requests to Composio - COMPOSIO_USER_ID tells Composio which user this session belongs to - OPENAI_API_KEY lets the Mastra agent call OpenAI models ```bash COMPOSIO_API_KEY=your_composio_api_key_here COMPOSIO_USER_ID=your_user_id_here OPENAI_API_KEY=your_openai_api_key_here ``` ### 4. Import libraries and validate environment What's happening: - dotenv/config auto loads your .env so process.env.* is available - openai gives you a Mastra compatible model wrapper - Agent is the Mastra agent that will call tools and produce answers - MCPClient connects Mastra to your Composio MCP server - Composio is used to create a Tool Router session ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Agent } from "@mastra/core/agent"; import { MCPClient } from "@mastra/mcp"; import { Composio } from "@composio/core"; import * as readline from "readline"; import type { AiMessageType } from "@mastra/core/agent"; const openaiAPIKey = process.env.OPENAI_API_KEY; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set"); if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set"); if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set"); const composio = new Composio({ apiKey: composioAPIKey as string, }); ``` ### 5. Create a Tool Router session for Mapbox What's happening: - create spins up a short-lived MCP HTTP endpoint for this user - The toolkits array contains "mapbox" for Mapbox access - session.mcp.url is the MCP URL that Mastra's MCPClient will connect to ```typescript async function main() { const session = await composio.create( composioUserID as string, { toolkits: ["mapbox"], }, ); const composioMCPUrl = session.mcp.url; console.log("Mapbox MCP URL:", composioMCPUrl); ``` ### 6. Configure Mastra MCP client and fetch tools What's happening: - MCPClient takes an id for this client and a list of MCP servers - The headers property includes the x-api-key for authentication - getTools fetches the tool definitions exposed by the Mapbox toolkit ```typescript const mcpClient = new MCPClient({ id: composioUserID as string, servers: { nasdaq: { url: new URL(composioMCPUrl), requestInit: { headers: session.mcp.headers, }, }, }, timeout: 30_000, }); console.log("Fetching MCP tools from Composio..."); const composioTools = await mcpClient.getTools(); console.log("Number of tools:", Object.keys(composioTools).length); ``` ### 7. Create the Mastra agent What's happening: - Agent is the core Mastra agent - name is just an identifier for logging and debugging - instructions guide the agent to use tools instead of only answering in natural language - model uses openai("gpt-5") to configure the underlying LLM ```typescript const agent = new Agent({ name: "mapbox-mastra-agent", instructions: "You are an AI agent with Mapbox tools via Composio.", model: "openai/gpt-5", }); ``` ### 8. Set up interactive chat interface What's happening: - messages keeps the full conversation history in Mastra's expected format - agent.generate runs the agent with conversation history and Mapbox toolsets - maxSteps limits how many tool calls the agent can take in a single run - onStepFinish is a hook that prints intermediate steps for debugging ```typescript let messages: AiMessageType[] = []; console.log("Chat started! Type 'exit' or 'quit' to end.\n"); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); rl.on("line", async (userInput: string) => { const trimmedInput = userInput.trim(); if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) { console.log("\nGoodbye!"); rl.close(); process.exit(0); } if (!trimmedInput) { rl.prompt(); return; } messages.push({ id: crypto.randomUUID(), role: "user", content: trimmedInput, }); console.log("\nAgent is thinking...\n"); try { const response = await agent.generate(messages, { toolsets: { mapbox: composioTools, }, maxSteps: 8, }); const { text } = response; if (text && text.trim().length > 0) { console.log(`Agent: ${text}\n`); messages.push({ id: crypto.randomUUID(), role: "assistant", content: text, }); } } catch (error) { console.error("\nError:", error); } rl.prompt(); }); rl.on("close", async () => { console.log("\nSession ended."); await mcpClient.disconnect(); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Complete Code ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Agent } from "@mastra/core/agent"; import { MCPClient } from "@mastra/mcp"; import { Composio } from "@composio/core"; import * as readline from "readline"; import type { AiMessageType } from "@mastra/core/agent"; const openaiAPIKey = process.env.OPENAI_API_KEY; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set"); if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set"); if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set"); const composio = new Composio({ apiKey: composioAPIKey as string }); async function main() { const session = await composio.create(composioUserID as string, { toolkits: ["mapbox"], }); const composioMCPUrl = session.mcp.url; const mcpClient = new MCPClient({ id: composioUserID as string, servers: { mapbox: { url: new URL(composioMCPUrl), requestInit: { headers: session.mcp.headers, }, }, }, timeout: 30_000, }); const composioTools = await mcpClient.getTools(); const agent = new Agent({ name: "mapbox-mastra-agent", instructions: "You are an AI agent with Mapbox tools via Composio.", model: "openai/gpt-5", }); let messages: AiMessageType[] = []; const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); rl.on("line", async (input: string) => { const trimmed = input.trim(); if (["exit", "quit"].includes(trimmed.toLowerCase())) { rl.close(); return; } messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed }); const { text } = await agent.generate(messages, { toolsets: { mapbox: composioTools }, maxSteps: 8, }); if (text) { console.log(`Agent: ${text}\n`); messages.push({ id: crypto.randomUUID(), role: "assistant", content: text }); } rl.prompt(); }); rl.on("close", async () => { await mcpClient.disconnect(); process.exit(0); }); } main(); ``` ## Conclusion You've built a Mastra AI agent that can interact with Mapbox through Composio's Tool Router. You can extend this further by: - Adding other toolkits like Gmail, Slack, or GitHub - Building a web-based chat interface around this agent - Using multiple MCP endpoints to enable cross-app workflows ## How to build Mapbox MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/mapbox/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/mapbox/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/mapbox/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/mapbox/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/mapbox/framework/codex) - [OpenClaw](https://composio.dev/toolkits/mapbox/framework/openclaw) - [Hermes](https://composio.dev/toolkits/mapbox/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/mapbox/framework/cli) - [Google ADK](https://composio.dev/toolkits/mapbox/framework/google-adk) - [LangChain](https://composio.dev/toolkits/mapbox/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/mapbox/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/mapbox/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/mapbox/framework/crew-ai) ## Related Toolkits - [Excel](https://composio.dev/toolkits/excel) - Microsoft Excel is a robust spreadsheet application for organizing, analyzing, and visualizing data. It's the go-to tool for calculations, reporting, and flexible data management. - [21risk](https://composio.dev/toolkits/_21risk) - 21RISK is a web app built for easy checklist, audit, and compliance management. It streamlines risk processes so teams can focus on what matters. - [Abstract](https://composio.dev/toolkits/abstract) - Abstract provides a suite of APIs for automating data validation and enrichment tasks. It helps developers streamline workflows and ensure data quality with minimal effort. - [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time. - [Agenty](https://composio.dev/toolkits/agenty) - Agenty is a web scraping and automation platform for extracting data and automating browser tasks—no coding needed. It streamlines data collection, monitoring, and repetitive online actions. - [Ambee](https://composio.dev/toolkits/ambee) - Ambee is an environmental data platform providing real-time, hyperlocal APIs for air quality, weather, and pollen. Get precise environmental insights to power smarter decisions in your apps and workflows. - [Ambient weather](https://composio.dev/toolkits/ambient_weather) - Ambient Weather is a platform for personal weather stations with a robust API for accessing local, real-time, and historical weather data. Get detailed environmental insights directly from your own sensors for smarter apps and automations. - [Anonyflow](https://composio.dev/toolkits/anonyflow) - Anonyflow is a service for encryption-based data anonymization and secure data sharing. It helps organizations meet GDPR, CCPA, and HIPAA data privacy compliance requirements. - [Api ninjas](https://composio.dev/toolkits/api_ninjas) - Api ninjas offers 120+ public APIs spanning categories like weather, finance, sports, and more. Developers use it to supercharge apps with real-time data and actionable endpoints. - [Api sports](https://composio.dev/toolkits/api_sports) - Api sports is a comprehensive sports data platform covering 2,000+ competitions with live scores and 15+ years of stats. Instantly access up-to-date sports information for analysis, apps, or chatbots. - [Apify](https://composio.dev/toolkits/apify) - Apify is a cloud platform for building, deploying, and managing web scraping and automation tools called Actors. It lets you automate data extraction and workflow tasks at scale—no infrastructure headaches. - [Autom](https://composio.dev/toolkits/autom) - Autom is a lightning-fast search engine results data platform for Google, Bing, and Brave. Developers use it to access fresh, low-latency SERP data on demand. - [Beaconchain](https://composio.dev/toolkits/beaconchain) - Beaconchain is a real-time analytics platform for Ethereum 2.0's Beacon Chain. It provides detailed insights into validators, blocks, and overall network performance. - [Big data cloud](https://composio.dev/toolkits/big_data_cloud) - BigDataCloud provides APIs for geolocation, reverse geocoding, and address validation. Instantly access reliable location intelligence to enhance your applications and workflows. - [Bigpicture io](https://composio.dev/toolkits/bigpicture_io) - BigPicture.io offers APIs for accessing detailed company and profile data. Instantly enrich your applications with up-to-date insights on 20M+ businesses. - [Bitquery](https://composio.dev/toolkits/bitquery) - Bitquery is a blockchain data platform offering indexed, real-time, and historical data from 40+ blockchains via GraphQL APIs. Get unified, reliable access to complex on-chain data for analytics, trading, and research. - [Brightdata](https://composio.dev/toolkits/brightdata) - Brightdata is a leading web data platform offering advanced scraping, SERP APIs, and anti-bot tools. It lets you collect public web data at scale, bypassing blocks and friction. - [Builtwith](https://composio.dev/toolkits/builtwith) - BuiltWith is a web technology profiler that uncovers the technologies powering any website. Gain actionable insights into analytics, hosting, and content management stacks for smarter research and lead generation. - [Byteforms](https://composio.dev/toolkits/byteforms) - Byteforms is an all-in-one platform for creating forms, managing submissions, and integrating data. It streamlines workflows by centralizing form data collection and automation. - [Cabinpanda](https://composio.dev/toolkits/cabinpanda) - Cabinpanda is a data collection platform for building and managing online forms. It helps streamline how you gather, organize, and analyze responses. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Mapbox MCP? With a standalone Mapbox MCP server, the agents and LLMs can only access a fixed set of Mapbox tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Mapbox and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Mastra AI? Yes, you can. Mastra AI fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Mapbox tools. ### Can I manage the permissions and scopes for Mapbox while using Tool Router? Yes, absolutely. You can configure which Mapbox scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do. ### How safe is my data with Composio Tool Router? All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Mapbox data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)