---
title: "Typesense Cloud MCP Server: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/typesense/
description: "Typesense's hosted MCP server for Typesense Cloud: agents create and configure clusters, build collections, import data, tune search and read metrics over Streamable HTTP with OAuth, with consent-screen permissions capped at the user's RBAC role."
---

# Typesense Cloud MCP Server: review, setup & limitations · Undominated.ai

> Typesense's hosted MCP server for Typesense Cloud: agents create and configure clusters, build collections, import data, tune search and read metrics over Streamable HTTP with OAuth, with consent-screen permissions capped at the user's RBAC role.

[← Explore all mcp servers](/mcp-servers/)

SEARCH AND ANALYTICS / Typesense

# Typesense Cloud MCP Server

Typesense's hosted MCP server for Typesense Cloud: agents create and configure clusters, build collections, import data, tune search and read metrics over Streamable HTTP with OAuth, with consent-screen permissions capped at the user's RBAC role.

 [See setup guidance ↓](#setup)[Original source ↗](https://typesense.org/docs/guide/typesense-cloud/mcp-server.html)

SOURCE REVIEW

 Reviewed 2026-10-13
 Evidence 2 linked sources
 Publisher Typesense
 Licence Not established
 [Read what was—and wasn’t—checked ↓](#review)

“It is a remote MCP server over Streamable HTTP with OAuth, so any client that supports those works.”

 [Typesense · upstream description ↗](https://typesense.org/docs/guide/typesense-cloud/mcp-server.html) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Typesense hosts its own Cloud MCP server, which manages clusters and the data inside them; its API clients page lists it as the official Typesense Cloud MCP server, separately from community implementations.
- On a team account the OAuth consent screen caps grantable permissions at the signer's RBAC role, and every connection is listed and revocable under Connected apps with an owner email on approval: a documented permission lifecycle.

### A good fit for

 - Provisioning and iterating on a Typesense Cloud cluster conversationally: create a free-tier cluster, propose a schema, import data and run searches.
- Tuning search behaviour — synonyms, curation pins, facet fields, typo tolerance — and reading cluster metrics without the dashboard.

### Weigh up before choosing

 - The server works on Typesense Cloud accounts and their clusters; the docs describe no way to point it at a self-hosted Typesense server.
- A connection is tied to one account; working across accounts means adding the server again under a different name.
- Every tool is offered to every connection and each call is checked against the granted permissions; the default Build preset can create and resize billable clusters, and the Everything preset can terminate clusters.
- Imports over 1,000 documents or 10 MB, every export and cluster-key retrieval come back as a curl command for the agent to run on the user's machine, writing a temporary or cluster key to a private local file.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - Typesense Cloud MCP documentation, read 2026-10-13: endpoint https://cloud.typesense.org/mcp/v1 over Streamable HTTP with OAuth; per-client setup; the consent screen's five presets and individual permissions, capped at the team RBAC role; Connected apps and owner emails; the tool list; large imports and exports; free tier and billing; rate limits; headless use with a Cluster Management API key; cluster API keys.
- Typesense API clients documentation: lists the official Typesense Cloud MCP server as hosted by Typesense Cloud, managing clusters and the data inside them, alongside community implementations.

### Our findings

 - The publisher distinguishes its hosted server from community implementations explicitly in its API clients page, naming it the official Typesense Cloud MCP server.
- The documented tools are whoami, search_typesense_docs, search_documents, get_clusters, manage_cluster, documents, read_cluster_data, change_cluster_data and submit_feedback. manage_cluster, documents and change_cluster_data are marked destructive, so clients that honour the annotation ask before running them.
- Typesense Cloud runs data operations with a key it keeps server-side; the agent does not receive the cluster admin key unless it asks manage_cluster to issue one, which arrives as a one-time download into a private file (inline for assistants without a shell).
- Each connection gets 300 data calls and 30 cluster-management actions per minute. Without a browser, a Cluster Management API key as Bearer token unlocks only the cluster tools; the data tools need the OAuth connection.
- configExample is the docs' Cursor mcp.json block. Corrected 2026-10-13: the earlier example added a "type": "http" key the docs do not show, and whySelected leaned on a claim about community servers that no cited page makes.

### Not established by this review

 - No Typesense Cloud account was connected and no cluster, collection or search operation was executed.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

[Upstream setup instructions ↗](https://typesense.org/docs/guide/typesense-cloud/mcp-server.html)
 - Add https://cloud.typesense.org/mcp/v1 as a remote MCP server in the client.
- Complete the OAuth consent in the browser: choose the account, choose the permissions, and connect.
- Ask the agent to show your clusters to verify the connection.

### Before you start

 - A Typesense Cloud account (a free tier is available).
- An MCP client supporting Streamable HTTP with OAuth.

### Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

 {
 "mcpServers": {
 "typesense-cloud": {
 "url": "https://cloud.typesense.org/mcp/v1"
 }
 }
} Copy configuration ↗

### Compatibility

Claude Code, Codex CLI, Cursor, claude.ai and Claude Desktop custom connectors, and ChatGPT, per the publisher's per-client instructions. · Any MCP client supporting Streamable HTTP with OAuth.

### Transports

Streamable HTTP

### Typesense Cloud OAuth

 - Grantable permissions are capped at the signer's RBAC role in the team account; the consent screen offers five presets (Search only, Search and curate, Manage clusters, Build as default, Everything) or individual cluster and data permissions.
- Each connection is listed under Connected apps, can be disconnected at any time, and triggers an owner email on approval.
- Cluster permissions include billable creates and configuration changes, cloning, issuing cluster API keys, reading invoices and terminating clusters; data permissions range from view and search to full collection and document writes.

### Cost model

Requires a Typesense Cloud account; a free-tier cluster needs no payment method, while larger clusters, configuration changes and clones need a payment method or prepaid credit and are billed to the account.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Typesense Cloud MCP Server documentation ↗](https://typesense.org/docs/guide/typesense-cloud/mcp-server.html) Checked 2026-10-13 https://typesense.org/docs/guide/typesense-cloud/mcp-server.html Supports: summary, upstreamDescription, descriptionSourceUrl, configExample, install, access, whySelected, bestFor, limitations, transports, compatibility, review
- [Typesense API clients page listing the official MCP server ↗](https://typesense.org/docs/30.2/api/api-clients.html) Checked 2026-10-13 https://typesense.org/docs/30.2/api/api-clients.html Supports: whySelected, limitations

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Algolia MCP Server ↗ Algolia's managed MCP offerings: Public MCP exposes application-scoped search and recommendations on selected indices for customer-facing agents; Productivity MCP gives user-scoped, read-only exploration and analytics; DevEx MCP serves version-matched API client snippets to coding agents without touching data.](/mcp-servers/algolia/)[### OpenSearch MCP Server ↗ Lets an assistant list indices, read mappings, run searches and call any OpenSearch API through one generic tool, against one or several clusters. The Python implementation supports stdio and a streaming transport (SSE and Streamable HTTP) at the pinned revision.](/mcp-servers/opensearch/)[### Elastic Agent Builder MCP ↗ Exposes an Elastic Agent Builder tool catalog to external MCP clients through a chosen Kibana space.](/mcp-servers/elastic-agent-builder/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
