# Typesense Cloud MCP server > Create and configure Typesense Cloud clusters, build collections, index data, tune search and read metrics from your assistant. - Listing: https://mcp.tc/i/typesense-cloud - Connect: use the server's own URL `https://cloud.typesense.org/mcp/v1` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: OAuth sign-in - Category: [Databases & Backend](https://mcp.tc/c/databases) - Vendor: Typesense - Homepage: - Docs: ## 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 it 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 ## 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." ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http typesense-cloud https://cloud.typesense.org/mcp/v1 ``` 2. 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: ```url https://cloud.typesense.org/mcp/v1 ``` 3. 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: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://cloud.typesense.org/mcp/v1` and click **Add**. 3. 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 [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```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 [Install in VS Code]() (opens VS Code) Or from a terminal: ```bash 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`: ```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`: ```json { "mcpServers": { "typesense-cloud": { "serverUrl": "https://cloud.typesense.org/mcp/v1" } } } ``` 2. 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 ```bash 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`: ```toml [mcp_servers.typesense-cloud] url = "https://cloud.typesense.org/mcp/v1" ``` ### Gemini CLI ```bash 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. ```json { "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`. ## Details - Server version: 1.0.1 - Last checked: 2026-10-03 (reachable, asks for credentials) - Listed: 2026-10-03 - Updated: 2026-10-03 --- Source: https://mcp.tc/i/typesense-cloud (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report