typesense_collection_stats
Get statistics about a Typesense collection
LABSCO 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>
USE CASES
01
Answering a question against an index someone else built
Enumerate the collections and their field definitions, pick the one that carries the data, and search it with the fields, filters and sort that its schema actually supports.
02
Pulling the full record behind a search hit
Search returns the match; fetching the document by its ID gets the fields the search response left out.
03
Checking whether a collection holds what you expect before you trust it
Read the collection's statistics and its field definitions to confirm the shape and the volume, rather than inferring both from the first page of results.
4 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
typesense_get_document
Retrieve a specific document by ID from a Typesense collection
typesense_list_collections
List all available Typesense collections with their schemas. Allows zero-conf discovery and routing - the LLM can enumerate collections at runtime and pick the right one(s) before searching. Useful when collections vary by environment, tenant, or version. Returns field definitions for schema inference.
typesense_query
Search for relevant documents in the TypeSense database based on the user's query.
BEFORE YOU INSTALL
What to know first
Tools you get
4 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 4 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"typesense-mcp-server": {
"command": "npx",
"args": [
"-y",
"typesense-mcp-server",
"--host",
"<YOUR_TYPESENSE_HOST>",
"--port",
"8108",
"--protocol",
"http",
"--api-key",
"<YOUR_API_KEY>"
]
}
}
}npx
TERMINAL
npx -y typesense-mcp-server --host <YOUR_TYPESENSE_HOST> --port 8108 --protocol http --api-key <YOUR_API_KEY>
