# How to integrate Mapbox MCP with CrewAI ```json { "title": "How to integrate Mapbox MCP with CrewAI", "toolkit": "Mapbox", "toolkit_slug": "mapbox", "framework": "CrewAI", "framework_slug": "crew-ai", "url": "https://composio.dev/toolkits/mapbox/framework/crew-ai", "markdown_url": "https://composio.dev/toolkits/mapbox/framework/crew-ai.md", "updated_at": "2026-05-12T10:18:31.242Z" } ``` ## Introduction This guide walks you through connecting Mapbox to CrewAI 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 CrewAI 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) - [Mastra AI](https://composio.dev/toolkits/mapbox/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/mapbox/framework/llama-index) ## TL;DR Here's what you'll learn: - Get a Composio API key and configure your Mapbox connection - Set up CrewAI with an MCP enabled agent - Create a Tool Router session or standalone MCP server for Mapbox - Build a conversational loop where your agent can execute Mapbox operations ## What is CrewAI? CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews. Key features include: - Agent Roles: Define specialized agents with specific goals and backstories - Task Management: Create tasks with clear descriptions and expected outputs - Crew Orchestration: Combine agents and tasks into collaborative workflows - MCP Integration: Connect to external tools through Model Context Protocol ## 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: - Python 3.9 or higher - A Composio account and API key - A Mapbox connection authorized in Composio - An OpenAI API key for the CrewAI LLM - Basic familiarity with Python ### 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'll need credits to use the models, or you can connect to another model provider. - Keep the API key safe. Composio API Key - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Navigate to your API settings and generate a new API key. - Store this key securely as you'll need it for authentication. ### 2. Install dependencies **What's happening:** - composio connects your agent to Mapbox via MCP - crewai provides Agent, Task, Crew, and LLM primitives - crewai-tools[mcp] includes MCP helpers - python-dotenv loads environment variables from .env ```bash pip install composio crewai crewai-tools[mcp] python-dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's happening: - COMPOSIO_API_KEY authenticates with Composio - USER_ID scopes the session to your account - OPENAI_API_KEY lets CrewAI use your chosen OpenAI model ```bash COMPOSIO_API_KEY=your_composio_api_key_here USER_ID=your_user_id_here OPENAI_API_KEY=your_openai_api_key_here ``` ### 4. Import dependencies **What's happening:** - CrewAI classes define agents and tasks, and run the workflow - MCPServerHTTP connects the agent to an MCP endpoint - Composio will give you a short lived Mapbox MCP URL ```python import os from composio import Composio from crewai import Agent, Task, Crew from crewai_tools import MCPServerAdapter import dotenv dotenv.load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID") if not COMPOSIO_API_KEY: raise ValueError("COMPOSIO_API_KEY is not set") if not COMPOSIO_USER_ID: raise ValueError("COMPOSIO_USER_ID is not set") ``` ### 5. Create a Composio Tool Router session for Mapbox **What's happening:** - You create a Mapbox only session through Composio - Composio returns an MCP HTTP URL that exposes Mapbox tools ```python composio_client = Composio(api_key=COMPOSIO_API_KEY) session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["mapbox"]) url = session.mcp.url ``` ### 6. Initialize the MCP Server **What's Happening:** - Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication. - MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format. - Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools. - Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops. - Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries. ```python server_params = { "url": url, "transport": "streamable-http", "headers": {"x-api-key": COMPOSIO_API_KEY}, } with MCPServerAdapter(server_params) as tools: agent = Agent( role="Search Assistant", goal="Help users search the internet effectively", backstory="You are a helpful assistant with access to search tools.", tools=tools, verbose=False, max_iter=10, ) ``` ### 7. Create a CLI Chatloop and define the Crew **What's Happening:** - Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable. - Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean. - Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses. - Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context. - Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response. - Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity. ```python print("Chat started! Type 'exit' or 'quit' to end.\n") conversation_context = "" while True: user_input = input("You: ").strip() if user_input.lower() in ["exit", "quit", "bye"]: print("\nGoodbye!") break if not user_input: continue conversation_context += f"\nUser: {user_input}\n" print("\nAgent is thinking...\n") task = Task( description=( f"Conversation history:\n{conversation_context}\n\n" f"Current request: {user_input}" ), expected_output="A helpful response addressing the user's request", agent=agent, ) crew = Crew(agents=[agent], tasks=[task], verbose=False) result = crew.kickoff() response = str(result) conversation_context += f"Agent: {response}\n" print(f"Agent: {response}\n") ``` ## Complete Code ```python from crewai import Agent, Task, Crew, LLM from crewai_tools import MCPServerAdapter from composio import Composio from dotenv import load_dotenv import os load_dotenv() GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY") COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID") if not GOOGLE_API_KEY: raise ValueError("GOOGLE_API_KEY is not set in the environment.") if not COMPOSIO_API_KEY: raise ValueError("COMPOSIO_API_KEY is not set in the environment.") if not COMPOSIO_USER_ID: raise ValueError("COMPOSIO_USER_ID is not set in the environment.") # Initialize Composio and create a session composio = Composio(api_key=COMPOSIO_API_KEY) session = composio.create( user_id=COMPOSIO_USER_ID, toolkits=["mapbox"], ) url = session.mcp.url # Configure LLM llm = LLM( model="gpt-5", api_key=os.getenv("OPENAI_API_KEY"), ) server_params = { "url": url, "transport": "streamable-http", "headers": {"x-api-key": COMPOSIO_API_KEY}, } with MCPServerAdapter(server_params) as tools: agent = Agent( role="Search Assistant", goal="Help users with internet searches", backstory="You are an expert assistant with access to Composio Search tools.", tools=tools, llm=llm, verbose=False, max_iter=10, ) print("Chat started! Type 'exit' or 'quit' to end.\n") conversation_context = "" while True: user_input = input("You: ").strip() if user_input.lower() in ["exit", "quit", "bye"]: print("\nGoodbye!") break if not user_input: continue conversation_context += f"\nUser: {user_input}\n" print("\nAgent is thinking...\n") task = Task( description=( f"Conversation history:\n{conversation_context}\n\n" f"Current request: {user_input}" ), expected_output="A helpful response addressing the user's request", agent=agent, ) crew = Crew(agents=[agent], tasks=[task], verbose=False) result = crew.kickoff() response = str(result) conversation_context += f"Agent: {response}\n" print(f"Agent: {response}\n") ``` ## Conclusion You now have a CrewAI agent connected to Mapbox through Composio's Tool Router. The agent can perform Mapbox operations through natural language commands. Next steps: - Add role-specific instructions to customize agent behavior - Plug in more toolkits for multi-app workflows - Chain tasks for complex multi-step operations ## 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) - [Mastra AI](https://composio.dev/toolkits/mapbox/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/mapbox/framework/llama-index) ## 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. - [Agentql](https://composio.dev/toolkits/agentql) - Agentql is a toolkit that connects AI agents to the web using a specialized query language. It enables structured web interaction and data extraction for smarter automations. - [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. ## 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 CrewAI? Yes, you can. CrewAI 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)