Typesense Cloud

org.typesensePublished by typesense.orgOfficial publisherv1.0.1Updated Oct 24, 2026

Add fast, typo-tolerant search to your site or app, and run the Typesense clusters behind it.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingCloud & Infrastructure

Overview

AI-generated overview

Lets an assistant add typo-tolerant search to an app and manage the Typesense Cloud clusters behind it.

What you can do
This remote MCP server connects an assistant to Typesense Cloud, a hosted search service. According to its description, it lets you add fast, typo-tolerant search to a site or app and run the Typesense clusters behind it. No individual tools are listed in the supplied information, so the exact operations available are not documented here.
When to use it
Consider it when you are building or maintaining search for a site or application on Typesense Cloud and want an assistant to help with search setup or cluster management. It is less relevant if you do not use Typesense Cloud.
Requirements
A remote endpoint at cloud.typesense.org over streamable HTTP. No packages, environment variables, or headers are declared, but the manifest declares no authentication, so account access and credentials for Typesense Cloud are not described in the supplied information.
Before you install
The manifest declares no authentication and no headers, so it is unclear how access to your Typesense Cloud account is controlled. Cluster operations may change or delete data, and search configuration may affect a live service. Confirm the actual authentication and permissions before connecting.

Installation

In SourceWeft

  1. Open Typesense Cloud in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/org.typesense%2Ftypesense-cloud/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "typesense-cloud": {
      "type": "http",
      "url": "https://cloud.typesense.org/mcp/v1"
    }
  }
}

Tools

2

create_claimable_cluster

Create a free cluster without an account

Creates a free-tier cluster (0.5 GB memory, 2 vCPU burst, one node) with no account and no credential, in the region nearest the caller unless one is given. The answer carries a claim_url for the person you are working with and an access_token for polling; when a ready cluster is on hand it also carries the hostname and an api_key, otherwise status is provisioning and next says what to do (poll get_claimable_cluster about every 60 seconds until ready, and tell the user you are waiting). The api_key reads, writes and searches every collection but cannot delete anything or manage keys; it stays valid for 24 hours after the person claims the cluster. The cluster is deleted 72 hours after creation unless a signed-in person opens the claim_url and claims it into their Typesense Cloud account: give them the link; never open it yourself. Limits per address: 2 clusters per hour, 5 per day.

Parametersregion

get_claimable_cluster

Get a claimable cluster's status

Pass the cluster_id from the create answer as id. Returns the cluster's status: provisioning (poll again in about 60 seconds), ready (with hostname and api_key, on every call until the person claims), claimed, or expired. Authenticate with the access_token from create_claimable_cluster as a bearer token. Limit: 120 calls per hour per cluster.

Parametersidrequiredaccess_tokenrequired

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Typesense integrations

TypesenseKit

Published by GitHub account typesensekit

A local MCP server that gives AI assistants typed tools to search, inspect schemas, manage collections and administer a Typesense cluster, read-only by default.

STDIODesktop only
DatabasesNot validated yetOct 24, 2026

TypesenseKit

Published by GitHub account akshitkrnagpal

Local MCP server exposing 95 typed Typesense operations so an assistant can search, inspect schemas, manage collections and administer a cluster.

STDIODesktop only
DatabasesNot validated yetOct 24, 2026