Labsco
MCP SERVER · OFFICIAL PROJECT

Algolia Search & Analytics

by Algolia

Two read-only Algolia servers: one that generates a search tool per index, one that adds analytics and configuration reads.

NoSQL, Graph & Key-Value StoresOfficial source
Summary
One tool per index is a good fit for search, and read-only removes the worst failure mode.

Generating a tool per index means the model picks the index by name instead of passing a string that has to be exactly right — the sort of mistake that returns an empty result set and no explanation. Both servers being read-only matters just as much: an agent with search analytics can tell you which queries return nothing, and cannot reconfigure the index while it is at it. The two ChatGPT-only tools are a compatibility detail worth knowing if that is your client.

What it is

Algolia publishes two endpoints. The public one is dynamic — it generates a search tool for each index you expose, plus facet-value search and recommendations. The productivity one adds 16 documented tools covering analytics and index configuration. Both are read-only.

What you get
  • A search tool per exposed index, named after the index itself
  • Facet-value search and recommendation retrieval
  • Analytics reads: click positions, no-click rate, top searches without clicks, top filters, no-results rate
  • Two extra tools, search and fetch, that ChatGPT requires to connect at all
Requirements

OAuth 2.0 with PKCE and dynamic client registration against dashboard.algolia.com, scoped to public. Calling tools/list without a login returns 401, so the tool tables here are Algolia's documentation rather than a live listing.

Setup effort

Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen