Missing from search
Support at Brightwave Ltd says a new article cannot be found. Memtro lists recent tasks, finds a failed document addition from 23:40 with a primary key error, and confirms the article is not in the index.
Ask why a document is missing from Meilisearch search, and whether last night's import failed.
Connect Meilisearch with your host and an API key and Memtro reads indexes with their statistics, searches an index, reads one document and lists indexing tasks with their status and errors. The instance's API keys are never read, and documents are your own data, so restrict the key to the indexes Memtro should see. When you ask, and once an administrator has granted them by name and the key allows, it can add, update or permanently delete documents, empty an index, create, delete or swap indexes, change settings and synonyms, cancel tasks, and start dumps or snapshots.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Meilisearch tool, reads what it needs, and answers with the source cited.
These tools change something in Meilisearch. 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.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Meilisearch for you. Each event can start a job, with the event as its input. Meilisearch sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Meilisearch 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.
Did last night's import into the products index fail?
Why does a search for blue kettle return nothing?
How many documents are in the articles index?
Delete the document with id 4471 from the products index
Add kettle as a synonym for jug in the products index
Support at Brightwave Ltd says a new article cannot be found. Memtro lists recent tasks, finds a failed document addition from 23:40 with a primary key error, and confirms the article is not in the index.
Priya Sharma asks Memtro to take a recalled Acme product out of search. With the action granted, Memtro finds it, permanently deletes that one document by primary key and says the task was queued. The shop's search stops showing it once the task runs.
The teams that lean on Meilisearch most, a question each of them asks, and what they connect beside it.
A record in Meilisearch 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.
Make a key for Memtro (Meilisearch Cloud → Project → Settings → API Keys, or POST /keys with the master key) with indexes.get, stats.get, search, documents.get and tasks.get. Never paste the master key
Add documents.add and documents.delete only if Memtro should change documents, indexes.create, indexes.update, indexes.delete and indexes.swap to manage indexes, settings.update for settings, tasks.cancel and tasks.delete for tasks, and dumps.create and snapshots.create for backups
In Connections → Meilisearch in Memtro type the Host name only, a public DNS name with a publicly trusted certificate (plain http on 7700 is refused, so put a self-hosted server behind a TLS proxy), and paste the API key
Ask whether last night's import failed
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Meilisearch tools are the same everywhere.
Only when you ask, and only what it has been granted: add documents to an index, replacing whole any document with the same primary key; update fields of documents in an index, adding any that do not exist; delete one document from an index; delete the documents in an index that match a filter; empty an index (delete every document); create an index; delete an index with all its documents and settings; delete up to 100 listed documents by id; change an index's settings (searchable, filterable, sortable and displayed attributes, ranking, stop words, synonyms, typo tolerance, limits); replace an index's synonyms; change an index's primary key; swap two indexes; cancel listed queued or running tasks; delete listed tasks from the task history; create a dump of the instance; create a snapshot of the instance. 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.
Host and API key. Make a key for Memtro (Meilisearch Cloud → Project → Settings → API Keys, or POST /keys with the master key) with indexes.get, stats.get, search, documents.get and tasks.get. Never paste the master key.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Meilisearch for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
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