What did people search for on our site and fail to find last week?
Memtro reads your Algolia application's search analytics: top searches, searches with no results, the records returned most often and daily search volume. It lists your indices and reads an index's relevance settings, and runs a bounded search the way your site does. When asked and once an administrator has granted the action by name, it can save or update records, change relevance settings, query rules and synonyms, and copy an index, all of which change live search for your visitors. Deleting records, rules or synonyms is permanent, and copying onto an index overwrites it.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Algolia tool, reads what it needs, and answers with the source cited.
These tools change something in Algolia. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Algolia is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
What did people search for and not find last week?
What were the top searches on the products index in the last 8 days?
Which attributes are searchable on the products index?
Why does the steel kettle rank above the glass one in products?
Add a synonym on products so hob also finds cooktop.
Maya Okafor, ecommerce manager at Northwind, asked what customers searched for and could not find last week. Memtro listed the no-result searches on the products index, most frequent first. She took the top terms to the buying team.
Tom Reilly, a developer at Acme Ltd, saw that hob returned nothing although the shop sells cooktops. He asked Memtro to fix it. Memtro added a synonym on the products index so hob and cooktop find each other, and once Algolia finished the indexing task, visitors searching hob saw the cooktops.
The teams that lean on Algolia most, a question each of them asks, and what they connect beside it.
A record in Algolia is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
UptimeRobot
Honeycomb
Cronitor
FireHydrant
StatusCake
GlitchTip
GLPI
Langfuse
LibreNMS
NetBox
Snipe-IT
Woodpecker CI
Zabbix
LangSmith
Helicone
GrowthBook
Drata
Intruder
GitGuardian
Secureframe
ilert
JumpCloud
ConfigCat
Split
Aikido Security
Astronomer
Comet Opik
CrowdStrike Falcon
Detectify
Domotz
LambdaTest
LangWatch
LlamaCloud
Logz.io
Lunary
NinjaOne
Northflank
Portkey
PromptLayer
PRTG Network Monitor
Raygun
Retell AI
Runpod
Shodan
Spike.sh
Squadcast
Tenable
UpGuard
Uptime.com
Vanta
Zenduty
Cortex
WorkOS
Kandji
Automox
Huntress
SimpleMDM
Healthchecks.io
Rapid7 InsightVM
ZenhubIn Algolia, open dashboard.algolia.com → Settings → API Keys and note the Application ID at the top of the page.
Under All API Keys → New API Key, create a key for Memtro with the listIndexes, settings, search and analytics ACLs. Add addObject, deleteObject or editSettings only for the actions you will grant. Do not use the Admin API key.
In Memtro, open Connections → Algolia and paste Application ID and API key. Set Analytics region to de if Settings → Infrastructure → Analytics shows de.
Ask: "What did people search for and not find last week?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Algolia tools are the same everywhere.
Only when you ask, and only what it has been granted: add a record to an index, or replace the record with the same objectID; change some attributes of an existing record; delete one record from an index, permanently; delete up to 100 records named by objectID, permanently; create or replace a query rule (pin, hide, boost, redirect) on an index; delete a query rule from an index, permanently; create or replace a synonym on an index; delete a synonym from an index, permanently; change an index's relevance settings (only the settings named); copy an index (or only its settings, synonyms or rules) onto another index, overwriting it. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Application ID and API key. In Algolia, open dashboard.algolia.com → Settings → API Keys and note the Application ID at the top of the page.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time
