How to integrate Algolia MCP with Google ADK

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Algolia Logo
Google ADK Logo
divider

Introduction

This guide walks you through connecting Algolia to Google ADK 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 Google ADK 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:
  • Get a Algolia account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Algolia
  • Build an agent that connects to Algolia through MCP
  • Interact with Algolia using natural language

What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.

Key features include:

  • Gemini Integration: Native support for Google's Gemini models
  • MCP Toolset: Built-in support for Model Context Protocol tools
  • Streamable HTTP: Connect to external services through streamable HTTP
  • CLI and Web UI: Run agents via command line or web interface

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:
  • A Google API key for Gemini models
  • A Composio account and API key
  • Python 3.9 or later installed
  • Basic familiarity with Python

Getting API Keys for Google and Composio

Google API Key
  • Go to Google AI Studio and create an API key.
  • Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
  • Log in to the Composio dashboard.
  • Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
  • Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.

Install dependencies

bash
pip install google-adk composio python-dotenv

Inside your virtual environment, install the required packages.

What's happening:

  • google-adk is Google's Agents Development Kit
  • composio connects your agent to Algolia via MCP
  • python-dotenv loads environment variables

Set up ADK project

bash
adk create my_agent

Set up a new Google ADK project.

What's happening:

  • This creates an agent folder with a root agent file and .env file

Set environment variables

bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email

Save all your credentials in the .env file.

What's happening:

  • GOOGLE_API_KEY authenticates with Google's Gemini models
  • COMPOSIO_API_KEY authenticates with Composio
  • COMPOSIO_USER_ID identifies the user for session management

Import modules and validate environment

python
import os
import warnings

from composio import Composio
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

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

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_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:
  • os reads environment variables
  • Composio is the main Composio SDK client
  • GoogleProvider declares that you are using Google ADK as the agent runtime
  • Agent is the Google ADK LLM agent class
  • McpToolset lets the ADK agent call MCP tools over HTTP

Create Composio client and Tool Router session

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["algolia"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
What's happening:
  • Authenticates to Composio with your API key
  • Declares Google ADK as the provider
  • Spins up a short-lived MCP endpoint for your user and selected toolkit
  • Stores the MCP HTTP URL for the ADK MCP integration

Set up the McpToolset and create the Agent

python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Algolia operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
What's happening:
  • Connects the ADK agent to the Composio MCP endpoint through McpToolset
  • Uses Gemini as the model powering the agent
  • Lists exact tool names in instruction to reduce misnamed tool calls

Run the agent

bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web

Execute the agent from the project root. The web command opens a web portal where you can chat with the agent.

What's happening:

  • adk run runs the agent in CLI mode
  • adk web . opens a web UI for interactive testing

Complete Code

Here's the complete code to get you started with Algolia and Google ADK:

import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()
warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

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

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_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.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["algolia"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Algolia operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")

Conclusion

You've successfully integrated Algolia with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Algolia using natural language commands.

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Algolia tools
  • Environment variables keep your credentials secure and separate from code
  • Clear agent instructions reduce tool calling errors
  • The ADK web UI provides an interactive interface for testing and development

You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

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

LangChain

LangChain

Use Algolia MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Algolia MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Algolia MCP with Mastra AI

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 Google ADK?

Yes, you can. Google ADK 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