How to integrate Honeyhive MCP with LlamaIndex

This guide walks you through connecting Honeyhive to LlamaIndex using the Composio tool router. By the end, you'll have a working Honeyhive agent that can add new datapoints to your evaluation dataset, list all datasets in your honeyhive project, log a batch of model events for analysis through natural language commands. This guide will help you understand how to give your LlamaIndex agent real control over a Honeyhive account through Composio's Honeyhive MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Honeyhive logoHoneyhive
Api Key

Honeyhive is an AI observability and evaluation platform for analyzing LLM apps. It helps teams monitor, debug, and improve AI system reliability faster.

42 Tools

Introduction

This guide walks you through connecting Honeyhive to LlamaIndex using the Composio tool router. By the end, you'll have a working Honeyhive agent that can add new datapoints to your evaluation dataset, list all datasets in your honeyhive project, log a batch of model events for analysis through natural language commands.

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

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

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

The Honeyhive MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Honeyhive account. It provides structured and secure access to your AI observability platform, so your agent can perform actions like managing datasets, logging model and tool events, evaluating runs, and configuring project settings on your behalf.

  • Dataset management and organization: Create, retrieve, and delete datasets for your AI projects, helping you maintain organized and up-to-date evaluation data.
  • Efficient event logging: Log batches of model or external tool events, enabling comprehensive tracking and analysis of AI system interactions in real-time.
  • Data curation and cleanup: Add new datapoints to datasets or remove specific datapoints, ensuring your evaluation data remains accurate and relevant.
  • Streamlined evaluation workflows: Mark evaluation runs as completed and fetch project configuration details, making it easy to track progress and update run statuses automatically.

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

Step by step10 STEPS
1

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

Getting API Keys for OpenAI, Composio, and Honeyhive

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
3

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
4

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 Honeyhive access
5

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 honeyhive_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
6

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.

7

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: ["honeyhive"],
    },
  );

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

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 Honeyhive
  • 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 Honeyhive 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
9

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 Honeyhive
10

Run the agent

npx ts-node llamaindex-agent.ts

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

Complete Code

Here's the complete code to get you started with Honeyhive 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: ["honeyhive"],
    },
  );

  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 Honeyhive 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 Honeyhive to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Honeyhive 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 Honeyhive action and event your agent gets out of the box.

Add datapoints to dataset

Tool to add datapoints to a dataset.

Compare Experiment Runs

Tool to retrieve experiment comparison between two evaluation runs.

Compare Runs Events

Tool to compare events between two experiment runs side-by-side.

Batch Create Datapoints

Tool to create multiple datapoints in a single batch operation.

Create Batch Model Events

Tool to create multiple model events in a single request.

Create Batch Tool Events

Tool to log a batch of external API calls as tool events.

Create Configuration

Creates a new configuration in HoneyHive for managing LLM or pipeline settings.

Create Datapoint

Tool to create a new datapoint with input-output pairs.

Create Dataset

Tool to create a dataset.

Create Event

Tool to create a new event in HoneyHive to track execution of different parts of your application.

Create Metric

Tool to create a new metric in HoneyHive.

Create Model Event

Tool to create a new model event to log LLM call data.

Create Tool

Creates a new tool definition in a HoneyHive project.

Delete Datapoint

Tool to delete a specific datapoint by its ID.

Delete Dataset

Tool to delete a dataset by ID.

End Evaluation Run

Tool to update an evaluation run's status and metadata.

Get Configurations

Tool to retrieve a list of configurations.

Get Datasets

Retrieve datasets from HoneyHive for a specified project.

Get Events

Tool to query events with filters and projections from HoneyHive.

Get Events By Session ID

Tool to retrieve the complete tree of nested events for a specific session.

Get Events Chart

Tool to retrieve charting and analytics data for events over time.

Get Metrics

Retrieves all metrics associated with a HoneyHive project.

Get Projects

Tool to retrieve all projects in the HoneyHive account.

Get Evaluation Run Details

Tool to get details of an evaluation run by its UUID.

Get Run Metrics

Tool to get event metrics for an experiment run.

Get Evaluation Runs

Tool to retrieve a list of evaluation runs from HoneyHive.

Get Runs Schema

Tool to retrieve the schema for experiment runs in HoneyHive.

Get Session

Retrieve a complete session tree by session ID from HoneyHive.

List Tools

Tool to list all available Honeyhive tools.

Retrieve Datapoint

Retrieve a specific datapoint by its ID from HoneyHive.

Retrieve Datapoints

Retrieve datapoints from a HoneyHive project.

Retrieve Events

Retrieve and export events from a HoneyHive project.

Retrieve Experiment Result

Tool to retrieve the result of a specific experiment run.

Start Evaluation Run

Creates a new evaluation run to group and track multiple session events for analysis.

Start Session

Start a new HoneyHive session for tracing and observability.

Update Configuration

Tool to update an existing HoneyHive configuration.

Update Datapoint

Update an existing datapoint by ID.

Update Dataset

Tool to update an existing dataset.

Update Event

Update an existing HoneyHive event by ID.

Update Metric

Tool to update an existing metric.

Update Project

Updates an existing HoneyHive project's name or description.

Update Tool

Tool to update an existing tool in HoneyHive.

FAQ

Frequently asked questions

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

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

Start with Honeyhive.It takes 30 seconds.

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

Start building