mcp

MCP.Pizza Chef: algolia

This MCP server repository provides experimental servers designed to interface with Algolia APIs using the Model Context Protocol. It enables real-time, structured interaction with Algolia search services, allowing developers to build and experiment with AI-enhanced search workflows. While unofficial and unsupported by Algolia's SLA, it offers a flexible platform for prototyping and integrating Algolia capabilities into MCP-based applications.

Use This MCP server To

Integrate Algolia search into AI workflows via MCP Prototype AI-driven search enhancements with Algolia data Experiment with real-time Algolia API calls in MCP environments Build custom search tools leveraging Algolia through MCP Test Algolia query responses within AI context protocols

README

MCP

This repository contains experimental Model Context Protocol (or MCP) servers for interacting with Algolia APIs. This MCP repo is something we're sharing for you to explore and experiment with. Feel free to use it, fork it, or build on top of it — but just know that it's not officially supported by Algolia and isn't covered under our SLA. We might update it, break it, or remove it entirely at any time. If you customize or configure things here, there's a chance that work could be lost. Also, using MCP in production could affect your Algolia usage.

If you have feedback or ideas (even code!), we'd love to hear it. Just know that we might use it to help improve our products. This project is provided "as is" and "as available," with no guarantees or warranties. To be super clear: MCP isn't considered an "API Client" for SLA purposes.

Installation

First follow the quick start, which will install Claude Desktop and setup a sample Fileserver MCP server. This is a great introduction to using MCP and will let you debug things using the official guide if there are issues.

Setup the prototype Algolia MCP server

Requirements:

Clone the repo and build the server

Clone the repo, amd build the mcp server:

$ git clone git@github.com:algolia/mcp.git
$ cd mcp/cmd/mcp
$ go build

We need to have the full path of the built server binary:

$ pwd
/path/to/the/repo/cmd/mcp

NOTE: When adding this command to your configuration, you must specify the binary along with the path (/path/to/the/repo/cmd/mcp/mcp)

Update the settings to point to the new server

In Claude desktop edit the settings as per https://modelcontextprotocol.io/quickstart/user#2-add-the-filesystem-mcp-server and this time add the server definition for algolia (using the server path that you found earlier).

{
   "mcpServers": {
      "algolia": {
         "command": "/path/to/the/repo/cmd/mcp/mcp",
         "env": {
            "ALGOLIA_APP_ID": "<APP_ID>",
            "ALGOLIA_INDEX_NAME": "<INDEX_NAME>",
            "ALGOLIA_API_KEY": "<API_KEY>",
            "ALGOLIA_WRITE_API_KEY": "<ADMIN_API_KEY>",  /* if you want to allow write operations, use your ADMIN key here */
            "MCP_ENABLED_TOOLS": "",  /* optional: specify which tools to enable (e.g., "search,collections") */
            "MCP_SERVER_TYPE": "stdio",  /* optional: server type, either "stdio" (default) or "sse". If not set, defaults to "stdio" */
            "MCP_SSE_PORT": "8080"  /* optional: port for SSE server, default is 8080 (only used when MCP_SERVER_TYPE is "sse") */
         }
      }
   }
}

By default, all available tools are enabled when MCP_ENABLED_TOOLS is empty or not set. If you want to enable only specific tools, you can set this variable to a comma-separated list of tool names. Available tools are: abtesting, analytics, collections, monitoring, querysuggestions, recommend, search, search_read, search_write, usage.

  • search: Enables all search operations (both read and write)
  • search_read: Enables only read operations (list indices, get settings, run queries, get objects)
  • search_write: Enables only write operations (clear, copy, delete, move, set settings, delete objects, insert objects)

Restart Claude desktop, and you should see a new "algolia" tool is available.

Debugging

You can run the Inspector (see https://modelcontextprotocol.io/docs/tools/inspector) to check the MCP features and run them manually.

From the repo root, setup the environment

$ export ALGOLIA_APP_ID=""
$ export ALGOLIA_INDEX_NAME=""
$ export ALGOLIA_API_KEY=""
$ export ALGOLIA_WRITE_API_KEY=""  # if you want to allow write operations, use your ADMIN key here
$ export MCP_ENABLED_TOOLS=""  # if you want to restrict the tools activated you can optionally specify a list
$ export MCP_SERVER_TYPE="stdio"  # optional: server type, either "stdio" (default) or "sse". If not set, defaults to "stdio"
$ export MCP_SSE_PORT="8080"  # optional: port for SSE server, default is 8080 (only used when MCP_SERVER_TYPE is "sse")

Move into the server directory, and rebuild (if necessary):

$ cd cmd/mcp
$ go build # might already be up-to-date

Run the MCP inspector on the server:

$ npx @modelcontextprotocol/inspector ./mcp

Using with Ollama

You can actually run a local mcphost (which orchestrates the MCP servers for you), and then use them with other models locally via Ollama.

We are using https://github.com/mark3labs/mcphost for this.

As per the README you need a a config file, so you can copy the Claude one, and put it somewhere sensible so you can use it on the command line (for example ~/mcp.json)

{
   "mcpServers": {
      "algolia": {
         "command": "/path/to/the/repo/cmd/mcp/mcp",
         "env": {
            "ALGOLIA_APP_ID": "<APP_ID>",
            "ALGOLIA_INDEX_NAME": "<INDEX_NAME>",
            "ALGOLIA_API_KEY": "<API_KEY>",
            "MCP_ENABLED_TOOLS": "",  /* optional: specify which tools to enable (e.g., "search,collections") */
            "MCP_SERVER_TYPE": "stdio",  /* optional: server type, either "stdio" (default) or "sse". If not set, defaults to "stdio" */
            "MCP_SSE_PORT": "8080"  /* optional: port for SSE server, default is 8080 (only used when MCP_SERVER_TYPE is "sse") */
         }
      }
   }
}

By default, all available tools are enabled when MCP_ENABLED_TOOLS is empty or not set. If you want to enable only specific tools, you can set this variable to a comma-separated list of tool names. Available tools are: abtesting, analytics, collections, monitoring, querysuggestions, recommend, search, search_read, search_write, usage. You can now run it directly (no need to check out the repo):

$ go run github.com/mark3labs/mcphost@latest --config ~/mcp.json -m ollama:qwen2.5:3b

FAQ

What sort of things can I do once I install this MCP?

Here are some sample prompts to seed your imagination:

  • “Search all products in the index where brand = ‘Nike’ and price < 100.”
  • “Add this JSON object to the blog_posts index.”
  • “Update the searchable attributes for the recipes index to include ingredients.”
  • “Configure my index to rank nebula_award winners higher”

Where can I read more about the Algolia MCP server?

Check out this blog post including an embedded demo video.

Resource templates and root are not supported by Claude desktop right now

This is a weird one, since there is a bunch of content online showing the templates, maybe it's just not GA yet.

mcp FAQ

Is this MCP server officially supported by Algolia?
No, this MCP server is experimental and not covered under Algolia's SLA or official support.
Can I use this MCP server in production environments?
It is not recommended as it may affect your Algolia usage and is subject to change or removal without notice.
How do I install and start using this MCP server?
Follow the MCP quick start guide and the repository's installation instructions to set up the server.
Can I customize or extend this MCP server?
Yes, you can fork, customize, and build on top of it, but be aware that updates may break your changes.
Does this MCP server guarantee uptime or stability?
No, it is provided "as is" without warranties or guarantees of uptime or stability.
How can I provide feedback or contribute?
You can submit feedback or code contributions via the repository; maintainers may use it to improve their products.
What risks are involved in using this MCP server?
Using it may lead to loss of custom work if updates occur and could impact your Algolia usage quotas.