Typesense MCP Server

What is Typesense MCP Server?

A Model Context Protocol (MCP) server that provides a standardized interface for performing typo-tolerant searches across any Typesense collection. It integrates with the Typesense search engine and is intended for developers building AI-powered applications that need to query Typesense through the MCP protocol.

How to use Typesense MCP Server?

Configure the server with environment variables (TYPESENSE_HOST, TYPESENSE_PORT, TYPESENSE_PROTOCOL, TYPESENSE_API_KEY), then build the Go binary (go build -o typesense-mcp-server) and run it (./typesense-mcp-server). The server exposes the typesense_search tool to search documents in any Typesense collection.

Key features of Typesense MCP Server

• Generic search interface for any Typesense collection
• Support for all Typesense search parameters
• Typo-tolerant search
• Filtering and faceting support
• Pagination

Use cases of Typesense MCP Server

• Perform typo-tolerant full-text searches across Typesense collections
• Apply filter expressions and faceted search on documents
• Paginate through search results with configurable page size
• Integrate Typesense search capabilities into MCP‑enabled AI agents

FAQ from Typesense MCP Server

What environment variables are required to configure the server?

TYPESENSE_API_KEY is required; optional variables include TYPESENSE_HOST (default "localhost"), TYPESENSE_PORT (default 8108), and TYPESENSE_PROTOCOL (default "http").

What tool does the server provide?

The server provides one tool: typesense_search. It accepts a required collection name, a required search query q, and optional parameters (query_by, filter_by, page, per_page).

What are the prerequisites for running the server?

Go 1.23 or later and access to a running Typesense server.

What is the default search behavior?

By default, the search query is matched against all fields (query_by: "*"), with results paginated starting at page 1 and 10 results per page (max 100).