Artificial Intelligence
Algolia MCP connector
Connect Algolia to Elaichi and Claude, ChatGPT, Cursor, and any other MCP client can search your indices, browse records, tune settings and synonyms, and manage allowed sources, all as the person who signed in.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
57 tools
How to connect
How to connect Algolia to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Algolia once
-
Open Connections, choose Add connection, and pick Algolia.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an Algolia API key. One person generates a token in Algolia and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Algolia to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Algolia to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Algolia to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Algolia to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Algolia through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Engineering
Check an index before a release
Ask which indices exist, pull up the settings on one, and browse a sample of its records to confirm the latest push landed as expected.
-
Product
Find out why a search returns nothing
Run the exact query a customer typed against the live index, look at the facets that come back, and see whether a synonym or a setting is getting in the way.
-
Merchandising
Add a synonym so shoppers find it
When people search for "sneakers" and your catalog says "trainers", update the synonym in Algolia during the conversation instead of filing a ticket.
-
Support
Confirm a record made it into search
A customer says their listing is missing from results. Search the index for it, browse the records around it, and give them a straight answer in minutes.
-
Content
Push a batch of new records
Send a set of new articles or products into the right Algolia index in one go, then run a search to confirm they show up where they should.
-
IT
Review which sources are allowed
List the security sources Algolia currently accepts, spot the ones that belong to an old office or vendor, and remove them without opening the dashboard.
Try asking
- “Which Algolia indices gained the most records this week?”
- “List synonyms added to the products index this month.”
- “Show security sources allowed on the catalog index.”
AI tools
Algolia tools for your AI agents
57 tools are ready to call through Elaichi's MCP endpoint the moment you connect Algolia, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Algolia gets you
6 screens from the product, each doing one job for your Algolia account.
The agent
Ask about your Algolia indices in plain language.
Starter prompts return answers from live indices, records and security sources.
- indices
- records
- synonyms
- security sources
Ask Elaichi to work across your apps.
Which Algolia indices gained the most records this week?
List synonyms added to the products index this month.
Show security sources allowed on the catalog index.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Algolia together.
One org MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
57 Algolia tools arrive ready to call.
Indices, records, synonyms and security sources covered without writing custom code.
- List all Algolia security sources
- Delete a Algolia security source by ID
- Algolia security sources append
- Algolia security sources bulk update
ElaichiToolsToolboxes
Every team gets its own Algolia toolbox.
Search, commerce and support each work from a toolbox scoped to them.
- Search
- Commerce
- Content
- Support
ElaichiToolboxesShared connections
Teammates query Algolia without seeing an API key.
The connections table shows who connected each account and who shares it.
- Search Core
- Commerce EMEA
- Content
- Support
ElaichiConnectionsAudit log
Every Algolia index change is on record.
When, who, what happened, type and resource, appended and never edited.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires and Algolia work finishes.
Records are fetched, grouped, drafted into a digest, approved, then posted back.
Algolia digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch indices
Algolia
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Algolia
Queued
Collections and dashboards
Algolia index health is counted, not requested.
Four metrics, 14 days of records created, split by team, refreshed on schedule.
Algolia health
Refreshed 4 minutes ago · every 15 minutes · from the indices collection
Indices
1,284 ↓ 12%
Records
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Indices created
Last 14 days
By team
Share of activity
Search Core 34%
Commerce EMEA 27%
Content 21%
Support 18%
FAQ
Frequently asked questions
How do I connect Algolia to Claude?
First, connect Algolia in Elaichi by pasting an API key from your Algolia dashboard. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in as yourself and Algolia is ready to use.
Does Algolia work with ChatGPT and Cursor as well as Claude?
Yes. Once Algolia is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Algolia once and every client picks it up.
What can an AI agent actually do with my Algolia data?
With Algolia connected, an agent can list your indices, run a search or several at once, look through facets, browse the records in an index, and read or change index settings and synonyms. It can also add records in batches, clear or delete an index, and list, add, or remove the security sources Algolia accepts. Because Algolia has many capabilities, short concrete asks like "search the products index for red boots" work better than long instructions.
Does connecting Algolia give the AI access to every index and setting?
No. Access follows the Algolia API key and the person who signed in, so the agent can only reach the indices, records, and settings that key already allows. Elaichi can narrow that further, for example to search and browse only, but it can never grant more than Algolia itself grants.
Can I stop an agent from deleting or changing things in Algolia?
Yes. Restrictions in Elaichi apply per action, so you can allow searching and browsing in Algolia while blocking deleting an index, clearing records, or changing settings. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt can reach it.
What happens to an Algolia connection when someone leaves?
Offboarding a person in Elaichi ends their access to Algolia at once, across every client they used. A shared Algolia connection keeps working for everyone else on the team. If you disconnect Algolia in Elaichi, it is removed from Claude, ChatGPT, Cursor, and every other client in one step.
Put Algolia in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.