by Typesense
Updated October 19, 2026
MCP100 verdict
Not currently recommended. Shortlist — editorially admitted, not a Recommended endorsement.
MCP100 Assessment
Editorial verdict
Reviewed October 19, 2026
Task Fit
Mapped
Specialized workflows
Trust
Status warning
Prefer Search only permissions; key auth does not enable full data tools
Maintenance
Date unavailable
No dated repository or package update is currently stored.
Popularity
Signals unavailable
No independently comparable adoption metric is currently stored.
Evidence scope
No MCP-specific repository metric is stored
No MCP-specific package metric is stored
Stars observed October 20, 2026 · Downloads observed October 20, 2026
Typesense Cloud MCP is a hosted service. No current first-party public repository containing the hosted server implementation was verified.
Typesense Cloud MCP is hosted; no exact public installable MCP package was verified.
Publisher activity observed October 19, 2026
Current source snapshot
Source relationship: First-party MCP
Reviewed October 19, 2026
Evidence-backed setup
Choose your MCP client. A client connects to the MCP server; the language model is selected inside that client. Only stored, source-backed configurations are shown.
Transport not recorded
Complete client-specific setup, verification and removal are not documented in this reviewed source.
Publisher-documented setup is not the same as MCP100 execution testing. “MCP100 logic checked” means the stored configuration shape was reviewed, not that third-party MCP software was run.
Evidence checked 2026-10-19
Type-appropriate, source-backed setup for this mcp server profile.
{"url":"https://cloud.typesense.org/mcp/v1"}Capability
Typesense Cloud MCP is a Typesense MCP integration for typesense cloud clusters, collections, search indexing and monitoring. Use for teams operating hosted Typesense Search. Cluster provisioning, schema changes and indexing can cost money or change production data.
Permissions determine tool surface; preset and OAuth capability dependent
Not measured yet
Estimated token footprint of the MCP tool schemas exposed to the agent.
https://cloud.typesense.org/mcp/v1
Reviewed access
Related reviewed MCPs
Let AI clients inspect and automate web browsers with Playwright.
Choose this instead if
Choose Playwright MCP instead if inspecting and testing web interfaces through accessibility snapshots.
Let AI clients inspect and automate web browsers with Playwright.
Use Stripe's remote MCP endpoint for supported payment workflows.
Choose this instead if
Choose Stripe MCP instead if searching Stripe documentation and support knowledge from an MCP client.
Use Stripe's remote MCP endpoint for supported payment workflows.
Manage and search Redis data through Redis's MCP server.
Choose this instead if
Choose Redis MCP instead if inspecting and manipulating Redis strings, hashes, lists, sets, sorted sets, streams, JSON, and search indexes.
Manage and search Redis data through Redis's MCP server.
Typesense is listed as First-party MCP in MCP100’s current evidence.
Current official resources:
Original product, capability, tool, and usage documentation from the MCP publisher. Installation sections appear under Install & Agents.
Title: Typesense Cloud MCP Server | Typesense
URL Source: https://typesense.org/docs/guide/typesense-cloud/mcp-server.html
Published Time: Fri, 02 Oct 2026 00:02:21 GMT
Markdown Content: Connect your AI agent to Typesense Cloud and it can create and configure clusters, build collections, index your data, tune search and read metrics, all from the conversation. You decide what it is allowed to do when you connect it, and you can disconnect it at any time.
Add the Typesense Cloud MCP server to your AI Agent:
It is a remote MCP server over Streamable HTTP with OAuth, so any client that supports those works.
Here are instructions for common agents:
Claude Code:
Then open a new Claude Code session, type /mcp, select the typesense-cloud MCP you just added, and select "Authenticate"
Codex CLI:
Codex reads your project's AGENTS.md every turn. Add this line to it so Codex reaches for Typesense Cloud instead of asking you for keys:
Cursor (mcp.json, MCP setup docs(opens new window)):
claude.ai and Claude Desktop (custom connector docs(opens new window)):
Go to Customize, then Connectors, then Add custom connector, and paste this URL: https://cloud.typesense.org/mcp/v1
ChatGPT (MCP setup docs(opens new window)):
In the ChatGPT desktop app, go to Settings, then Plugins, then MCP, then Add, then Add MCP Server. Name it "Typesense Cloud", set the type to Streamable HTTP and the URL to https://cloud.typesense.org/mcp/v1, and save.
Then ask: "Using Typesense Cloud MCP, show me my clusters."
Other Clients:
Any other client that supports MCP over Streamable HTTP with OAuth works the same way.
Once you add the MCP Server, follow your client's instructions to authenticate the MCP Server.
Your browser will open a Typesense Cloud consent page.
Sign in (or sign up), choose the account the agent should work on, choose what permissions it has, and click Connect.
If you're part of a team account, the permissions in the consent screen will be capped at permissions your RBAC role in your team account already gives you. So for eg: someone on your team with a curator role, connecting their agent, will only be able to add permissions for searching and curation, and not any of the other permissions.
TIP
Once connected, paste this into your agent:
The agent creates a free-tier cluster, asks what your data looks like, proposes a schema, imports the data and runs a search you can check. From there, ask your agent for what you need. Here are some examples for inspiration:
Working with your data:
products.jsonl"products collection and a few sample documents"brand as a facet field to the products collection"products_live alias at the products_v2 collection"orders where status:=cancelled"orders collection to a file"Searching:
products and articles for trail running in one call and show me the top three of each"articles for getting started with vector search"brand and show me two per brand"Tuning search results:
created_at descending"sneakers"sneakers also matches trainers"title but none on sku"the, a and an as stopwords for the articles collection"storefront"products so people can type cheap red shoes for kids"docs collection"Search Typesense docs:
The MCP server will automatically query the docs for the version your Typesense Cloud cluster is running on
drop_tokens_threshold do and what should I set it to?"Managing your cluster's infrastructure:
max-per-page to 500 on this cluster"staging-old cluster"Analyzing your billing data:
When you connect your agent, the permissions page shows five presets:
| Preset | The agent can |
|---|---|
| Search only | Search collections and read schemas, list clusters. |
| Search and curate | Search, plus synonyms, curation, presets and stopwords, plus list clusters. |
| Manage clusters | Create, resize, rename and tune clusters. No access to the data inside them. |
| Build (default) | Manage clusters and everything inside them. No terminating, cloning or billing; the only key it can create is a search-only cluster key for an app. |
| Everything | Every capability your role allows, including terminating clusters. |
You can also enable or disable individual permissions. Cluster permissions are the same ones a Cluster Management API key can carry:
clusters:read: list clusters and read their configuration, status, history and server parametersmetrics:read: read cluster metricsclusters:create: create clusters (billed to the account)clusters:configure: resize, change topology, rename and toggle auto-upgrade (billable changes)cluster_parameters:manage: change Typesense server parameters (no billing impact)clusters:clone: clone clusterscluster_credentials:issue: issue cluster API keysbilling:read: read invoicesclusters:terminate: terminate clustersData permissions match the cluster UI dashboard's permissions:
data:view: read collections, schemas, documents and aliasesdata:search: search, and create a search-only cluster key for an app (if your role manages keys)data:full_access: create, change and drop collections; add, update and delete documents; manage aliasesdata:manage_synonyms, data:manage_overrides (curation), data:manage_presets, data:manage_stopwords, data:manage_stemmingdata:manage_analytics_rules, data:manage_conversation_models, data:manage_natural_language_modelsEvery tool is offered to every connection; but each tool call is checked against the permissions you granted, and a refused call tells the agent which permission it is missing so it can ask you for it. To widen a connection, disconnect the MCP Server from your agent, then re-add and re-authenticate. You'll see the consent screen again, where you'll be able to select the new set of permissions.
The tools that change things (manage_cluster, documents and change_cluster_data) are marked destructive, so clients that honor that annotation ask you before running them.
On a team account you can only grant what your own role allows. Options your role does not cover are greyed out with the reason.
These are the tools available for your agent to use once it is connected. Agents read the tool descriptions, so you do not need to name tools or actions in your prompts; this list is here so you know what is possible.
whoami: which account and permissions the connection has, the clusters on the account, and what to do with them first. Agents call it first.search_typesense_docs: searches this documentation, matched to your cluster's Typesense version.search_documents: searches a collection, including multi-search and vector or hybrid queries.get_clusters: lists clusters and reads configuration, status, metrics, configuration-change and cloning history, server parameters and invoices, plus the regions, memory and vCPU options a cluster can be created with.manage_cluster: creates, renames, resizes, tunes, clones and terminates clusters, and issues cluster API keys.documents: indexes, updates, fetches, deletes, imports and exports documents.read_cluster_data and change_cluster_data: everything else in the Typesense Server API by path: collections, aliases, synonyms, curation, presets, stopwords, stemming dictionaries, analytics, and conversation and natural language search models.submit_feedback: lets the agent tell the Typesense Cloud team about a paper cut it hit, such as a tool that refused something that should work or a missing action. The team reads every submission; nobody replies through the tool, so for anything blocking you, contact support(opens new window).Typesense Cloud performs data operations against your cluster with a key it keeps server-side. The agent does not receive your cluster's admin key.
The agent imports up to 1,000 documents or 10 MB in one call. For anything larger, and for every export, it receives a curl command to run on your machine instead, so the data moves directly between your machine and the cluster. The command uses a temporary key that Typesense Cloud creates for that one job: scoped to that collection and that action, valid for 24 hours, fetched once into a private file on your machine.
Browser-based assistants such as claude.ai and ChatGPT cannot run commands, so their imports stay within the inline limit.
A new account can create a free-tier cluster (0.5 GB memory, 2 vCPU burst, one node) without a payment method. Creating anything beyond the free tier needs a payment method on the account, or enough prepaid credit for a new cluster. Changing a cluster's configuration or cloning it needs a payment method or a positive prepaid credit balance. Upgrading the Typesense server version is exempt, and free-tier clusters can always take it. The agent tells you when a payment method is needed and can offer to test with a subset of your data that fits the free tier.
Each connection gets 300 data calls (search, documents, reads and writes) per minute and 30 cluster-management actions per minute, the same as the Cloud Management API.
An agent on a server, in CI, or anywhere it cannot open a browser can use a Cluster Management API key as the bearer token on the same URL:
Use the key exactly as it was shown when you created it. A key unlocks the cluster tools (whoami, search_typesense_docs, get_clusters and manage_cluster) with the capabilities the key carries; the data tools act as a signed-in person, so they need the browser connection. A headless agent provisions the cluster and issues its keys over MCP, then works with the data through the Typesense Server API directly.
manage_cluster can issue a cluster's admin key and search-only key, both covering every collection and neither expiring. The keys do not appear in the conversation: the agent receives a curl command that downloads them once, within five minutes, into a private file on your machine, and reads a key from that file when it needs one. An assistant with no shell, such as claude.ai or ChatGPT, can ask for the keys inline in the response instead.
Keep the admin key on your server and give applications the search-only key. A connection with data:search can also create a search-only key for an application directly on the cluster, if your role manages keys, so the Build preset covers "make my catalog searchable from my app" end to end without issuing an admin key.
For a key limited to certain collections, actions or an expiry, ask the agent to create one. If different users must see different parts of one collection, use a scoped search key.