Skip to main content
Glama
Typesense MCP Server

Typesense MCP Server

by avarant

Typesense MCP Server

A Model Context Protocol (MCP) Server that interfaces with Typesense

Installation

Install uv

Requires Python 3.11 or higher.

On Mac you can install it using homebrew

brew install uv

Clone the package

git clone git@github.com:avarant/typesense-mcp-server.git ~/typesense-mcp-server

Add the server to your MCP client config. Most clients (Cursor at ~/.cursor/mcp.json, Claude Desktop at ~/Library/Application Support/Claude/claude_desktop_config.json, Windsurf, Zed, VS Code, etc.) accept the same mcpServers shape:

{
  "mcpServers": {
    "typesense": {
      "command": "uv",
      "args": ["--directory", "~/typesense-mcp-server", "run", "mcp", "run", "main.py"],
      "env": {
        "TYPESENSE_HOST": "",
        "TYPESENSE_PORT": "",
        "TYPESENSE_PROTOCOL": "",
        "TYPESENSE_API_KEY": ""
      }
    }
  }
}

Refer to your client's MCP documentation for the exact config file location.

Related MCP server: Better Qdrant MCP Server

Transports

The server supports three MCP transports. STDIO is the default and is what most desktop clients (Claude Desktop, Cursor, etc.) use. For remote clients or web UIs, you can run it as an HTTP server using either the legacy SSE transport or the newer Streamable HTTP transport.

STDIO (default)

TYPESENSE_API_KEY=xyz uv run python main.py

Single endpoint at /mcp. Works with browser-based clients like the llama.cpp web chat. Set MCP_TRANSPORT=streamable-http (or pass --http):

TYPESENSE_API_KEY=xyz \
MCP_TRANSPORT=streamable-http \
MCP_STATELESS_HTTP=true \
MCP_CORS_ORIGINS='*' \
uv run python main.py
  • Stateless mode (MCP_STATELESS_HTTP=true) is required for clients that don't keep an MCP session across requests.

  • CORS must be enabled (MCP_CORS_ORIGINS) for browser clients. Use a specific origin like http://localhost:8080 in production rather than *.

SSE (legacy)

Two endpoints, GET /sse for the event stream and POST /messages/ for JSON-RPC. Set MCP_TRANSPORT=sse (or pass --sse):

TYPESENSE_API_KEY=xyz MCP_TRANSPORT=sse uv run python main.py

Configuration

Env var

Default

Description

MCP_TRANSPORT

stdio

stdio, sse, or streamable-http

MCP_HOST

0.0.0.0

Bind address for HTTP transports

MCP_PORT

8000

Bind port for HTTP transports

MCP_STATELESS_HTTP

false

Stateless mode for HTTP transports (required for some web clients)

MCP_CORS_ORIGINS

(empty)

Comma-separated allowed origins. Empty disables CORS. * = any.

Available Tools

The Typesense MCP Server provides the following tools:

Server Management

  • check_typesense_health - Checks the health status of the configured Typesense server

  • list_collections - Retrieves a list of all collections in the Typesense server

Collection Management

  • describe_collection - Retrieves the schema and metadata for a specific collection

  • export_collection - Exports all documents from a specific collection

  • create_collection - Creates a new collection with the provided schema

  • delete_collection - Deletes a specific collection

  • truncate_collection - Truncates a collection by deleting all documents but keeping the schema

Document Operations

  • create_document - Creates a single new document in a specific collection

  • upsert_document - Upserts (creates or updates) a single document in a specific collection

  • index_multiple_documents - Indexes (creates, upserts, or updates) multiple documents in a batch

  • delete_document - Deletes a single document by its ID from a specific collection

  • import_documents_from_csv - Imports documents from CSV data into a collection

Search Capabilities

  • search - Performs a keyword search on a specific collection

  • vector_search - Performs a vector similarity search on a specific collection

Available Tools

14 tools
check_typesense_healthB
Checks the health status of the configured Typesense server.

Args:
    ctx (Context): The MCP context, providing access to application resources.

Returns:
    dict | str: The health status dictionary from Typesense or an error message.

Inputs: no named parameters.

create_collectionC
Creates a new collection with the provided schema.

Args:
    ctx (Context): The MCP context.
    schema (dict): The collection schema dictionary (must include 'name' and 'fields').

Returns:
    dict | str: The created collection schema dictionary or an error message string.

Inputs: schema (required).

create_documentC
Creates a single new document in a specific collection.

Args:
    ctx (Context): The MCP context.
    collection_name (str): The name of the collection.
    document (dict): The document data to create (must include an 'id' field unless auto-schema).

Returns:
    dict | str: The created document dictionary or an error message string.

Inputs: collection_name (required), document (required).

delete_collectionC
Deletes a specific collection.

Args:
    ctx (Context): The MCP context.
    collection_name (str): The name of the collection to delete.

Returns:
    dict | str: The deleted collection schema dictionary or an error message string.

Inputs: collection_name (required).

delete_documentA
Deletes a single document by its ID from a specific collection.

Args:
    ctx (Context): The MCP context.
    collection_name (str): The name of the collection.
    document_id (str): The ID of the document to delete.

Returns:
    dict | str: The deleted document dictionary or an error message string.

Inputs: collection_name (required), document_id (required).

describe_collectionC
Retrieves the schema and metadata for a specific collection.

Args:
    ctx (Context): The MCP context.
    collection_name (str): The name of the collection to describe.

Returns:
    dict | str: The collection schema dictionary or an error message string.

Inputs: collection_name (required).

export_collectionB
Exports all documents from a specific collection.

Warning: This can be memory-intensive for very large collections.

Args:
    ctx (Context): The MCP context.
    collection_name (str): The name of the collection to export.

Returns:
    list[dict] | str: A list of document dictionaries or an error message string.

Inputs: collection_name (required).

import_documents_from_csvA
Imports documents from CSV data (as a string) or a file path into a collection.
Assumes CSV header row maps directly to Typesense field names.
Does basic type inference for int/float, otherwise treats as string.

Args:
    ctx (Context): The MCP context.
    collection_name (str): The name of the collection.
    csv_data_or_path (str): Either the raw CSV data as a string or the path to a CSV file.
    batch_size (int): Number of documents to import per batch. Defaults to 100.
    action (str): Import action ('create', 'upsert', 'update'). Defaults to 'upsert'.

Returns:
    dict: A summary of the import process including total processed, successful, failed count, and any errors.

Inputs: collection_name (required), csv_data_or_path (required), action, batch_size.

index_multiple_documentsA
Indexes (creates, upserts, or updates) multiple documents in a batch.

Args:
    ctx (Context): The MCP context.
    collection_name (str): The name of the collection.
    documents (list[dict]): A list of document dictionaries to index.
    action (str): The import action ('create', 'upsert', 'update'). Defaults to 'upsert'.

Returns:
    list[dict] | str: A list of result dictionaries (one per document) or an error message string.
                     Each result dict typically looks like {'success': true/false, 'error': '...', 'document': {...}}.

Inputs: collection_name (required), documents (required), action.

list_collectionsC
Retrieves a list of all collections in the Typesense server.

Args:
    ctx (Context): The MCP context.

Returns:
    list | str: A list of collection schemas or an error message string.

Inputs: no named parameters.

truncate_collectionA
Truncates a collection by deleting all documents but keeping the schema.
Achieved by retrieving schema, deleting collection, and recreating it.

Args:
    ctx (Context): The MCP context.
    collection_name (str): The name of the collection to truncate.

Returns:
    str: A success or error message string.

Inputs: collection_name (required).

upsert_documentA
Upserts (creates or updates) a single document in a specific collection.

Args:
    ctx (Context): The MCP context.
    collection_name (str): The name of the collection.
    document (dict): The document data to upsert (must include an 'id' field).

Returns:
    dict | str: The upserted document dictionary or an error message string.

Inputs: collection_name (required), document (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool has a distinct purpose with clear boundaries. For example, create_document vs. upsert_document vs. index_multiple_documents cover different single/batch operations, while search vs. vector_search target different search methods. No tools appear to duplicate functionality.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case throughout (e.g., create_collection, delete_document, list_collections). The naming convention is predictable and matches the action-resource structure of the Typesense API domain.

    Tool Count5/5

    With 14 tools, this server provides comprehensive coverage for a search engine/database server. The count is well-scoped for the domain, offering health checks, collection management, document CRUD operations, search capabilities, and data import/export without being overwhelming.

    Completeness5/5

    The tool set provides complete coverage for Typesense operations, including health monitoring, full collection lifecycle (create/describe/list/delete/truncate), document operations (create/upsert/delete/batch import/indexing), and both keyword and vector search capabilities. No obvious gaps exist for core search engine functionality.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server providing vector database capabilities through Chroma, enabling semantic document search, metadata filtering, and document management with persistent storage.
      6
      41
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables semantic search capabilities by providing tools to manage Qdrant vector database collections, process and embed documents using various embedding services, and perform semantic searches across vector embeddings.
      4
      62 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides AI assistants with direct access to local document collections through full-text search, supporting multiple formats and hierarchical collections.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A local-first semantic search server for documents, supporting PDFs, Office files, and text/markdown, enabling natural language search via the Model Context Protocol (MCP).
      1
      MIT