Algolia MCP integration for AI agents.
Connect AI agents to Algolia through 9 structured actions, including get record, add or replace record, delete records by filter, and browse index. Review au…
- ACTION CONTRACTS
- 9
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Algolia integration exposes
The Algolia Agent App exposes 9 provider-backed actions for developer tools and data work. Its current contract lets an authorized agent retrieve a single record from an algolia index by objectid, add a new record or replace an existing algolia record using its objectid, and delete algolia records that match a filter expression. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Algolia account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Algolia capabilities.
Showing 9 of 9 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_recordREADRetrieve a single record from an Algolia index by objectID.
INPUTS: indexName / objectID / attributesToRetrieve
add_or_replace_recordWRITEAdd a new record or replace an existing Algolia record using its objectID.
INPUTS: indexName / record / forwardToReplicas
delete_records_by_filterHIGH IMPACTDelete Algolia records that match a filter expression.
INPUTS: indexName / filters
browse_indexREVIEWBrowse records from a single Algolia index, optionally continuing with a cursor.
INPUTS: indexName / cursor / query / filters / facetFilters
list_indicesREADList Algolia indices accessible to the current API key.
INPUTS: page / hitsPerPage
save_ruleREVIEWSave a single Algolia rule by objectID.
INPUTS: indexName / rule / forwardToReplicas
save_synonymREVIEWSave a single Algolia synonym by objectID.
INPUTS: indexName / synonym / forwardToReplicas
search_indexREADSearch a single Algolia index with the most common search parameters.
INPUTS: indexName / query / page / hitsPerPage / filters
update_record_partiallyWRITEPartially update an existing Algolia record by objectID.
INPUTS: indexName / objectID / attributesToUpdate / createIfNotExists / forwardToReplicas
INPUT CONTRACTS
Know what the action needs before it runs.
get_record
indexNameREQUIRED- The Algolia index name.
objectIDREQUIRED- The Algolia record objectID.
attributesToRetrieveOPTIONAL- A list of non-empty strings.
add_or_replace_record
indexNameREQUIRED- The Algolia index name.
recordREQUIRED- The Algolia record payload.
forwardToReplicasOPTIONAL- Whether to forward the write operation to replicas.
delete_records_by_filter
indexNameOPTIONAL- The Algolia index name.
filtersOPTIONAL- The filter expression used to select records to delete.
browse_index
indexNameREQUIRED- The Algolia index name.
cursorOPTIONAL- The cursor returned by the previous browse response.
queryOPTIONAL- An optional browse query string.
filtersOPTIONAL- The filter expression using Algolia's SQL-like syntax.
facetFiltersOPTIONAL- An Algolia filter expression in string or array form.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Record
Retrieve a single record from an Algolia index by objectID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_recordControl Add Or Replace Record
Add a new record or replace an existing Algolia record using its objectID. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_or_replace_recordVerify with List Indices
List Algolia indices accessible to the current API key. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_indicesSAFETY BOUNDARY
Operate Algolia with explicit limits
- Authorize Algolia with API key and grant only the provider access required by the selected actions.
- 3 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_records_by_filter` as high-impact operations and require an explicit approval boundary.
- The sampled contract declares provider scopes including `addObject`, `browse`, `deleteIndex`, and `search`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Algolia task completed successfully.
CONNECTION MODEL
API key
Algolia API Key used with the X-Algolia-API-Key header. Manage keys in the Algolia dashboard: https://dashboard.algolia.com/account/api-keys.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 3
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 3
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Algolia.