Algolia documents an official managed Model Context Protocol server at algolia.com/doc/guides/model-context-protocol/productivity-mcp. Connect MCP clients to the remote HTTP endpoint `https://mcp.algolia.com/mcp` with OAuth (enable under Generate AI in the Algolia dashboard; sign in when prompted so the MCP inherits your account permissions). Productivity MCP is user-scoped and read-only per docs—tools cover search (`algolia_search_list_indices`, `algolia_search_index`, `algolia_search_for_facet_values`), Recommend (`algolia_recommendations`), and analytics helpers such as top searches, no-click rates, filter usage, and user counts. Algolia docs distinguish this from Algolia Public MCP for application-scoped, curated index exposure to external agents. Supported clients include ChatGPT, Claude, Claude Code, Cursor, Gemini CLI, VS Code, and OpenAI Playground.
Use cases
- Let agents query Algolia indices and facet values during relevance tuning
- Pull no-click and zero-result analytics into LLM-assisted search reviews
- Compare Productivity MCP against meilisearch-mcp for hybrid search ops
- Prototype internal search QA workflows without writing custom analytics scripts
- Pair with algolia tool entry when evaluating Public MCP for external agents
Key features
- Claude Desktop
- Cursor
- ChatGPT
- VS Code
- Gemini CLI
Frequently Asked Questions
- Is this the same as algolia/mcp-node on GitHub?
- No—Algolia docs describe managed Public and Productivity MCP servers; mcp-node is an experimental local Node server not covered by Algolia SLA.
- Can agents write to indices?
- Productivity MCP docs describe read-only access for analysis and exploration; data changes still happen through Algolia APIs outside MCP.
- Public MCP or Productivity MCP?
- Algolia docs: Public MCP for curated external agent access; Productivity MCP for internal user-scoped workflows across your applications.
Related
Related
3 Indexed items
Meilisearch MCP Server
Meilisearch maintains an official Model Context Protocol server in meilisearch/meilisearch-mcp, documented at meilisearch.com/blog/introducing-mcp-server. The Python stdio server connects MCP clients to any running Meilisearch instance via `MEILI_HTTP_ADDR` and optional `MEILI_MASTER_KEY`, with `update-connection-settings` to switch hosts mid-session. Tools cover index management, document ingestion, search (filters, sorting, facets, semantic/hybrid), settings, API keys, tasks, and health checks per the README. Install paths include `uvx meilisearch-mcp`, pip, source, and Docker (`getmeili/meilisearch-mcp`). Meilisearch notes the server is development-oriented and that native Meilisearch MCP transport support is coming.
Elastic Agent Builder MCP Server
Elastic documents the recommended Agent Builder Model Context Protocol endpoint at `{KIBANA_URL}/api/agent_builder/mcp` (or `{KIBANA_URL}/s/{SPACE_NAME}/api/agent_builder/mcp` for custom Kibana spaces) per elastic.co/docs/explore-analyze/ai-features/agent-builder/mcp-server. The MCP server exposes built-in and custom Agent Builder tools to Claude Desktop, Cursor, VS Code, and other MCP clients via `npx mcp-remote` with an `Authorization: ApiKey` header. API keys must include the Kibana application privilege `feature_agentBuilder.read` or clients receive HTTP 403. Elastic notes the legacy `elastic/mcp-server-elasticsearch` project is deprecated in favor of this endpoint on Elastic 9.2+ and Elasticsearch Serverless; docs recommend least-privilege index scopes and API key expiration.
PostHog MCP Server
PostHog documents a free hosted Model Context Protocol endpoint at `https://mcp.posthog.com/mcp` per posthog.com/docs/model-context-protocol that lets MCP clients query analytics, manage feature flags, investigate errors, run HogQL, triage support workflows, and configure CDP destinations from natural-language prompts. The PostHog Wizard installs the server into Cursor, Claude Code, Claude Desktop, Codex, VS Code, Windsurf, and Zed via `npx @posthog/wizard@latest mcp add`. Authentication routes to the correct US or EU data region; manual setups can pass a personal API key with the MCP Server preset through `mcp-remote` and an `Authorization` Bearer header. Source lives in the PostHog monorepo at `services/mcp` (the standalone PostHog/mcp repository redirects there).