SEARCH AND ANALYTICS / Algolia
Algolia MCP Server
Algolia's managed MCP offerings: Public MCP exposes application-scoped search and recommendations on selected indices for customer-facing agents; Productivity MCP gives user-scoped, read-only exploration and analytics; DevEx MCP serves version-matched API client snippets to coding agents without touching data.
“Algolia supports MCP with three offerings. … All three are Algolia-managed services.”
01 / THE REASONING
Why this made the selection.
- The publisher runs three distinct managed MCP services — application-scoped public search, user-scoped read-only analysis, and a snippet generator — where the community servers found in discovery only wrap search API keys.
- Productivity MCP is read-only by design and inherits each user's Algolia permissions at sign-in, so the read/write boundary is enforced by the platform rather than by prompt discipline.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- Algolia MCP documentation overview: three Algolia-managed offerings with a selection table; Public MCP is a tool-scoped search and recommend surface with no separate MCP fee; Productivity MCP is enabled once per account with per-user sign-in and read-only index access plus analytics tools; DevEx MCP generates client snippets in eleven languages with no authentication and no data access; page last modified 2026-09-16.
- Productivity MCP setup page: server URL https://mcp.algolia.com/mcp with OAuth; scoping is account-wide and each user's Algolia permissions determine access; the offering is registry-visible in public MCP directories.
- Algolia launch announcement (June 17, 2025): the MCP Server is the first component of the publisher's agentic retrieval strategy.
Our findings
- The three offerings deliberately separate trust boundaries: customer-facing agents get a tool-scoped search surface, internal users get read-only analysis, and coding agents get snippets without credentials.
- The server is hosted by Algolia; no official server source repository exists, so repository and revision are null per the hosted-server precedent.
- Correction, 2026-10-13: the earlier configExample mixed the Productivity MCP page’s Cursor and VS Code blocks and matched neither. It is now the page’s VS Code ~/.vscode/mcp.json block as printed.
Not established by this review
- No Algolia application was connected and no search, analytics or snippet tool was executed.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
- Enable Productivity MCP once per account in the Algolia dashboard under Generative AI > MCP Servers.
- Add https://mcp.algolia.com/mcp as a remote MCP server in the client and sign in with your Algolia login when prompted.
- For customer-facing agents, create a Public MCP instance from the dashboard and select the indices to expose.
Before you start
- An Algolia account with access to the target applications and indices.
- An MCP client supporting Streamable HTTP with OAuth.
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"servers": {
"algolia": {
"type": "http",
"url": "https://mcp.algolia.com/mcp"
}
}
}04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://www.algolia.com/doc/guides/model-context-protocol
Supports: summary, upstreamDescription, descriptionSourceUrl, whySelected, limitations, access
https://www.algolia.com/doc/guides/model-context-protocol/productivity-mcp
Supports: configExample, install, transports, compatibility
https://www.algolia.com/about/news/algolia-introduces-context-aware-retrieval-for-the-agentic-era
Supports: summary, whySelected