Algolia Search
Search indices, index records, and fetch Algolia recommendations from the agent while wiring in-app search and merchandising.
Overview
com.mcparmory/algolia-search is an MCP server for the Build phase that searches Algolia indices, indexes data, and returns personalized recommendations through your agent.
What is this MCP server?
- Search across multiple Algolia indices from agent prompts
- Index and update searchable records during build and seed tasks
- Personalized recommendation retrieval for storefront and content apps
- Remote streamable-http endpoint at https://mcp.mcparmory.com/algolia-search plus local stdio
- Version 1.0.9 with uvx mcparmory-algolia-search or Docker ghcr.io/mcparmory/algolia-search:1.0.9
- Server version 1.0.9
- 1 remote: streamable-http at https://mcp.mcparmory.com/algolia-search
- 2 local packages: PyPI mcparmory-algolia-search and OCI ghcr.io/mcparmory/algolia-search:1.0.9
Community signal: 25 GitHub stars.
What problem does it solve?
Builders implementing Algolia still context-switch to dashboards and curl scripts to test queries, push records, or verify recommend results.
Who is it for?
Indie SaaS and ecommerce builders standardizing on Algolia who want IDE-native search debugging and seeding during integration sprints.
Skip if: Sites using only database LIKE search, organic SEO rank tracking, or teams with no Algolia application configured.
What do I get? / Deliverables
After you connect the server, your agent can run live Algolia search, indexing, and recommendation calls while you implement and debug product discovery.
- Validated multi-index Algolia search results in development
- Indexed or updated records in target indices
- Recommendation payloads for personalization experiments
Recommended MCP Servers
Journey fit
Product search and discovery are built during integrations work when you connect Algolia to your frontend and data pipeline. Integrations captures hosted search SaaS wiring—multi-index query, indexing, and recommend APIs—not pure Launch SEO research.
How it compares
Algolia product-search MCP integration, not an SEO rank tracker or generic Elasticsearch admin skill.
Common Questions / FAQ
Who is com.mcparmory/algolia-search for?
Solo builders wiring Algolia into apps who want search, index, and recommend operations available from Claude Code, Cursor, or Codex.
When should I use com.mcparmory/algolia-search?
Use it while building catalog search, docs search, onboarding indexes, or recommendation widgets and you need iterative API calls from the agent.
How do I add com.mcparmory/algolia-search to my agent?
Either point MCP at the remote URL https://mcp.mcparmory.com/algolia-search (streamable-http) or run stdio via uvx mcparmory-algolia-search / Docker ghcr.io/mcparmory/algolia-search:1.0.9 with Algolia credentials.