← Explore all mcp servers

DEVELOPER DOCUMENTATION / Algolia

Algolia DocSearch MCP

Search indexed public developer documentation and return excerpts with source URLs, without an Algolia account or API key.

“DocSearch MCP”

01 / THE REASONING

Why this made the selection.

  • Documents both one-shot product lookup and explicit documentation-set selection for multi-product questions.
  • Provides a hosted documentation-only path without granting index administration or private repository access.
  • Algolia’s DocSearch MCP pages describe a public HTTPS endpoint that does not require an Algolia application ID or API key.
  • The overview tells clients not to add Algolia credentials and not to send secrets, and it says the service does not provide access to private sources listed after that sentence.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • DocSearch MCP coverage, tools and service terms
  • Official host-specific manual installation and verification
  • DocSearch usage and source-selection workflow
  • https://docsearch.algolia.com/docs/mcp/overview/
  • https://docsearch.algolia.com/docs/mcp/installation/
  • https://docsearch.algolia.com/docs/mcp/usage/
  • Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.

Our findings

  • Official overview defines coverage, tool names, no-auth access and service limits; installation documentation separates manual MCP configuration from optional CLI/plugin guidance.
  • This is DocSearch’s public documentation endpoint, not the authenticated Algolia Productivity or application-scoped Public MCP.
  • DocSearch MCP is a remote server. The overview and install pages say the endpoint does not require authentication, an application ID, or a search API key.
  • Clients are told to connect only to the HTTPS endpoint on the page, not to add Algolia credentials, and not to send secrets or confidential data.
  • The overview says the service is for public documentation and that it does not provide access to the private categories that follow that sentence. The usage page repeats that the public endpoint does not require authentication.
  • The docs workflow resolves product documentation IDs before querying, and accepts multiple IDs for cross-product questions.

Not established by this review

  • Installation, authentication and live tool execution were not tested.
  • Service availability, security isolation and package/container parity with source were not tested.
  • The resource was not executed and its tools were not called.
  • The server was not called. A source review is not a runtime or security certification.

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.

Upstream setup instructions ↗

DOCUMENTED COMMAND

codex mcp add algolia-docsearch --url https://mcp.algolia.com/1/docsearch/mcp

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

  1. Add the official endpoint as a remote MCP server. Do not add Algolia credentials; none are required.
  2. The shown JSON is the Cursor wrapper; the upstream installation page supplies separate Codex, Claude Code, Gemini and other host formats.
  3. For routine questions use algolia_docsearch_search_docs with a product name and specific query. For ambiguity or multiple products, resolve docsets before calling query_docs.
  4. Verify that the client calls an algolia_docsearch_ tool and returns relevant source URLs; follow those sources before using generated commands.
  5. Connect only to the documented HTTPS endpoint without Algolia credentials; resolve the relevant product IDs before querying their documentation.

Before you start

  • An MCP client supporting the documented remote HTTP configuration and outbound HTTPS.
  • No Algolia application, API key or local server runtime is required for manual connection.

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "mcpServers": {
    "algolia-docsearch": {
      "url": "https://mcp.algolia.com/1/docsearch/mcp"
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://docsearch.algolia.com/docs/mcp/overview/

    Supports: summary, access, limitations, bestFor, review

  2. https://docsearch.algolia.com/docs/mcp/installation/

    Supports: install, configExample, compatibility

  3. https://docsearch.algolia.com/docs/mcp/usage/

    Supports: bestFor, install

Evidence & Ask