Algolia

Algolia

This connector calls the Algolia Search API (v1) and the Analytics API (v2) of one Algolia application with the user's own API key: list indices, search and browse records, read records, settings, synonyms and Rules, read search analytics (top searches, searches without results, top hits, search volume) and, when the key allows it, add or update records.

Setup (about 3 minutes)

1. Open the Algolia dashboard: Settings > API Keys (https://dashboard.algolia.com/account/api-keys). Copy the Application ID into ALGOLIA_APP_ID.
2. Create a dedicated key under All API keys > New API key rather than reusing the Admin key, give it a description such as AnythingMCP, optionally limit it to some indices, and pick its ACL (below). Paste it into ALGOLIA_API_KEY. It is sent as the X-Algolia-API-Key header with X-Algolia-Application-Id.
3. Set ALGOLIA_ANALYTICS_REGION to us or de: the analytics region shown at https://dashboard.algolia.com/account/infrastructure/analytics. Most applications use us.

Which key for which tools

• Use a custom read key with the ACL search, browse, listIndexes, settings and analytics: it covers every tool here except writes. Recommended.
• The connection check lists the indices, which needs the listIndexes ACL. The default Search-Only API key has only search, so it fails the check with 403 "Method not allowed with this API key" even though algolia_search and algolia_get_object would work with it. Create the custom read key instead.
• Writes (algolia_save_object, algolia_partial_update_object) need addObject in addition. Every write asks the user to confirm first.
• algolia_delete_object is installed switched off and needs deleteObject. Do not use the Admin API key: it can delete indices and manage keys, and none of the tools here need that.
• To see what a key may do, open Settings > API Keys > All API keys in the dashboard: each key lists its ACL, the indices it is limited to and its rate limit; edit the key to change them. Check there when a tool answers 403 "Method not allowed with this API key".

Which tool

• algolia_list_indices first, for exact (case-sensitive) index names and record counts.
• algolia_search searches like the user's site: query text, filters (e.g. brand:Apple AND price < 500), facet counts and paging; 10 hits by default, at most 100. It does not count in the user's analytics unless record_analytics is true.
• algolia_browse reads records in bulk with a cursor (call again until no cursor comes back); use attributes_to_retrieve to keep it small.
• algolia_get_object, algolia_get_settings, algolia_search_synonyms, algolia_search_rules explain one record and why results rank as they do.
• Analytics: algolia_top_searches, algolia_no_result_searches (what users look for and do not find), algolia_top_hits, algolia_search_count. Dates are YYYY-MM-DD; the default period is the last 8 days. Analytics lag behind by up to a few hours, and an index needs traffic before it has data.

Writes are asynchronous: Algolia answers with a taskID at once and the change becomes searchable shortly after. Saving replaces the whole record; a partial update changes only the given attributes. Writes go to <APP_ID>.algolia.net, reads to <APP_ID>-dsn.algolia.net.

Errors: 403 "Invalid Application-ID or API key" means the application ID or the key is wrong or the key was deleted; 401 "Invalid credentials" is the same on the Analytics API. 403 "Method not allowed with this API key" names an ACL the key lacks, and "Index not allowed with this API key" an index it may not use. 404 "Index does not exist" or "ObjectID does not exist" is a wrong name. 429 means a rate limit of the key was hit.

Out of scope here: creating, copying or deleting indices, changing settings, synonyms or Rules, API key management, Insights events, Recommend, Query Suggestions and the Crawler.