How to integrate Route4me MCP with LlamaIndex

This guide walks you through connecting Route4me to LlamaIndex using the Composio tool router. By the end, you'll have a working Route4me agent that can list all available delivery vehicles today, mark stop 12 on route 8 as completed, show vehicles with capacity over 1000 lbs through natural language commands. This guide will help you understand how to give your LlamaIndex agent real control over a Route4me account through Composio's Route4me MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for free Get a demo

Route4me

Api Key

Route4Me is a Last Mile Routing API that automates route planning for logistics teams. It helps businesses save time and fuel with optimized, real-time delivery routes.

97 Tools

Managed auth

Connect Route4me without auth hassles

We manage OAuth, API keys, token refresh, and scopes — you just build.

Try for free

Introduction

This guide will help you understand how to give your LlamaIndex agent real control over a Route4me account through Composio's Route4me MCP server.

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

Also integrate Route4me with

OpenAI Agents SDK Claude Agent SDK Claude Code Claude Cowork Codex OpenClaw Hermes CLI Google ADK LangChain Vercel AI SDK Mastra AI CrewAI

TL;DR

Here's what you'll learn:

Set your OpenAI and Composio API keys
Install LlamaIndex and Composio packages
Create a Composio Tool Router session for Route4me
Connect LlamaIndex to the Route4me MCP server
Build a Route4me-powered agent using LlamaIndex
Interact with Route4me through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

ReAct Agent: Reasoning and acting pattern for tool-using agents
MCP Tools: Native support for Model Context Protocol
Context Management: Maintain conversation context across interactions
Async Support: Built for async/await patterns

What is the Route4me MCP server, and what's possible with it?

The Route4me MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Route4me account. It provides structured and secure access to your fleet and route data, so your agent can perform actions like listing vehicles, retrieving asset details, updating destination statuses, and streamlining last-mile logistics on your behalf.

Full vehicle inventory retrieval: Instantly ask your agent to pull a complete list of all vehicles in your organization for planning and operational audits.
Vehicle data access for route planning: Get detailed information on each vehicle—including capacity and assignment details—to optimize delivery routes.
Automated destination status updates: Let your agent mark destinations as completed, skipped, or failed after deliveries or stops, keeping your records accurate in real time.
Streamlined delivery confirmation workflows: Have your agent confirm delivery outcomes automatically, ensuring your route progress is always up to date for dispatchers and drivers.

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:

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

Step-by-step Guide

Step by step10 STEPS

Prerequisites

Before you begin, make sure you have:

Python 3.8/Node 16 or higher installed
A Composio account with the API key
An OpenAI API key
A Route4me account and project
Basic familiarity with async Python/Typescript

Getting API Keys for OpenAI, Composio, and Route4me

OpenAI API key (OPENAI_API_KEY)

Go to the OpenAI dashboard
Create an API key if you don't have one
Assign it to OPENAI_API_KEY in .env

Composio API key and user ID

Log into the Composio dashboard
Copy your API key from Settings
- Use this as COMPOSIO_API_KEY
Pick a stable user identifier (email or ID)
- Use this as COMPOSIO_USER_ID

Installing dependencies

npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv

Create a new Typescript project and install the necessary dependencies:

@composio/llamaindex: Composio's LlamaIndex integration
@llamaindex/openai: OpenAI LLM integration
@llamaindex/tools: MCP client for LlamaIndex
@llamaindex/workflow: Workflow framework for LlamaIndex
dotenv: Environment variable management

Set environment variables

bash

OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

Authenticate with OpenAI's GPT-5 model
Connect to Composio's Tool Router
Identify your Composio user session for Route4me access

Import modules

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

Create a new file called route4me_llamaindex_agent.ts and import the required modules:

Key imports:

dotenv.config loads .env at runtime
readline gives us a simple CLI chat loop
Composio is the main Composio SDK client
mcp connects to an MCP endpoint
createAgent builds a LlamaIndex agent
openai configures the LLM backend

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!COMPOSIO_API_KEY) throw new Error("COMPOSIO_API_KEY is not set");
if (!COMPOSIO_USER_ID) throw new Error("COMPOSIO_USER_ID is not set");

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

Create a Tool Router session and build the agent function

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["route4me"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Route4me actions." ,
    llm,
    tools,
  });

  return agent;
}

What's happening here:

We create a Composio client using your API key and configure it with the LlamaIndex provider
We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, route4me)
The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
LlamaIndex will connect to this endpoint to dynamically discover and use the available Route4me tools.
The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.

Create an interactive chat loop

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

We're creating a direct terminal interface to chat with Route4me
The LLM's responses are streamed to the CLI for faster interaction.
The agent uses context to maintain conversation history
The agent processes the request, selects appropriate Route4me tools, and returns a result
We extract the answer from the result data structure and display it to the user
You can type 'quit' or 'exit' to stop the chat loop gracefully
Agent responses and any errors are streamed in a clear, readable format

Define the main entry point

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();

What's happening here:

We're orchestrating the entire application flow
The agent gets built with proper error handling
Then we kick off the interactive chat loop so you can start talking to Route4me

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Route4me, then start asking questions.

Complete Code

Here's the complete code to get you started with Route4me and LlamaIndex:

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["route4me"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Route4me actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();

Conclusion

You've successfully connected Route4me to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:

Tool Router dynamically exposes Route4me tools through an MCP endpoint
LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
The agent becomes more capable without increasing prompt size
Async Python provides clean, efficient execution of agent workflows

You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.

TOOLS

Supported Tools

Every Route4me action and event your agent gets out of the box.

Add Order Custom Field

Tool to add a new custom field definition for orders.

Add Route Note

Tool to add a note to a route or address destination.

Create Address

Tool to add a new address to the address book.

Create Avoidance Zone

Tool to create an avoidance zone with circular, rectangular, or polygon shape.

Create Location Type

Tool to create a new location type in the address book.

Create Master Route

Tool to create a new master route in Route4Me.

Create Custom Note Type

Tool to create a new custom note type in Route4me.

Create Route Optimization

Tool to create a new route optimization in Route4Me.

Create Optimization Profile

Tool to create a new optimization profile in Route4Me.

Create Order Custom Field

Tool to create a new custom field definition for orders.

Create Orders from Contacts

Tool to create orders from address book contacts.

Create Territory

Tool to create a new territory with circular, rectangular, or polygon shape.

Create Vehicle Capacity Profile

Tool to create a vehicle capacity profile with weight, volume, item count, and revenue limits.

Delete Address from Route

Tool to delete an address from a route.

Delete Addresses

Tool to delete addresses from the Route4Me address book.

Delete Avoidance Zone

Tool to delete an avoidance zone by territory_id.

Delete Configuration Setting

Tool to delete a member configuration setting by config_key.

Delete Current User

Tool to delete the current authenticated user account.

Delete Location Type

Tool to delete a location type from the address book.

Delete Optimization

Tool to remove optimization problems from the Route4Me database.

Delete Optimization Profile

Tool to delete an optimization profile by ID.

Delete Order Custom Field

Tool to delete an order custom field by ID.

Delete Route V4

Tool to delete one or more routes by route_id.

Delete Territory

Tool to delete a territory by territory_id.

Delete Vehicle Capacity Profile by ID

Tool to delete a vehicle capacity profile by ID.

Dispatch Routes

Tool to approve or revoke routes for execution in Route4Me.

Display Datatable Config

Tool to retrieve datatable configuration for vehicle capacity profiles.

Duplicate Routes

Tool to duplicate one or more existing routes.

Find Address

Tool to retrieve detailed information about a specific address from the Route4Me address book.

Geocode Address

Tool to geocode an address and obtain its coordinates.

Geocode Address (Body)

Tool to geocode an address by sending a body payload with the address and options.

Bulk Geocode Addresses

Tool to geocode multiple addresses in a single request.

Geocode Address Forward

Tool to convert an address to geographic coordinates using forward geocoding.

Get Activity Feed

Tool to retrieve activities from the Route4Me activity feed with optional filtering and pagination.

Get Address

Tool to get address/destination information from a route.

Get Address Book Groups

Tool to retrieve address book groups from Route4Me.

Get Addresses from Address Book

Tool to retrieve addresses from the Route4Me address book.

Get Async Export Tracking History

Tool to save tracking history file via async export.

Get All Territories (Avoidance Zones v5)

Tool to retrieve all avoidance zones (territories) using API v5.

Get Avoidance Zone By ID

Tool to retrieve a specific avoidance zone by its territory ID.

Get Clustered Locations

Tool to retrieve locations grouped by geographic proximity using geohash clustering.

Get Current Member Information

Tool to retrieve the current authenticated member's information.

Get Activity Feed

Tool to retrieve all activities from the Route4Me activity feed.

Get Last Scheduled Route for Member

Tool to retrieve the most recently scheduled route for a specific member as of today.

Get Location Heatmap

Tool to retrieve a heat map of location clusters from the address book.

Get Location Service-Time Heatmap

Tool to retrieve location service-time heatmap data for address book locations.

Get Location Type

Tool to get location type details by ID.

Get Member Configuration Settings

Tool to get member configuration settings with optional filtering.

Get Note Custom Types

Tool to retrieve all custom note types configured for the account.

Get Optimization Profile

Tool to retrieve detailed information about an optimization profile by its unique identifier.

Get Route Destination By ID

Tool to get a route address/destination by its ID.

Get Route Info

Tool to get detailed route information by route ID.

Get Route List

Tool to retrieve a list of routes with filtering and pagination.

Get Route Settings

Tool to get route settings with detailed information including waypoints, optimization settings, and delivery details.

Get Territories with Location Counts

Tool to retrieve territories with location counts for geographic analysis.

Get Territory

Tool to retrieve territory information by ID or get all territories.

Submit Device Tracking Data

Tool to submit device GPS tracking information to Route4Me.

Get Tracking History Export

Tool to export tracking history file from Route4Me.

Get User By ID

Tool to retrieve a sub-user by their unique ID.

Get User Locations

Tool to view locations of all users/drivers in real-time.

Get User Modification History

Tool to get user modification history from Route4Me.

Get User Template

Tool to retrieve the template of a sub-user with detailed information including contact information, preferences, and account status.

Get User Information (v4)

Tool to retrieve authenticated user information in v4 format.

Get Vehicles

Tool to retrieve details of vehicles in the organization.

Get Vehicle Capacity Profile As Datatable

Tool to retrieve vehicle capacity profiles in datatable format with pagination.

Get Vehicle Capacity Profile by ID

Tool to retrieve a specific vehicle capacity profile by its ID.

Get Vehicle Capacity Profile Page Config

Tool to retrieve vehicle capacity profile page configuration including unit settings.

Get Vehicle Capacity Profiles

Tool to retrieve vehicle capacity profiles with weight, volume, and item constraints.

List Location Types

Tool to retrieve location type definitions used in the address book system.

List Optimization Profiles

Tool to retrieve optimization profiles with settings and configuration details.

List Optimizations

Tool to get a list of all optimizations or retrieve a single optimization by ID.

List Order Custom Fields

Tool to retrieve all order custom field definitions from Route4Me v5.

List Route Directions

Tool to get detailed route directions including turn-by-turn navigation information for each stop.

List Team Users

Tool to get the list of team members/users in the account.

List Users By IDs

Tool to retrieve detailed information about team members by their member IDs.

List Team Users (Paginated)

Tool to get a paginated list of team members/users in the account.

Lookup For New Destination

Tool to lookup optimal routes for inserting a new destination.

Merge Routes

Tool to merge multiple routes into a single target route.

Move Route Destination

Tool to move a destination from one route to another.

Preview Route Assignment

Tool to generate a preview of route assignments based on filters, grouping, sorting, and assignment strategy without applying changes.

Re-run Optimization

Tool to re-optimize an existing optimization problem by updating route parameters and/or addresses.

Reverse Geocode Address

Tool to reverse geocode coordinates to obtain an address.

Set Destination Status

Tool to set or update the status of a route destination.

Set Route Rating

Tool to set a rating for a route.

Set Route Tracking Data

Tool to insert tracking data for a route.

Update Address

Tool to update an existing address in the Route4Me address book.

Update Avoidance Zone

Tool to update an existing avoidance zone.

Update Location Type

Tool to update an existing location type in the address book.

Update Member Configuration Setting

Tool to update a member configuration setting.

Update Custom Note Type

Tool to update an existing custom note type in Route4Me.

Update Optimization Profile

Tool to update an existing optimization profile.

Update Order Custom Field

Tool to update an existing order custom field in Route4Me.

Update Routes

Tool to bulk update multiple routes in a single operation.

Update Route Settings

Tool to update route settings including optimization parameters, distance units, and device types.

Update Route V4

Tool to update route parameters and addresses in Route4Me.

Update Territory

Tool to update an existing territory.

Update Vehicle Capacity Profile By ID

Tool to update an existing vehicle capacity profile by ID.

FRAMEWORKS

How to build Route4me MCP Agent with another framework

OpenAI Agents SDK

Use Route4me MCP with OpenAI Agents SDK

Claude Agent SDK

Use Route4me MCP with Claude Agent SDK

Claude Code

Use Route4me MCP with Claude Code

Claude Cowork

Use Route4me MCP with Claude Cowork

Codex

Use Route4me MCP with Codex

OpenClaw

Use Route4me MCP with OpenClaw

Hermes

Use Route4me MCP with Hermes

CLI

Use Route4me MCP with CLI

Google ADK

Use Route4me MCP with Google ADK

LangChain

Use Route4me MCP with LangChain

Vercel AI SDK

Use Route4me MCP with Vercel AI SDK

Mastra AI

Use Route4me MCP with Mastra AI

CrewAI

Use Route4me MCP with CrewAI

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

Apilio

Api KeyBasic

Apilio is a home automation platform that lets you connect and control smart devices from different brands. It helps you build flexible automations with complex conditions, schedules, and integrations.

Basin

Api Key

Basin is a no-code form backend for quickly setting up reliable contact forms. It lets you collect and manage form submissions without writing any server-side code.

Bouncer

Api Key

Bouncer is an email validation platform that verifies the authenticity of email addresses in real-time and batch. It helps boost deliverability and reduce bounce rates for your communications.

Conveyor

Api Key

Conveyor is a platform that automates security reviews with a Trust Center and AI-driven questionnaire automation. It streamlines compliance and vendor security processes for faster, hassle-free reviews.

FAQ

Frequently asked questions

With a standalone Route4me MCP server, the agents and LLMs can only access a fixed set of Route4me tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Route4me and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. LlamaIndex 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 Route4me tools.

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

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 Route4me data and credentials are handled as safely as possible.

Start with Route4me.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Route4me tool your agent needs.Free to start.

Start building

Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREE BOOK A DEMO

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati

Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya

Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave

CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu

Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola

Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche

Co-Founder, Ingram Technologies

How to integrate Route4me MCP with LlamaIndex

Connect Route4me without auth hassles

Introduction

Also integrate Route4me with

TL;DR

What is LlamaIndex?

What is the Route4me MCP server, and what's possible with it?

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

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI, Composio, and Route4me

Installing dependencies

Set environment variables

Import modules

Load environment variables and initialize Composio

Create a Tool Router session and build the agent function

Create an interactive chat loop

Define the main entry point

Run the agent

Complete Code

Conclusion

Supported Tools

How to build Route4me MCP Agent with another framework

OpenAI Agents SDK

Claude Agent SDK

Claude Code

Claude Cowork

Codex

OpenClaw

Hermes

CLI

Google ADK

LangChain

Vercel AI SDK

Mastra AI

CrewAI

Explore Other Toolkits

Apilio

Basin

Bouncer

Conveyor

Frequently asked questions

What are the differences in Tool Router MCP and Route4me MCP?+

Can I use Tool Router MCP with LlamaIndex?+

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

How safe is my data with Composio Tool Router?+

Start with Route4me.It takes 30 seconds.

Teams ship real agents on Composio