typesense

This MCP server provides a generic interface to search across any Typesense collection. It exposes a single tool named typesense_search that lets you query a Typesense cluster with a collection name, a query string, and optional filtering and pagination parameters. You can specify which fields to search in via query_by, apply filters with filter_by, and control results with page and per_page. The server is designed to be run in a containerized or environment-configured setup, using the standard Typesense connection details (host, port, protocol, and API key) through environment variables.

To use the tool, configure the environment variables to point at your Typesense instance (host, port, protocol, and API key). Then invoke a search by providing: the collection name, your query, and any optional parameters like query_by, filter_by, page, and per_page. The tool supports typo-tolerant searching and comprehensive Typesense search parameters, making it suitable for building robust search experiences across any collection.

Prerequisites:

• Docker (if you choose to run via docker) or a suitable environment to run the binary/containerized server
• Optional: Go for building from source if you have a source workflow (not required if using prebuilt container)

Installation steps (docker-based):

1. Ensure Docker is installed and running on your machine.
2. Pull/run the MCP server image (adjust the image name if you have a custom one): docker pull typesense-mcp-server-image docker run -d --name typesense-mcp-server -p 8080:8080 typesense-mcp-server-image
3. Configure environment variables for Typesense connection as needed (TYPESENSE_HOST, TYPESENSE_PORT, TYPESENSE_PROTOCOL, TYPESENSE_API_KEY).

If you prefer running a native binary (Go) or another deployment method, follow your standard deployment steps for Go binaries or container images, ensuring the Typesense connection details are provided via environment variables as described above.

Environment variables:

• TYPESENSE_HOST: Typesense server host (default: localhost)
• TYPESENSE_PORT: Typesense server port (default: 8108)
• TYPESENSE_PROTOCOL: http or https (default: http)
• TYPESENSE_API_KEY: API key for Typesense (default: xyz)

Common issues:

• Ensure Typesense is reachable from the MCP server network (firewalls, container networking).
• If authentication fails, verify the API key and that the protocol/port are correct.
• When using pagination, keep page and per_page within sensible bounds (per_page default is typically 10, max 100 as per common Typesense behavior).

Configuration tips:

• Use TYPESENSE_PROTOCOL and TYPESENSE_API_KEY to securely connect to secured clusters.
• For local development, mapping localhost:8108 and http is usually sufficient.