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.
“It is a remote MCP server over Streamable HTTP with OAuth, so any client that supports those works.”
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.
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.
- 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"
}
}
}04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://typesense.org/docs/guide/typesense-cloud/mcp-server.html
Supports: summary, upstreamDescription, descriptionSourceUrl, configExample, install, access, whySelected, bestFor, limitations, transports, compatibility, review
https://typesense.org/docs/30.2/api/api-clients.html
Supports: whySelected, limitations