Search Algolia indices and keep their records, settings, synonyms and rules in sync.
Algolia ships in the w6w first-party pack. It declares 22 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
io.w6w.algoliaAlgolia turns a workflow step into full control over a search index: running one-off and multi-index searches, walking an entire index page by page with browse, and reading, adding, updating or deleting individual records, plus batch writes and filtered bulk deletes for larger changes.
Index management goes beyond records: list indices, read and update settings, manage synonyms and query rules, and re-index with zero downtime by building a temporary index and atomically moving it into place, or cloning configuration without records. Every write in Algolia is asynchronous — it returns immediately with a task ID, and the change is not searchable until that task publishes. A dedicated action checks a task’s status, so a workflow that searches right after writing can wait for the real guarantee instead of racing it.
Reads are automatically routed through Algolia’s geo-replicated read host and writes go to the primary, matching the split Algolia’s own client libraries use. A log-list action surfaces recent API activity for troubleshooting search and indexing issues.
Three routes to the same 22 actions. The Workflow tab is generated from Algolia's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
index-clear Delete every record in an index, keeping its settings, synonyms and rules.
index-operation Copy an index (optionally just its configuration), or move it atomically.
objects-delete-by Delete every record matching a filter. Filters only — not a text query.
search-multi Run several queries, across one or many indices, in a single request.
settings-get Read an index's searchable attributes, ranking, faceting and typo settings.
synonym-search List or search an index's synonyms. An empty query returns all of them.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Algolia's real ids.
{
"manifestVersion": "2",
"name": "algolia-example",
"steps": [
{
"id": "browse",
"uses": {
"app": "io.w6w.algolia",
"action": "browse",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"indexName": "<indexName>"
}
}
]
}browse index-clear index-list index-operation log-list +17 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Algolia, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Algolia. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "browse",
payload: {
indexName: "<value>",
// cursor: "<value>",
// hitsPerPage: "<value>",
// query: "<value>",
// filters: "<value>",
// attributesToRetrieve: "<value>",
// extraParams: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value); npm install -g @w6w/cli w6w run conn_YOUR_CONNECTION_ID --action browse --payload '{"indexName":"<value>"}' Give an AI agent Algolia — without giving it Algolia's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.algolia#browse",
"input": {
"indexName": "<indexName>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Algolia connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Algolia's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Algolia itself is MIT, and the runtime that executes it is source-available (FSL).
Algolia declares its own checks, so its health is a property of the app rather than something the host guesses at.
Algolia's own per-cluster status API (status.algolia.com/1/status), rolled up across the fleet. Unauthenticated and unsigned.