Integration

Typesense integration

Lightning-fast, open-source search engine with typo tolerance. Build powerful search experiences with instant results, faceted navigation, geo-search, and semantic search. Index and search documents with real-time updates, multi-collection search, and advanced ranking. Features include full-text search with typo correction, vector search for AI applications, geolocation queries, collection aliases for zero-downtime reindexing, and built-in analytics. Perfect for e-commerce search, site search, and any application requiring fast, relevant search results with minimal configuration.

Connect Typesense How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Typesense.Built from the 38 Typesense tools below, on the connection you add once.

Common Typesense use cases

admin dashboards
cleanup unused rules
configuration auditing
monitoring
key management
rule management
search analytics
inventory management
data backup
detail pages

What you can do with Typesense

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Document, 9 operations

delete_documentDelete documentDELETEDeletes a single document from a Typesense collection by its ID. The document is permanently removed and no longer appears in search results. Use ignore_not_found=true to avoid errors if document doesn't exist.
delete_documents_by_queryDelete documents by queryDELETEDeletes all documents matching a filter query. Returns the count of deleted documents. Use filter_by to specify matching criteria. Control performance with batch_size.
export_documentsExport documentsGETExports documents from a Typesense collection in JSONL format. Stream large datasets efficiently. Filter with filter_by and control fields with include_fields/exclude_fields.
get_documentGet documentGETRetrieves a single document from a Typesense collection by its ID. Returns the complete document unless include_fields/exclude_fields limit the response. Use for fetching document details or verifying indexed content.
import_documentsImport documentsPOSTBulk imports multiple documents into a Typesense collection. Uses JSONL format (one JSON object per line) for efficient streaming. Returns per-document success/failure status.
index_documentIndex documentPOSTAdds a new document or replaces an existing document in a Typesense collection. Use action=upsert for create-or-replace, action=update for partial updates. Document must match collection schema.
searchSearchGETSearches a Typesense collection for matching documents. Returns hits with relevance ranking, highlighting, and optional facet counts. Supports typo-tolerance, filters, sorting, and pagination. Use query_by to specify searchable fields and facet_by...
update_documentUpdate documentPATCHPartially updates an existing document by specifying only the fields to modify. Unspecified fields are preserved. More efficient than full replacement when updating individual fields.
update_documents_by_queryUpdate documents by queryPATCHPartially updates all documents in a Typesense collection that match a filter_by expression. Sends field changes as JSON body and applies them to every matching document. Returns the count of updated documents.

Collection, 5 operations

create_collectionCreate collectionPOSTCreates a new Typesense collection with a defined schema. Specify field names, types, and properties like faceting and sorting. Field types include string, int32, int64, float, bool, geopoint, object, auto, image, and array variants. Returns the c...
delete_collectionDelete collectionDELETEPermanently deletes a Typesense collection and all its documents. This operation cannot be undone. Use with caution in production environments.
get_collectionGet collectionGETRetrieves the schema and configuration of a specific Typesense collection. Returns field definitions, types, and settings. Use to verify collection exists or check configuration before operations.
list_collectionsList collectionsGETLists all collections in your Typesense instance with their schemas. Returns name, fields, and configuration for each collection. Use exclude_fields to omit field definitions for faster response.
update_collectionUpdate collectionPATCHUpdates a collection schema by adding new fields or dropping existing fields. Set drop=true on a field to remove it. New fields must have optional=true since existing documents won't have values.

Alias, 4 operations

create_aliasCreate aliasPUTCreates or updates a collection alias pointing to a specific collection. Aliases enable zero-downtime reindexing by swapping the underlying collection without changing application code.
delete_aliasDelete aliasDELETEDeletes a collection alias. The underlying collection and its documents are not affected. Applications using the alias will need to be updated to use the actual collection name.
get_aliasGet aliasGETRetrieves information about a collection alias including the collection it points to. Use to verify alias configuration or check current collection mapping.
list_aliasesList aliasesGETLists all collection aliases in your Typesense instance. Returns each alias name and the collection it points to. Essential for alias inventory and management.

Key, 4 operations

create_api_keyCreate api keyPOSTCreates a new API key with specified permissions and collection access. Define actions (allowed operations), collections (accessible collections with wildcard support), and optional expiration. Returns the full key value (only visible at creation).
delete_api_keyDelete api keyDELETEPermanently deletes an API key. The key can no longer be used for authentication. Use for revoking access or cleaning up unused keys.
get_api_keyGet api keyGETRetrieves metadata about an API key including description, actions, collections, and expiration. The key value is partially masked for security (only prefix shown).
list_api_keysList api keysGETLists all API keys in your Typesense instance. Returns key metadata including description, actions, collections, and expiration. Key values are partially masked.

Override, 4 operations

create_overrideCreate overridePUTCreates or updates a curation override (merchandising rule) that promotes, excludes, or dynamically filters/sorts results for specific search queries.
delete_overrideDelete overrideDELETEDeletes a curation override rule from a Typesense collection. The override no longer affects search results after deletion.
get_overrideGet overrideGETRetrieves a specific curation override rule by ID. Returns rule configuration including trigger conditions and include/exclude lists.
list_overridesList overridesGETLists all curation override rules for a Typesense collection. Use for auditing merchandising configuration or building admin interfaces.

Synonym, 4 operations

create_synonymCreate synonymPUTCreates or updates a synonym rule for a Typesense collection. Use multi-way synonyms for equivalent terms or one-way synonyms to map terms to a root word.
delete_synonymDelete synonymDELETEDeletes a synonym rule from a Typesense collection. The synonym no longer affects search queries after deletion.
get_synonymGet synonymGETRetrieves a specific synonym rule by ID from a Typesense collection. Returns the synonym terms and root word configuration.
list_synonymsList synonymsGETLists all synonym rules configured for a Typesense collection. Use for auditing synonym configuration or building admin interfaces.

Analytics rule, 3 operations

create_analytics_ruleCreate analytics rulePOSTCreates an analytics rule for tracking search behavior. Define popular_queries rules to aggregate frequently searched terms, nohits_queries to track zero-result searches, or counter rules to track document popularity via events.
delete_analytics_ruleDelete analytics ruleDELETEDeletes an analytics rule. Stops further analytics collection but data already aggregated in destination collection is preserved.
list_analytics_rulesList analytics rulesGETLists all configured analytics rules in your Typesense instance. Returns rule names, types, and configurations.

Analytics event, 1 operation

send_analytics_eventSend analytics eventPOSTSends an analytics event for tracking search behavior and document popularity. Event types include search, click, conversion, and visit. Use with analytics rules for query suggestions and popularity tracking.

Health, 1 operation

healthHealthGETChecks the health status of a Typesense node. Returns ok when the node is healthy. Does not require API key authentication. Use for load balancer health checks.

Metric, 1 operation

get_metricsGet metricsGETRetrieves system metrics for the Typesense node including CPU, RAM, disk, and network usage. Essential for monitoring and capacity planning.

Multi search, 1 operation

multi_searchMulti searchPOSTExecutes multiple search queries in a single API call across one or more collections. Each query can have different parameters. Perfect for federated search, multi-category queries, or reducing API calls.

Stat, 1 operation

get_statsGet statsGETRetrieves API statistics including average requests per second and latency for all endpoints over the last 10 seconds. Use for real-time performance monitoring.

Use Typesense from Claude Code, Cursor or Codex

Connect Typesense in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Typesense operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Typesense

Create your workspace
Sign up free. Nothing to install.
Connect Typesense once
Add your Typesense connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Typesense integration FAQ

What can you do with the Typesense integration?

LiveContext exposes 38 operations on Typesense, covering document, collection, alias and key. Common uses include admin dashboards, cleanup unused rules and configuration auditing.