Developer · Remote MCP server
Typesense Cloud
Add fast, typo-tolerant search to your site or app, and run the Typesense clusters behind it.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
org.typesense/typesense-cloud- Version
- 1.0.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-10
- Updated
- 2026-09-10
- Publisher
- org.typesense
- Namespace
- Namespace verified by the MCP Registry via the domain typesense.org · how
- Website
- typesense.org/docs/guide/typesense-cloud/mcp-server.html
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://cloud.typesense.org/mcp/v1 | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Typesense Cloud
Typesense Cloud is a remote MCP server: there is nothing to install. Its endpoint is https://cloud.typesense.org/mcp/v1, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| TVWizardControl Android TV from any AI. 38 MCP tools: playback, recap, recommend, -home, schedules. | Remote · HTTPLive check: ✗ no handshake |
| TwiceshyExperience memory for coding agents: validated traps, fixes and dead-ends at decision time. | Remote · HTTPLive check: ✗ no handshake |
| Type AtlasEditor-grade TypeScript, Markdown, and JSON intelligence for coding agents. | Local · stdio |
| TypeDBExecute TypeQL queries and manage databases and users on a TypeDB server. | Local · HTTP |
| TypeshipGenerate a typed SDK, CLI, and MCP server from any OpenAPI or GraphQL spec, and keep them current. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| TypestateBuild and run a backend from plain English. Data, logic, endpoints, auth and jobs, deployed live. | Remote · HTTPLive check: ✓ handshake |
| TypeUIDesign systems, UI prompts, and layout variations for AI coding tools. | Remote · HTTPLive check: sign-in required |
| TyrekickRead and resolve human feedback pinned on your live prototype, straight from your coding agent. | Local · stdio |