How to integrate Algolia MCP with Mastra AI

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Algolia Logo
Mastra AI Logo
divider

Introduction

This guide walks you through connecting Algolia to Mastra AI using the Composio tool router. By the end, you'll have a working Algolia agent that can export all records from products index, clear all objects from blog_posts index, copy index settings from staging to production, create an ab test comparing two search configs through natural language commands.

This guide will help you understand how to give your Mastra AI agent real control over a Algolia account through Composio's Algolia 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 up your environment so Mastra, OpenAI, and Composio work together
  • Create a Tool Router session in Composio that exposes Algolia tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Algolia tool definitions and attach them as a toolset
  • Build a Mastra agent that can reason, call tools, and return structured results
  • Run an interactive CLI where you can chat with your Algolia agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

  • MCP Client: Built-in support for Model Context Protocol servers
  • Toolsets: Organize tools into logical groups
  • Step Callbacks: Monitor and debug agent execution
  • OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

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

The Algolia MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Algolia account. It provides structured and secure access to your search indices, so your agent can perform actions like browsing records, managing index settings, running A/B tests, copying configurations, and tracking search events on your behalf.

  • Comprehensive index browsing and export: Easily direct your agent to retrieve and iterate through all records in any Algolia index for analysis, backup, or migration tasks.
  • Automated A/B test management: Set up, launch, and monitor A/B tests to compare search performance between different index variants or configurations—all without manual coding.
  • Index and rule duplication: Quickly copy entire indices, settings, or query rules from one index to another, streamlining your search deployment and versioning workflows.
  • Bulk index cleanup and resets: Instruct your agent to clear all objects or rules in an index while keeping configurations intact, letting you efficiently manage large data updates or reindexing processes.
  • Real-time event tracking: Capture user interactions like clicks and conversions, enabling your agent to report search analytics and optimize relevance based on actual user behavior.

Supported Tools & Triggers

Tools
Add AB TestTool to create an ab test comparing search performance between two variants.
Browse Algolia IndexTool to retrieve all records from an index.
Clear ObjectsTool to clear records of an index without affecting settings.
Clear RulesTool to delete all rules in an index.
Clicked Object IDsTool to send a click event to algolia to capture clicked items.
Clicked Object IDs After SearchTool to send a click event after a search response.
Converted Object IDsTool to send a conversion event for items outside of search context.
Copy IndexTool to copy the specified index to a new index.
Copy RulesTool to copy rules from one index to another.
Copy Index SettingsTool to copy the settings from one index to another.
Delete IndexTool to delete the specified index and all its records.
Delete Multiple RecordsTool to delete multiple records from an algolia index.
Delete RuleTool to delete the specified rule from an index.
Delete SynonymTool to delete a synonym from a specified index.
Export RulesTool to export all rules defined on an index.
Find ObjectTool to find the first object matching a query or filter in an index.
Get Object PositionTool to retrieve an object’s position in a result set.
Get multiple objectsTool to retrieve multiple records from an index.
Get Index SettingsTool to retrieve the settings of a specified index.
Index ExistsTool to check if an algolia index exists.
Init Insights API ClientTool to initialize the algolia insights api client.
List IndicesTool to list all indices and their metadata.
Partial Update ObjectsTool to partially update multiple records in the specified index.
Replace All RulesTool to push a new set of rules, erasing previous ones.
Save SynonymTool to add or update a synonym in the specified index.
Search Algolia IndexTool to perform a search on a specified algolia index.
Search Multiple IndicesTool to perform searches across multiple indices in a single call.
Search RulesTool to search for rules in the specified index.
Search SynonymsTool to search for synonyms in the specified index.
Set Index SettingsTool to update an algolia index's settings.

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:

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

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Node.js 18 or higher
  • A Composio account with an active API key
  • An OpenAI API key
  • Basic familiarity with TypeScript

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key.
  • You need credits or a connected billing setup to use the models.
  • Store the key somewhere safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Go to Settings and copy your API key.
  • This key lets your Mastra agent talk to Composio and reach Algolia through MCP.

Install dependencies

bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

  • @composio/core is the Composio SDK for creating MCP sessions
  • @mastra/core provides the Agent class
  • @mastra/mcp is Mastra's MCP client
  • @ai-sdk/openai is the model wrapper for OpenAI
  • dotenv loads environment variables from .env

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio
  • COMPOSIO_USER_ID tells Composio which user this session belongs to
  • OPENAI_API_KEY lets the Mastra agent call OpenAI models

Import libraries and validate environment

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

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

const composio = new Composio({
  apiKey: composioAPIKey as string,
});
What's happening:
  • dotenv/config auto loads your .env so process.env.* is available
  • openai gives you a Mastra compatible model wrapper
  • Agent is the Mastra agent that will call tools and produce answers
  • MCPClient connects Mastra to your Composio MCP server
  • Composio is used to create a Tool Router session

Create a Tool Router session for Algolia

typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["algolia"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Algolia MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "algolia" for Algolia access
  • session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

Configure Mastra MCP client and fetch tools

typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
What's happening:
  • MCPClient takes an id for this client and a list of MCP servers
  • The headers property includes the x-api-key for authentication
  • getTools fetches the tool definitions exposed by the Algolia toolkit

Create the Mastra agent

typescript
const agent = new Agent({
    name: "algolia-mastra-agent",
    instructions: "You are an AI agent with Algolia tools via Composio.",
    model: "openai/gpt-5",
  });
What's happening:
  • Agent is the core Mastra agent
  • name is just an identifier for logging and debugging
  • instructions guide the agent to use tools instead of only answering in natural language
  • model uses openai("gpt-5") to configure the underlying LLM

Set up interactive chat interface

typescript
let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\n");

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        algolia: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
What's happening:
  • messages keeps the full conversation history in Mastra's expected format
  • agent.generate runs the agent with conversation history and Algolia toolsets
  • maxSteps limits how many tool calls the agent can take in a single run
  • onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

Here's the complete code to get you started with Algolia and Mastra AI:

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

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

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["algolia"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      algolia: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "algolia-mastra-agent",
    instructions: "You are an AI agent with Algolia tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { algolia: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Algolia through Composio's Tool Router. You can extend this further by:
  • Adding other toolkits like Gmail, Slack, or GitHub
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows

How to build Algolia MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Algolia MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Algolia MCP with Claude Agent SDK

Google ADK

Google ADK

Use Algolia MCP with Google ADK

LangChain

LangChain

Use Algolia MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Algolia MCP with Vercel AI SDK

LlamaIndex

LlamaIndex

Use Algolia MCP with LlamaIndex

CrewAI

CrewAI

Use Algolia MCP with CrewAI

FAQ

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

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

Can I use Tool Router MCP with Mastra AI?

Yes, you can. Mastra AI 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 Algolia tools.

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

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

Book a call↗Get started for free