Tave with LlamaIndex

How to integrate Tave MCP with LlamaIndex

Introduction TL;DR What is LlamaIndex What is the Tave MCP server Supported Tools & Triggers Creating MCP Server - Stand-alone vs Tool Router Step-by-step Guide Complete Code Conclusion How to build Tave MCP Agent with another framework Explore Other Toolkits FAQ

Connect Tave without Auth hassles

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

Try for Free

Introduction

This guide walks you through connecting Tave to LlamaIndex using the Composio tool router. By the end, you'll have a working Tave agent that can list all open jobs assigned to me, add a new client to tave contacts, update status of a job to 'completed' through natural language commands.

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

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

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 Tave
Connect LlamaIndex to the Tave MCP server
Build a Tave-powered agent using LlamaIndex
Interact with Tave 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 Tave MCP server, and what's possible with it?

The Tave MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Tave account. It provides structured and secure access so your agent can perform Tave operations on your behalf.

Supported Tools & Triggers

Tools

Apply Payment to OrderTool to apply a payment to a specific order in Tave.

Create BrandTool to create a new brand in VSCO Workspace.

Create Custom FieldTool to create a custom field in Tave for Jobs or Contacts.

Create Discount TypeTool to create a new discount type in Tave.

Create GalleryTool to create a new gallery in Tave (VSCO Workspace).

Create Address Book EntryTool to create an entry in the address book.

Create DiscountTool to create a discount in Tave.

Create EventTool to create a new event in Tave (VSCO Workspace).

Create Event TypeTool to create a new event type in Tave.

Create FileTool to create a file in Tave.

Create JobTool to create a new job in Tave (VSCO Workspace).

Create Job Closed ReasonTool to create a job closed reason in Tave.

Create Job ContactTool to create a job contact in Tave.

Create Job OrderTool to create an order on a job in Tave (VSCO Workspace).

Create Job RoleTool to create a job role in Tave (VSCO Workspace).

Create Job TypeTool to create a new job type in Tave.

Create Job WorksheetTool to create a job using a worksheet in Tave (VSCO Workspace).

Create Lead SourceTool to create a lead source in Tave.

Create Lead StatusTool to create a lead status in Tave.

Create NoteTool to create a note in Tave (VSCO Workspace).

Create PaymentTool to create a payment in Tave.

Create ProductTool to create a product in Tave.

Create Product TypeTool to create a product type in Tave.

Create Profit CenterTool to create a profit center in Tave.

Create RestHook SubscriptionTool to create a RestHook webhook subscription in Tave.

Create Tax RateTool to create a tax rate in Tave.

Create UserTool to create a new user in Tave.

Delete Address Book EntryTool to delete an entry in the address book.

Delete BrandTool to delete a brand by its ULID.

Delete Custom FieldTool to delete a custom field by its ULID identifier.

Delete Event TypeTool to delete an event type by its ULID identifier.

Delete GalleryTool to permanently delete a gallery by its ULID.

Delete DiscountTool to delete a specific discount by its ULID.

Delete Discount TypeTool to delete a specific discount type by its ULID.

Delete EventTool to delete an event by its ULID identifier.

Delete JobTool to delete a job by its ULID identifier.

Delete Job Closed ReasonTool to delete a job closed reason by its ULID identifier.

Delete Job ContactTool to delete a job contact by its ULID.

Delete Job RoleTool to delete a job role by its ULID identifier.

Delete Job TypeTool to delete a job type by its ULID.

Delete Lead SourceTool to delete a specific lead source by its ULID.

Delete Lead StatusTool to delete a specific lead status by its ULID.

Delete NoteTool to delete a note by its ULID identifier.

Delete PaymentTool to delete a specific payment by its ULID.

Delete ProductTool to delete a specific product by its ULID.

Delete Product TypeTool to delete a specific product type by its ULID.

Delete Profit CenterTool to delete a profit center by its ULID.

Delete RestHookTool to unsubscribe from and delete a RestHook webhook subscription by its ULID.

Delete Tax GroupTool to delete a specific tax group by its ULID.

Delete Tax RateTool to delete a specific tax rate by its ULID.

Delete UserTool to delete a user by its ULID.

Get BrandTool to retrieve a specific brand from Tave by its ULID.

Get EventTool to get a specific event by its ID.

Get Event TypeTool to retrieve a specific event type by ID.

Get GalleryTool to retrieve a specific gallery by ID from Tave/VSCO Workspace.

Get Address Book EntityTool to fetch a specific Address Book entity by its ULID.

Get Address Book AddressTool to fetch the address associated with a given location ID.

Get Custom FieldTool to fetch a specific custom field by ID from Tave.

Get DiscountTool to retrieve a specific discount by its ID.

Get Discount TypeTool to get a specific discount type by ID.

Get JobTool to fetch a specific job by ID from Tave.

Get Job Closed ReasonTool to retrieve a specific job closed reason by its ID.

Get Job ContactTool to fetch a specific job contact by ID from Tave.

Get Job RoleTool to retrieve a specific job role by its ID.

Get Job TypeTool to retrieve a specific job type by ID.

Get Job WorksheetTool to fetch a Job Worksheet for a specific job by job ID.

Get Lead SourceTool to retrieve a specific lead source by its ID.

Get Lead StatusTool to retrieve a specific lead status by its ID.

Get My StudioTool to retrieve information about your studio from Tave.

Get NoteTool to fetch a specific note by ID from Tave.

Get OrderTool to fetch a specific order by ID from Tave.

Get PaymentTool to fetch a specific payment by ID from Tave.

Get Payment MethodTool to retrieve a specific payment method by its ID.

Get ProductTool to retrieve a specific product by its ID.

Get Product TypeTool to retrieve a specific product type by its ID.

Get Profit CenterTool to retrieve a specific profit center by its ID.

Get Tax RateTool to retrieve a specific tax rate by its ULID.

Get TimezoneTool to retrieve a specific timezone by its ULID from Tave.

Get User by IDTool to retrieve a specific user by their ULID identifier.

List Address Book ContactsTool to list contacts in the studio's address book.

List BrandsTool to list brands of a studio.

List Discount TypesTool to get a list of discount types from Tave.

List Studio EventsTool to list a studio's events from Tave.

List Event TypesTool to list a studio's event types.

List FilesTool to list files in Tave.

List Resource Custom FieldsTool to list custom fields configured on a studio.

List Resource DiscountTool to get a list of discounts from Tave.

List GalleriesTool to list all galleries for a studio.

List Resource JobTool to list jobs of a studio.

List Job Closed ReasonsTool to list a studio's job closed reasons.

List Resource Job ContactTool to list a job's contacts.

List Resource Job OrdersTool to list orders on a given job.

List Job PaymentsTool to get a list of payments for a specific job.

List Job RolesTool to list a studio's job roles.

List Resource Job TypeTool to list job types of a studio.

List Resource Lead SourceTool to list lead sources of a studio.

List Resource Lead StatusTool to list lead statuses of a studio.

List Resource NoteTool to list notes from Tave.

List Resource OrderTool to get a list of all orders.

List Resource PaymentTool to get a list of payments from Tave.

List Resource Payment MethodTool to get a list of payment methods from Tave.

List Resource ProductTool to get a list of products from Tave.

List Product TypesTool to get a list of product types from Tave.

List Resource Profit CenterTool to list profit centers of a studio.

List REST HooksTool to list REST hooks configured in Tave.

List Resource Tax GroupsTool to get a list of Tax Groups from Tave.

List Resource Tax RatesTool to get a list of tax rates from Tave.

List Resource TimezoneTool to get a list of timezones from Tave.

List Resource UserTool to list users of a studio.

Update Address Book EntryTool to update a specific entry in the Tave address book.

Update BrandTool to update a specific brand in Tave.

Update Event TypeTool to update an existing event type in Tave.

Update Custom FieldTool to update a specific custom field in Tave.

Update EventTool to update a specific event in Tave.

Update GalleryTool to update a specific gallery in Tave (VSCO Workspace).

Update JobTool to update a specific job in Tave (VSCO Workspace).

Update Job Closed ReasonTool to update a job closed reason in Tave.

Update Job ContactTool to update a specific job contact in Tave.

Update Job RoleTool to update a job role in Tave.

Update Job TypeTool to update an existing job type in Tave.

Update Lead SourceTool to update a specific lead source in Tave.

Update Lead StatusTool to update a specific lead status in Tave.

Update NoteTool to update a specific note in Tave.

Update OrderTool to update a specific order in Tave (VSCO Workspace).

Update Profit CenterTool to update a specific profit center in Tave.

Update Tax GroupTool to update a specific tax group in Tave.

Update Tax RateTool to update a specific tax rate in Tave.

Update UserTool to update a specific user in Tave.

Update Studio Readonly ModeTool to set studio readonly mode in Tave.

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

What is Tool Router?

Composio's Tool Router 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 Tool Router

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

How the Tool Router works

The Tool Router 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

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 Tave account and project
Basic familiarity with async Python/Typescript

Getting API Keys for OpenAI, Composio, and Tave

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

pip install composio-llamaindex llama-index llama-index-llms-openai llama-index-tools-mcp python-dotenv

Create a new Python project and install the necessary dependencies:

composio-llamaindex: Composio's LlamaIndex integration
llama-index: Core LlamaIndex framework
llama-index-llms-openai: OpenAI LLM integration
llama-index-tools-mcp: MCP client for LlamaIndex
python-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 Tave access

Import modules

import asyncio
import os
import dotenv

from composio import Composio
from composio_llamaindex import LlamaIndexProvider
from llama_index.core.agent.workflow import ReActAgent
from llama_index.core.workflow import Context
from llama_index.llms.openai import OpenAI
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec

dotenv.load_dotenv()

Create a new file called tave_llamaindex_agent.py and import the required modules:

Key imports:

asyncio: For async/await support
Composio: Main client for Composio services
LlamaIndexProvider: Adapts Composio tools for LlamaIndex
ReActAgent: LlamaIndex's reasoning and action agent
BasicMCPClient: Connects to MCP endpoints
McpToolSpec: Converts MCP tools to LlamaIndex format

Load environment variables and initialize Composio

OPENAI_API_KEY = os.getenv("OPENAI_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not OPENAI_API_KEY:
    raise ValueError("OPENAI_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")

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 def build_agent() -> ReActAgent:
    composio_client = Composio(
        api_key=COMPOSIO_API_KEY,
        provider=LlamaIndexProvider(),
    )

    session = composio_client.create(
        user_id=COMPOSIO_USER_ID,
        toolkits=["tave"],
    )

    mcp_url = session.mcp.url
    print(f"Composio MCP URL: {mcp_url}")

    mcp_client = BasicMCPClient(mcp_url, headers={"x-api-key": COMPOSIO_API_KEY})
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    llm = OpenAI(model="gpt-5")

    description = "An agent that uses Composio Tool Router MCP tools to perform Tave actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Tave actions.
    """
    return ReActAgent(tools=tools, llm=llm, description=description, system_prompt=system_prompt, verbose=True)

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, tave)
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 Tave tools.
The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.

Create an interactive chat loop

async def chat_loop(agent: ReActAgent) -> None:
    ctx = Context(agent)
    print("Type 'quit', 'exit', or Ctrl+C to stop.")

    while True:
        try:
            user_input = input("\nYou: ").strip()
        except (KeyboardInterrupt, EOFError):
            print("\nBye!")
            break

        if not user_input or user_input.lower() in {"quit", "exit"}:
            print("Bye!")
            break

        try:
            print("Agent: ", end="", flush=True)
            handler = agent.run(user_input, ctx=ctx)

            async for event in handler.stream_events():
                # Stream token-by-token from LLM responses
                if hasattr(event, "delta") and event.delta:
                    print(event.delta, end="", flush=True)
                # Show tool calls as they happen
                elif hasattr(event, "tool_name"):
                    print(f"\n[Using tool: {event.tool_name}]", flush=True)

            # Get final response
            response = await handler
            print()  # Newline after streaming
        except KeyboardInterrupt:
            print("\n[Interrupted]")
            continue
        except Exception as e:
            print(f"\nError: {e}")

What's happening here:

We're creating a direct terminal interface to chat with your Tave database
The LLM's responses are streamed to the CLI for faster interaction.
The agent uses context to maintain conversation history
You can type 'quit' or 'exit' to stop the chat loop gracefully
Agent responses and any errors are displayed in a clear, readable format

Define the main entry point

async def main() -> None:
    agent = await build_agent()
    await chat_loop(agent)

if __name__ == "__main__":
    # Handle Ctrl+C gracefully
    signal.signal(signal.SIGINT, lambda s, f: (print("\nBye!"), exit(0)))
    try:
        asyncio.run(main())
    except KeyboardInterrupt:
        print("\nBye!")

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 Tave

Run the agent

npx ts-node llamaindex-agent.ts

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

Complete Code

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

import asyncio
import os
import signal
import dotenv

from composio import Composio
from composio_llamaindex import LlamaIndexProvider
from llama_index.core.agent.workflow import ReActAgent
from llama_index.core.workflow import Context
from llama_index.llms.openai import OpenAI
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec

dotenv.load_dotenv()

OPENAI_API_KEY = os.getenv("OPENAI_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not OPENAI_API_KEY:
    raise ValueError("OPENAI_API_KEY is not set")
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")

async def build_agent() -> ReActAgent:
    composio_client = Composio(
        api_key=COMPOSIO_API_KEY,
        provider=LlamaIndexProvider(),
    )

    session = composio_client.create(
        user_id=COMPOSIO_USER_ID,
        toolkits=["tave"],
    )

    mcp_url = session.mcp.url
    print(f"Composio MCP URL: {mcp_url}")

    mcp_client = BasicMCPClient(mcp_url, headers={"x-api-key": COMPOSIO_API_KEY})
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    llm = OpenAI(model="gpt-5")
    description = "An agent that uses Composio Tool Router MCP tools to perform Tave actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Tave actions.
    """
    return ReActAgent(
        tools=tools,
        llm=llm,
        description=description,
        system_prompt=system_prompt,
        verbose=True,
    );

async def chat_loop(agent: ReActAgent) -> None:
    ctx = Context(agent)
    print("Type 'quit', 'exit', or Ctrl+C to stop.")

    while True:
        try:
            user_input = input("\nYou: ").strip()
        except (KeyboardInterrupt, EOFError):
            print("\nBye!")
            break

        if not user_input or user_input.lower() in {"quit", "exit"}:
            print("Bye!")
            break

        try:
            print("Agent: ", end="", flush=True)
            handler = agent.run(user_input, ctx=ctx)

            async for event in handler.stream_events():
                # Stream token-by-token from LLM responses
                if hasattr(event, "delta") and event.delta:
                    print(event.delta, end="", flush=True)
                # Show tool calls as they happen
                elif hasattr(event, "tool_name"):
                    print(f"\n[Using tool: {event.tool_name}]", flush=True)

            # Get final response
            response = await handler
            print()  # Newline after streaming
        except KeyboardInterrupt:
            print("\n[Interrupted]")
            continue
        except Exception as e:
            print(f"\nError: {e}")

async def main() -> None:
    agent = await build_agent()
    await chat_loop(agent)

if __name__ == "__main__":
    # Handle Ctrl+C gracefully
    signal.signal(signal.SIGINT, lambda s, f: (print("\nBye!"), exit(0)))
    try:
        asyncio.run(main())
    except KeyboardInterrupt:
        print("\nBye!")

Conclusion

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

Tool Router dynamically exposes Tave 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.

How to build Tave MCP Agent with another framework

OpenAI Agents SDK

Use Tave MCP with OpenAI Agents SDK

Claude Agent SDK

Use Tave MCP with Claude Agent SDK

Google ADK

Use Tave MCP with Google ADK

LangChain

Use Tave MCP with LangChain

Vercel AI SDK

Use Tave MCP with Vercel AI SDK

Mastra AI

Use Tave MCP with Mastra AI

CrewAI

Use Tave MCP with CrewAI

Claude Code

Use Tave MCP with Claude Code

Codex

Use Tave MCP with Codex

Explore Other Toolkits

Addressfinder

Api Key

Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.

Agiled

API Key

Agiled is an all-in-one business management platform for CRM, projects, and finance. It helps you streamline workflows, consolidate client data, and manage business processes in one place.

Airtable

OAuth2Bearer TokenAPI Key

Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations.

TOOLKIT MARKETPLACE

FAQ

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

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

Can I use Tool Router MCP with LlamaIndex?

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 Tave tools.

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

Yes, absolutely. You can configure which Tave 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 Tave data and credentials are handled as safely as possible.

Used by agents from

Never worry about agent reliability

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

Book a call↗Get started for free

Harsha GaddipatiCo-founder, Slashy

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

Abhi AryaCo-founder, Opennote

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 has immensely helped in keeping new users on the platform.

Nirman DaveCEO, Zams

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

Ryan YuFounder, Extra Thursday

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

Tomisin JenrolaFounder & CEO, SwarmZero

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

Jerome LeclancheCo-Founder, Ingram Technologies

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.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

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.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

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.

How to integrate Tave MCP with LlamaIndex

Table of Contents

Connect Tave without Auth hassles

Introduction

TL;DR

What is LlamaIndex?

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

Supported Tools & Triggers

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

What is Tool Router?

How the Tool Router works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI, Composio, and Tave

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

How to build Tave MCP Agent with another framework

OpenAI Agents SDK

Claude Agent SDK

Google ADK

LangChain

Vercel AI SDK

Mastra AI

CrewAI

Claude Code

Codex

Explore Other Toolkits

Addressfinder

Agiled

Airtable

FAQ

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

Can I use Tool Router MCP with LlamaIndex?

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

How safe is my data with Composio Tool Router?

Used by agents from

Never worry about agent reliability