by Algolia
Updated October 19, 2026
MCP100 verdict
Not currently recommended. Shortlist — editorially admitted, not a Recommended endorsement.
MCP100 Assessment
Editorial verdict
Reviewed October 19, 2026
Task Fit
Mapped
Specialized workflows
Trust
Status warning
Account-scoped remote OAuth runtime not tested independently; published tool list may vary by account.
Maintenance
Date unavailable
No dated repository or package update is currently stored.
Popularity
Signals unavailable
No independently comparable adoption metric is currently stored.
Evidence scope
12 shared-repository stars · not MCP-specific
No MCP-specific package metric is stored
Repository identity: algolia/skills
Stars observed October 20, 2026 · Downloads observed October 20, 2026
Official Algolia skills repository includes an `algolia-mcp` skill for the hosted Productivity MCP, but it is a multi-skill distribution repository, not the hosted server implementation.
Algolia Productivity MCP is hosted; no exact public package distribution for the hosted server was verified.
Publisher activity observed October 19, 2026
Current source snapshot
Source relationship: First-party MCP
Reviewed October 19, 2026
Evidence-backed setup
Choose your MCP client. A client connects to the MCP server; the language model is selected inside that client. Only stored, source-backed configurations are shown.
Transport not recorded
Complete client-specific setup, verification and removal are not documented in this reviewed source.
Publisher-documented setup is not the same as MCP100 execution testing. “MCP100 logic checked” means the stored configuration shape was reviewed, not that third-party MCP software was run.
Evidence checked 2026-10-19
Type-appropriate, source-backed setup for this mcp server profile.
Loading optional publisher installation details…
{"url":"https://mcp.algolia.com/mcp"}Capability
The official Algolia Productivity MCP connects an authorized Algolia account through the remote OAuth endpoint. It supports index inspection, search performance analysis, and recommendations; account mutation uses other tools such as Algolia CLI. Do not confuse Productivity MCP with the separately app-scoped Public MCP.
Remote Productivity MCP read-only surface; exact tool inventory not publicly established
Not measured yet
Estimated token footprint of the MCP tool schemas exposed to the agent.
https://mcp.algolia.com/mcp
Reviewed access
Related reviewed MCPs
Let AI clients inspect and automate web browsers with Playwright.
Choose this instead if
Choose Playwright MCP instead if inspecting and testing web interfaces through accessibility snapshots.
Let AI clients inspect and automate web browsers with Playwright.
Use Stripe's remote MCP endpoint for supported payment workflows.
Choose this instead if
Choose Stripe MCP instead if searching Stripe documentation and support knowledge from an MCP client.
Use Stripe's remote MCP endpoint for supported payment workflows.
Manage and search Redis data through Redis's MCP server.
Choose this instead if
Choose Redis MCP instead if inspecting and manipulating Redis strings, hashes, lists, sets, sorted sets, streams, JSON, and search indexes.
Manage and search Redis data through Redis's MCP server.
Algolia is listed as First-party MCP in MCP100’s current evidence.
Current official resources:
From the publisher README
Original client setup and configuration retained from the publisher documentation.
Publisher-documented clients
These names appear in the publisher's installation documentation. MCP100-verified configurations are shown separately above when available.
Extends Algolia MCP/CLI/official skills: install those official tools when the agent needs live account inspection (Algolia MCP, read-only) or write actions (Algolia CLI), then use these skills as the customer-ready implementation workflow layer.
These skills follow the open Agent Skills specification, so one folder works across most tools. Unzip the download and copy each algolia-* folder into .agents/skills/ in your project (or ~/.agents/skills/ for every project). That covers Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity and Devin Desktop (formerly Windsurf). Each copied folder must contain SKILL.md at its top level.
Two tools need their own path: Claude Code reads ~/.claude/skills/ or .claude/skills/ and does not read .agents/skills/; Kiro reads .kiro/skills/.
For the Claude and ChatGPT apps, upload an individual skill ZIP (Customize → Skills in Claude, the Skills tab in ChatGPT) rather than copying folders. The uploader expects one skill folder at the ZIP root, so the full-library ZIP will be rejected.
Note: the specification standardises the skill folder, not where each tool looks for it. .agents/skills/ is the documented cross-tool location for Codex; the older ~/.codex/skills/ still loads for backward compatibility.
See artifacts/install-instructions.md for a customer-facing install guide. The React site serves the same files from public/artifacts/.
Original product, capability, tool, and usage documentation from the MCP publisher. Installation sections appear under Install & Agents.
Title: implementation-skills/README.md at main · algolia/implementation-skills
URL Source: https://github.com/algolia/implementation-skills/blob/main/README.md
Markdown Content: Codex/Claude-compatible implementation skill bundles that extend Algolia MCP, the Algolia CLI, and official Algolia skills with business context, implementation guardrails, and launch QA.
This package is generally available and SME-reviewed.
This library is the customer implementation layer for Algolia's agent tooling. Algolia MCP gives agents read-only access to live account data, the Algolia CLI performs the account actions, and official Algolia skills carry the product workflows; these implementation skills make that tooling easier to apply by teaching agents how to ask better questions, sequence work, make safer assumptions, and produce validation artifacts before making implementation decisions.
When an agent downloads the full library, it should treat Algolia as a connected system, not a set of isolated tasks. Data modeling and event setup come first in that mental model because they shape how search behaves, how relevance can be tuned, how analytics can be trusted, and how AI features such as NeuralSearch, Dynamic Re-Ranking, Recommend, personalization, and Agent Studio can learn from user behavior.
It is designed to work either as a separate companion repo linked from the official Algolia skills/docs experience, or as a mergeable customer implementation extension inside the official skills repo after SME review.
This is for customer teams using Algolia with or without a dedicated search team. It is especially useful when a customer needs an AI agent to ask better setup questions, turn business goals into implementation steps, create handoff notes for the right owner, and validate the result before launch.
These are customer-ready implementation skills that work alongside official Algolia Academy, docs, MCP, CLI, official Algolia skills, and support. Use them to add discovery prompts, readiness checks, implementation planning, and validation artifacts around official Algolia tooling.
The recommended lens is whole-product Algolia implementation:
algolia-search-implementation: guided workflow and readiness signposts for net-new search, browse, autocomplete, ecommerce, personalization, recommendations, Dynamic Re-Ranking, and search UI builds.algolia-discovery-planning: ask the right product, business, data, and measurement questions before implementation.algolia-audit: entry point for reviewing an existing implementation — captures live state first and hunts the symptom-free defects (inert ranking chains, non-searchable facets, flat hierarchy, missing facet stats, leaked internal fields, drifted replicas, dead events) that pass every demo.algolia-data-modeling: design records, variants, SKUs, indices, replicas, objectIDs, and indexing contracts.algolia-index-configuration: configure relevance, ranking, facets, synonyms, rules, replicas, and merchandising.algolia-events-insights: implement a simple event plan for clicks, conversions, views, cart, purchase, queryID, and userToken.algolia-instantsearch-ui: build and review InstantSearch search and browse experiences.algolia-autocomplete: build and review autocomplete, query suggestions, recent searches, and federated panels.algolia-release-qa: audit implementation quality before release or after risky changes.algolia-agent-studio: plan, implement, validate, and optimize Agent Studio experiences, including tools, LLM providers, memory, analytics, feedback, guardrails, authentication, and tool security.algolia-neuralsearch: plan, implement, validate, and optimize NeuralSearch with data readiness, semantic query sets, event measurement, A/B testing, and rollout checks.algolia-ui-libraries: select current Algolia UI libraries and docs paths for InstantSearch, Autocomplete, mobile SDKs, routing, SSR, events, and frontend architecture. This is kept beside the procedural skills as a living selector/reference pack rather than a frozen docs dump.
Copy one or more skill folders into an agent skills directory, or invoke them directly from this repository by path. Each folder has a SKILL.md and optional references/ files. The same SKILL.md frontmatter pattern is intentionally usable by both Codex-style and Claude-style skill loaders.
These skills are intentionally modular, but the library should be used through a whole-Algolia lens. For net-new search implementation requests, start with algolia-search-implementation so the data, events, index configuration, UI, and release QA decisions are visible in order. Start with algolia-discovery-planning when the request is broad or the implementation path is unclear, then route to the narrower implementation skill. Product-focused AI skills should still call into the foundation skills when data, events, relevance settings, UI integration, security, or release validation are prerequisites. Use algolia-ui-libraries as a living selector before implementation when the agent needs to choose a current frontend or mobile library.
When live account data is needed — analytics, index inspection, search results — use Algolia MCP, which is read-only. When something must actually change — settings, object imports, rules, synonyms, API keys — use the Algolia CLI, or official Algolia skills for a product-specific workflow. Then use these implementation skills to interpret the result, ask the next customer question, and validate the implementation path.
Skill content lives in algolia/skills — the official repo, where this suite ships as the algolia-implementation plugin. This repo consumes it as a submodule at vendor/algolia-skills and never keeps its own copy, so skill content cannot drift from the official version. Edit skills by opening a PR against algolia/skills, then:
npm run skills:update && npm run release:prepare
Everything else the downloads need lives here: artifacts/ (canonical, hand-edited; public/artifacts/ is the served copy), packaging/suite.json (which skills this site packages), and packaging/library-README.md (bundled into the full-library ZIP).
The retired algolia/algolia-implementation-skills repo was the pre-merge staging ground for the suite. It is archived; do not add content there.
Customer start prompt:
Use the Algolia Discovery Planning skill to help me choose the right implementation path. Ask me only the questions needed to understand my goal, data, search UI, events, and launch risk. Assume I may not know which technical details matter yet. Then recommend the next Algolia skill, the smallest useful first milestone, and the validation artifact I should create.
Guided search build prompt:
Use the Algolia Search Implementation skill to build this search experience with clear decision points for the data contract, event taxonomy, index configuration, UI implementation, and release QA. If any decision is provisional or deferred, keep moving but document the assumption, owner, risk, and validation follow-up in the completion summary.
Whole-library orientation prompt:
Use the Algolia skills library through the whole Algolia lens. Begin by clarifying the data contract and event foundation because they determine search behavior, relevance tuning, analytics trust, and AI feature readiness. Then route to the right skills for index configuration, UI, NeuralSearch, Dynamic Re-Ranking, Recommend, personalization, Agent Studio, and release QA.
Install these official Algolia tools with the implementation bundles so agents can move from customer context to live inspection, account operations, official workflows, and validation:
Algolia Productivity MCP reads; the Algolia CLI writes. Reaching for the MCP to change something is the common wrong turn.
| Tool | Use it for | Install or setup |
|---|---|---|
| Algolia Productivity MCP | Live analytics, index inspection, recommendations, and account-aware reviews for your own account. | claude mcp add --transport http algolia https://mcp.algolia.com/mcp, then /mcp to authorize by browser sign-in. For customer-facing agents use app-scoped Public MCP instead; there is no local/npx server. |
| Algolia CLI | Index, settings, rules, synonyms, records, and operational account tasks. | brew install algolia on macOS, npx @algolia/cli anywhere, or the official setup guide for Linux and Windows. |
| Official Algolia skills | Official Algolia MCP, CLI, algobot, Crawler, InstantSearch, and core tooling workflows. | /plugin marketplace add algolia/skills then /plugin install algolia-implementation@algolia-skills in Claude Code; npx skills add https://github.com/algolia/skills elsewhere. |
See artifacts/repo-integration-strategy.md for the recommended separate-repo and merge-into-official-repo options.
The portal also packages scenario-specific bundles for:
Each bundle combines the relevant skills, validation artifacts, and a scenario-specific BUNDLE.md guide so an agent can work from customer context to implementation plan and QA evidence.
When a skill needs current source-backed guidance, use public Algolia sources:
artifacts/academy-reference-pack.md first as a metadata-only structure cache with title, url, course, module, learning_objectives, and updated_at.updated_at is stale, if no strong match is found, or if the agent needs current behavior, code, limits, or setup steps, fall back to live public lookup.academy.algolia.com for customer education alignment, relevant courses, and learning objectives.algolia.com/doc for implementation details, APIs, package usage, current feature behavior, limits, and configuration guidance.
The portal includes downloadable templates mirrored in artifacts/ and served by the React site from public/artifacts/:
The current pass is based on Algolia documentation checked through 2026-07-09, supplied Academy course/design material for data gaps, events, InstantSearch, Autocomplete, Query Suggestions, NeuralSearch, and Agent Studio, plus review against the official Algolia skills bundle supplied locally as skills-main.zip. The Academy material is used procedurally: to shape questions, teaching moments, readiness gates, implementation plans, and validation artifacts. For customer use, verify current public Algolia docs and the latest official skills repository before version-specific implementation guidance.
For questions about this review package, contact Daniel Williams at daniel.williams@algolia.com.
This is an SME-reviewed implementation companion library. Each skill declares the MIT license in its frontmatter, and the full terms are included in LICENSE. Position it as an implementation layer that works alongside official Algolia Academy, docs, MCP, CLI, official skills, and support; it does not replace current official product documentation or live-account validation.
These skills guide implementation work, but customers still need current official docs verification, access to their own Algolia/data systems, and production validation before launch.