Typesense Cloud

MCP server by Typesense

Create and configure Typesense Cloud clusters, build collections, index data, tune search and read metrics from your assistant.

OAuth sign-in (You sign in with the vendor the first time you connect)Streamable HTTP

Connect to Typesense Cloud

Typesense Cloud needs sign-in. Connect with its own URL:

https://cloud.typesense.org/mcp/v1

Your client opens Typesense’s sign-in the first time you use it. The token stays between your client and Typesense.

Share this server

Opens this page, with the URL and setup steps.

mcp.tc/i/typesense-cloud

About

Connects an AI assistant to Typesense Cloud, the hosted service for Typesense search. The assistant can create and configure clusters, build collections, index data, tune search settings such as synonyms, and read cluster metrics.

It runs as a hosted streamable HTTP endpoint at https://cloud.typesense.org/mcp/v1. Users sign in with OAuth and choose on a consent screen which permissions the agent gets, and can disconnect it at any time. Scopes cover cluster reads, creation, configuration, cloning, credentials, metrics and billing reads. A Typesense Cloud management API key can be used instead of OAuth.

What you can do

  • Create and configure Typesense Cloud clusters
  • Build collections and index data
  • Tune search, including synonyms
  • Read cluster metrics
  • Clone clusters and issue cluster credentials
  • Choose permissions on a consent screen when connecting

Tools

Typesense Cloud lists its tools only after you sign in, so we can’t show them here. Your client lists them once you’re connected.

Example prompts

  • Create a new Typesense Cloud cluster for my staging environment.

  • Create a products collection and import this JSON data into it.

  • Add synonyms for sneakers and trainers to my products collection.

  • Show me recent metrics for my production cluster.

Set up

Every client connects to cloud.typesense.org, and Typesense asks you to sign in the first time. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http typesense-cloud https://cloud.typesense.org/mcp/v1
  1. Start Claude Code, type /mcp, pick typesense-cloud and choose Authenticate. A browser window opens for the Typesense sign-in.

Add --scope user to make it available in every project, not just this one.

Claude Desktop

  1. Open Settings → Connectors and click Add custom connector.
  2. Name it Typesense Cloud and paste this URL:
https://cloud.typesense.org/mcp/v1
  1. Click Add, then Connect, and sign in when Typesense asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

claude.ai

  1. Open the connector form on claude.ai. This button fills in the name and URL for you:
  1. Check that the URL reads https://cloud.typesense.org/mcp/v1 and click Add.
  2. Click Connect and sign in when Typesense asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.

ChatGPT

  1. On chatgpt.com, open Settings → Security and login and turn on Developer mode.
  2. Go to chatgpt.com/plugins and click + to create an app for a remote MCP server.
  3. Paste https://cloud.typesense.org/mcp/v1 as the server URL and choose OAuth. ChatGPT sends you to Typesense to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "typesense-cloud": {
      "url": "https://cloud.typesense.org/mcp/v1"
    }
  }
}

Cursor shows Needs login next to the server. Click it to sign in.

VS Code

Or from a terminal:

code --add-mcp '{"name":"typesense-cloud","type":"http","url":"https://cloud.typesense.org/mcp/v1"}'

Or commit it to the repo in .vscode/mcp.json:

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

VS Code asks you to sign in the first time the server starts.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "typesense-cloud": {
      "serverUrl": "https://cloud.typesense.org/mcp/v1"
    }
  }
}
  1. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

codex mcp add typesense-cloud --url https://cloud.typesense.org/mcp/v1
codex mcp login typesense-cloud

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.typesense-cloud]
url = "https://cloud.typesense.org/mcp/v1"

Gemini CLI

gemini mcp add --transport http typesense-cloud https://cloud.typesense.org/mcp/v1

Then, inside Gemini CLI, run /mcp auth typesense-cloud to sign in.

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.

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

Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.

Client only starts local servers? Bridge it with npx -y mcp-remote https://cloud.typesense.org/mcp/v1.

FAQ

Can I paste mcp.tc/i/typesense-cloud into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://cloud.typesense.org/mcp/v1, so your client talks to Typesense Cloud directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.

Does Typesense Cloud need an API key or a sign-in?

Yes, you need a Typesense account. The first time your client connects, it opens Typesense’s sign-in page. The token goes straight to the server’s own URL, never through mcp.tc.

Is Typesense Cloud a remote or a local server?

Remote. Typesense hosts it at https://cloud.typesense.org/mcp/v1, and it speaks Streamable HTTP. There’s nothing to install.

What can Typesense Cloud do?

You can create and configure Typesense Cloud clusters, build collections and index data and tune search, including synonyms.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Who wrote this page?

mcp.tc’s robot read Typesense Cloud’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

Embed

Show Typesense Cloud in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work

README badge

Badge preview, lightBadge preview, dark
Markdown
[![Typesense Cloud on mcp.tc](https://mcp.tc/i/typesense-cloud/badge.svg)](https://mcp.tc/i/typesense-cloud)
HTML
<a href="https://mcp.tc/i/typesense-cloud"><img src="https://mcp.tc/i/typesense-cloud/badge.svg" alt="Typesense Cloud on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/typesense-cloud.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/typesense-cloud" title="Typesense Cloud on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/typesense-cloud.json

What each field means

mcp.tc isn’t affiliated with Typesense. This page was built from Typesense Cloud’s public metadata, last checked on 3 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.