How to integrate Optimoroute 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

Optimoroute logo
Claude Agent SDK logo
divider

Introduction

This guide walks you through connecting Optimoroute to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Optimoroute agent that can list all active drivers on duty today, show planned delivery routes for tomorrow, find unassigned orders for this week through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Optimoroute account through Composio's Optimoroute MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Optimoroute 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 Optimoroute
  • Configure an AI agent that can use Optimoroute as a tool
  • Run a live chat session where you can ask the agent to perform Optimoroute 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 Optimoroute MCP server, and what's possible with it?

The Optimoroute MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Optimoroute account. It provides structured and secure access to your logistics and planning data, so your agent can perform actions like retrieving driver details, viewing planned delivery routes, checking route assignments, and monitoring driver status on your behalf.

  • Live driver roster and status retrieval: Instantly fetch up-to-date information about all drivers, including their current availability and contact details.
  • Planned route overview for any date: Have your agent pull a detailed list of all planned routes for a specific date, including stop information and route parameters.
  • Monitor unassigned orders and route gaps: Easily identify orders that haven’t been assigned to a route, helping you spot scheduling bottlenecks.
  • Centralized route and driver reporting: Aggregate route and driver data to power dashboards or daily logistics summaries, all via your AI agent.

Supported Tools & Triggers

Tools
Create OrderTool to create a new order or update an existing order in OptimoRoute.
Create or Update OrdersTool to bulk create, update, or replace multiple orders at once without geocoding.
Delete All OrdersTool to remove all orders and planned routes for a specified date.
Delete OrderTool to remove a single order from the OptimoRoute system.
Delete OrdersTool to delete one or more orders from the system in bulk (max 500 per request).
Get Order Completion DetailsTool to retrieve completion details for one or more orders including proof of delivery data.
Get DriversTool to retrieve all drivers in the system.
Get Mobile EventsTool to retrieve mobile events from drivers' field operations.
Get OrdersTool to retrieve one or more orders from OptimoRoute.
Get Planning StatusTool to retrieve the status of an active planning/optimization process.
Get Planned RoutesTool to retrieve all planned routes for a given date.
Get Order Scheduling InfoTool to retrieve scheduling information for a specific order.
Search OrdersTool to search for orders in OptimoRoute based on criteria.
Start PlanningTool to start the planning/optimization process for a specified date or date range.
Stop PlanningTool to stop an active planning/optimization process.
Update Driver ParametersTool to update driver parameters for a specific date including work times, vehicle assignment, and start/end locations.
Update Drivers ParametersTool to update parameters of multiple drivers for specified dates in bulk (max 500 per request).

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 Optimoroute 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 Optimoroute 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 Optimoroute
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["optimoroute"]
    )

    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 Optimoroute
  • 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 Optimoroute 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 Optimoroute
  • 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 Optimoroute 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 Optimoroute
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["optimoroute"]
    )

    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 Optimoroute 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 Optimoroute 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 Optimoroute MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Optimoroute MCP with OpenAI Agents SDK

Claude Code logo

Claude Code

Use Optimoroute MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Optimoroute MCP with Claude Cowork

Codex logo

Codex

Use Optimoroute MCP with Codex

OpenClaw logo

OpenClaw

Use Optimoroute MCP with OpenClaw

Hermes logo

Hermes

Use Optimoroute MCP with Hermes

CLI logo

CLI

Use Optimoroute MCP with CLI

Google ADK logo

Google ADK

Use Optimoroute MCP with Google ADK

LangChain logo

LangChain

Use Optimoroute MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Optimoroute MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Optimoroute MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Optimoroute MCP with LlamaIndex

CrewAI logo

CrewAI

Use Optimoroute MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Optimoroute MCP?

With a standalone Optimoroute MCP server, the agents and LLMs can only access a fixed set of Optimoroute tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Optimoroute 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 Optimoroute tools.

Can I manage the permissions and scopes for Optimoroute while using Tool Router?

Yes, absolutely. You can configure which Optimoroute 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 Optimoroute 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↗