Labsco
MCP SERVER

Typesense MCP Server

by suhail-ak-s ↗

Search a Typesense collection with filters and sorting, fetch the document behind a hit by ID, and have the client discover which collections exist and what fields they carry.

NoSQL, Graph & Key-Value Stores✓ Verified
Summary
The index describes itself, so the client is not hardcoded to one deployment's collection names.

typesense_list_collections returns field definitions as well as names, which is what lets the same setup work when collections differ by environment, tenant or version — its description calls this zero-conf discovery and routing. The surface is narrow and entirely read-side: there is no document upsert, no collection creation and no schema change, so the server can point at a production index without being able to alter it.

What it is

A read-only client for a Typesense instance, with runtime schema discovery so collection names need not be known in advance.

What you get
  • Search against a named collection with query_by, filter_by, sort_by and a result limit
  • A single document retrieved by its ID from a collection
  • Per-collection statistics
  • The full collection list with field definitions, so a client can enumerate collections and route to the right one before searching
Requirements

A reachable Typesense host and an API key for it, given to the server at start along with the port and protocol to use.

Setup effort

One command — npx -y typesense-mcp-server --host your-typesense-host --port 8108 --protocol http --api-key your-api-key