How to integrate Booqable MCP with LlamaIndex

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

30 min · no commitment · see it on your stack

Booqable logo
LlamaIndex logo
divider

Introduction

This guide walks you through connecting Booqable to LlamaIndex using the Composio tool router. By the end, you'll have a working Booqable agent that can add a new customer named alice brown, list all active orders for this week, create a rental order for customer id 123 through natural language commands.

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

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

Also integrate Booqable with

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

The Booqable MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Booqable account. It provides structured and secure access to your rental management system, so your agent can perform actions like creating customers, managing orders, retrieving inventory data, and organizing product groups on your behalf.

  • Customer management and onboarding: Effortlessly create new customers, fetch details for existing clients, or delete customer records when needed—all through your AI agent.
  • Order creation and tracking: Let your agent generate new rental orders, retrieve specific order details, or list and filter all existing orders based on your business needs.
  • Inventory and product group organization: Have your agent create new product groups to organize inventory, fetch product group information, or remove groups that are no longer needed.
  • Automated cleanup and archiving: Direct your agent to archive customers or orders, helping you keep your database clean and up-to-date without manual intervention.

Supported Tools & Triggers

Tools
Create CustomerTool to create a new customer.
Create OrderTool to create a new order.
Create Product GroupTool to create a new product group in Booqable.
Delete CustomerTool to delete (archive) a customer by ID.
Delete OrderTool to delete (archive) an order by ID.
Delete Product GroupTool to delete a product group by ID.
Get CustomerTool to fetch a specific customer by ID.
Get CustomersTool to retrieve a list of customers.
Get Inventory LevelsTool to fetch inventory levels for products.
Get New OrderTool to retrieve a new order template with default values.
Get OrderTool to retrieve a specific order by ID.
Get ProductTool to fetch a specific product by ID.
Get Product GroupTool to fetch a specific product group by ID.
List BarcodesTool to retrieve a list of barcodes.
List Bundle ItemsTool to retrieve a list of bundle items.
List ClustersTool to retrieve a list of clusters from Booqable.
List CouponsTool to retrieve a list of coupons.
List Default PropertiesTool to retrieve a list of default properties from Booqable.
List DocumentsTool to retrieve a list of documents.
List Email TemplatesTool to list email templates from Booqable.
List EmployeesTool to retrieve a list of employees from Booqable.
List Inventory BreakdownsTool to retrieve a list of inventory breakdowns filtered by status and product/product group.
List ItemsTool to retrieve a list of items (products and product groups).
List LinesTool to retrieve a paginated list of lines from orders.
List LocationsTool to retrieve a list of locations from Booqable.
List NotesTool to retrieve a list of notes.
List OrdersTool to retrieve a paginated list of orders.
List Payment MethodsTool to retrieve a list of payment methods from Booqable.
List PaymentsTool to list all payments from Booqable.
List PhotosTool to retrieve a paginated list of photos from Booqable.
List PlanningsTool to retrieve planning records that track product and bundle reservations across locations and time periods.
List Price RulesetsTool to list price rulesets.
List Price StructuresTool to list price structures.
List Product GroupsTool to list product groups from Booqable API v4.
List ProductsTool to retrieve a list of products.
List PropertiesTool to retrieve a list of properties.
List ProvincesTool to retrieve a list of provinces.
List Stock Item PlanningsTool to retrieve a list of stock item plannings.
List Stock ItemsTool to retrieve a list of stock items.
List Tax RatesTool to retrieve a list of tax rates.
List Tax ValuesTool to retrieve a list of tax values.
List UsersTool to retrieve a list of users from Booqable.
Search BundlesTool to search bundles with advanced filtering.
Search CustomersTool to search customers in the Booqable system.
Search DocumentsTool to search documents using advanced filtering with logical operators.
Search ItemsTool to search items (products and bundles) with advanced filtering.
Search OrdersTool to search orders with advanced filtering using logical operators.
Search PlanningsTool to search plannings with advanced filtering.
Update CompanyTool to update the current company's information in Booqable.

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

Getting API Keys for OpenAI, Composio, and Booqable

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 Booqable 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 booqable_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=["booqable"],
    )

    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 Booqable actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Booqable 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, booqable)
  • 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 Booqable 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 Booqable 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 Booqable

Run the agent

npx ts-node llamaindex-agent.ts

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

Complete Code

Here's the complete code to get you started with Booqable 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=["booqable"],
    )

    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 Booqable actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Booqable 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 Booqable to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Booqable 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 Booqable MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Booqable MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Booqable MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Booqable MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Booqable MCP with Claude Cowork

Codex logo

Codex

Use Booqable MCP with Codex

OpenClaw logo

OpenClaw

Use Booqable MCP with OpenClaw

Hermes logo

Hermes

Use Booqable MCP with Hermes

CLI logo

CLI

Use Booqable MCP with CLI

Google ADK logo

Google ADK

Use Booqable MCP with Google ADK

LangChain logo

LangChain

Use Booqable MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Booqable MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Booqable MCP with Mastra AI

CrewAI logo

CrewAI

Use Booqable MCP with CrewAI

FAQ

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

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

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

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