MCP

Created By
expensivefava year ago
MCP servers for interacting with Algolia
Overview

What is MCP?

MCP (Model Context Protocol) is a set of experimental servers designed for interacting with Algolia APIs, allowing developers to explore and experiment with the protocol.

How to use MCP?

To use MCP, follow the quick start guide to install the necessary components and set up a sample Fileserver MCP server. You can clone the repository, build the server, and configure it to work with Algolia.

Key features of MCP?

  • Experimental servers for Algolia API interaction
  • Customizable and extendable for various use cases
  • Debugging tools available for testing MCP features

Use cases of MCP?

  1. Searching and managing product indexes in Algolia.
  2. Adding and updating JSON objects in Algolia indexes.
  3. Configuring index attributes for better search results.

FAQ from MCP?

  • What can I do with MCP?

You can perform various operations like searching products, adding JSON objects, and configuring index attributes.

  • Where can I read more about the Algolia MCP server?

Check out the blog post on Algolia's website for more information and a demo video.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
expensivefav
Star
0
Language
Go
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago