How to integrate Mapbox MCP with Claude Agent SDK

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Mapbox logo
Claude Agent SDK logo
divider

Introduction

This guide walks you through connecting Mapbox to the Claude Agent SDK 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 Claude Agent SDK 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

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Mapbox
  • Configure an AI agent that can use Mapbox as a tool
  • Run a live chat session where you can ask the agent to perform Mapbox operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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 & Triggers

Tools
Batch Geocode V6Tool to perform batch geocoding with up to 1000 queries in a single request.
Forward Geocode V5Tool to search for places by name or address using Mapbox Geocoding v5 API (forward geocoding).
Batch GeocodingTool to perform batch forward or reverse geocoding for multiple locations.
Forward GeocodingTool to convert free-form or structured address into geographic coordinates and place features.
Permanent Forward GeocodingTool to perform permanent forward geocoding.
Permanent Reverse GeocodingTool to perform permanent reverse geocoding.
Reverse GeocodingTool to reverse geocode coordinates into place names.
Get Access TokenTool to extract and validate Mapbox access token from connection metadata.
Get IsochroneTool to calculate areas reachable within a specified amount of time or distance from a location.
Get Map MatchingTool to snap fuzzy GPS traces to roads on the road network.
Get Optimization V1Tool to calculate optimal driving routes and trips that visit a set of waypoints.
Get SpriteTool to retrieve a sprite image or its JSON document from a Mapbox style.
Get Static ImageRequest a static map image from a Mapbox Studio style.
Get Static TilesTool to retrieve raster tiles from a Mapbox Studio style.
Get Token InformationTool to retrieve information about a Mapbox access token and validate its status.
Get Vector TilesTool to retrieve vector tiles from Mapbox-hosted vector tilesets.
Map Matching (POST)Tool to snap GPS coordinates to the road network using POST method for longer coordinate lists.
Query Tile FeaturesTool to retrieve data about specific features from vector tilesets based on a location.
Request Style Embed HTMLRetrieve embeddable HTML for a Mapbox style that can be embedded in an iframe.
Retrieve DirectionsTool to retrieve directions between waypoints.
Retrieve Font Glyph RangesTool to retrieve font glyph ranges as PBF tiles.
Retrieve MarkerTool to retrieve a standalone marker image without any background map.
Retrieve MatrixRetrieve a travel time and distance matrix between multiple locations.
Retrieve Searchbox Place DetailsTool to retrieve full details for a specific place by its Mapbox ID.
Retrieve StyleRetrieves the complete Mapbox style specification as JSON, including all layers, sources, sprites, and configuration.
Retrieve Style WMTSRetrieve a WMTS (Web Map Tile Service) capabilities document for a Mapbox style.
Retrieve Tileset MetadataTool to retrieve metadata for a Mapbox tileset.
Reverse Geocoding V6Tool to convert geographic coordinates to place names using Geocoding v6 API.
Search Box Reverse GeocodingTool to convert coordinates to places using the Search Box API (reverse geocoding).
Search Box ForwardTool to search for places by name or address using the Search Box API.
Search by CategoryTool to search for places by category (e.
Search Box SuggestTool to get autocomplete suggestions for a partial search query.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Mapbox account
  • Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The load_dotenv() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Mapbox functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Mapbox
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["mapbox"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Mapbox
  • The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Mapbox tools via Composio.",
    max_turns=10
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Mapbox
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

Here's the complete code to get you started with Mapbox and Claude Agent SDK:

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Mapbox
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["mapbox"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Mapbox tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Mapbox through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Mapbox MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Mapbox MCP with OpenAI Agents SDK

Claude Code logo

Claude Code

Use Mapbox MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Mapbox MCP with Claude Cowork

Codex logo

Codex

Use Mapbox MCP with Codex

OpenClaw logo

OpenClaw

Use Mapbox MCP with OpenClaw

Hermes logo

Hermes

Use Mapbox MCP with Hermes

CLI logo

CLI

Use Mapbox MCP with CLI

Google ADK logo

Google ADK

Use Mapbox MCP with Google ADK

LangChain logo

LangChain

Use Mapbox MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Mapbox MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Mapbox MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Mapbox MCP with LlamaIndex

CrewAI logo

CrewAI

Use Mapbox MCP with CrewAI

FAQ

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 Claude Agent SDK?

Yes, you can. Claude Agent SDK 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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Get started for freeGet a demo↗