Typesense Cloud (BYOK)

Typesense Cloud (BYOK) — connector documentation

• MCP endpoint: https://byok-typesense-cloud.connectorbay.com/mcp
• REST API: POST https://byok-typesense-cloud.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-typesense-cloud.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Typesense Cloud Cluster Management API key (read-only preset is enough; the billing:read capability is needed for invoices), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-typesense-cloud.connectorbay.com/health · Tool schemas: https://byok-typesense-cloud.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-typesense-cloud · agent@connectorbay.com

What Typesense Cloud (BYOK) is for

Typesense Cloud (BYOK) lets an AI assistant read your own Typesense Cloud data through the Typesense Cloud API with a key you supply (Cluster Management API key (read-only preset is enough; the billing:read capability is needed for invoices)). Read-only: 10 tools (list_clusters, get_cluster, get_cluster_options, get_cluster_metrics, list_configuration_changes, get_configuration_change, list_cloning_operations, list_server_parameters, list_invoices, get_invoice). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to cloud.typesense.org. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Typesense Cloud. Typesense Cloud and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which Typesense Cloud clusters do I have and are they in service?"
• "Show the details and host names of my Typesense Cloud cluster"
• "Which regions and sizes does Typesense Cloud offer?"
• "What was the search latency of my Typesense Cloud cluster over the last hour?"
• "Is a capacity change scheduled for my Typesense Cloud cluster?"
• "What is the status of this Typesense Cloud configuration change?"

What it does

• list_clusters: List the Typesense Cloud clusters of the account with size, regions, version, high availability, status and runtime hours. Needs the clusters:read capability.
• get_cluster: Get one Typesense Cloud cluster: size, regions, node counts, host names, version, bandwidth usage and status.
• get_cluster_options: List the values a Typesense Cloud cluster can be created with: regions and their availability, memory and vCPU options, GPU, high availability and the free tier configuration.
• get_cluster_metrics: Get per-node metric series for one cluster (CPU, memory, disk, search latency, request rates). Up to five metrics at once; needs the metrics:read capability.
• list_configuration_changes: List the scheduled and past configuration changes (resize, version upgrade, topology) of one cluster with old and new values and status.
• get_configuration_change: Get one configuration change of a cluster by ID with its old and new settings, schedule and status (pending, in_progress, canceled, succeeded, failed).
• list_cloning_operations: List the cloning operations of one cluster with status, source and target region, version and the ID of the new cluster.
• list_server_parameters: List the user-editable Typesense server configuration parameters set on a cluster (name and value).
• list_invoices: List Typesense Cloud invoices with number, status, amount in cents, billing period and payment split. Needs the billing:read capability.
• get_invoice: Get one Typesense Cloud invoice with its line items (node hours, bandwidth) and prices in cents. Needs the billing:read capability.

BYOK key

You bring your own Typesense Cloud Cluster Management API key (read-only preset is enough; the billing:read capability is needed for invoices) (https://cloud.typesense.org/account). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to cloud.typesense.org over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://typesense.org/docs/cloud-management-api/v1/ (the API this connector calls, with a BYOK key)

Live from the Typesense Cloud API (cloud.typesense.org) with a BYOK key; documentation: https://typesense.org/docs/cloud-management-api/v1/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Typesense Cloud. Typesense Cloud and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Typesense Cloud account.

Built for: Worldwide. Languages: English.

Typesense Cloud (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Typesense Cloud (BYOK) is. Typesense Cloud (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Typesense Cloud data: Read your Typesense Cloud search clusters, capacity options, metrics, configuration changes, cloning history and invoices with your own cluster management API key. You bring your own Typesense Cloud Cluster Management API key (read-only preset is enough; the billing:read capability is needed for invoices); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Typesense Cloud call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to cloud.typesense.org, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Typesense Cloud rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Typesense Cloud receives. The request we make on your behalf, including the key and the arguments, under Typesense Cloud's own terms and privacy policy. Typesense Cloud acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Typesense Cloud gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Typesense Cloud data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Typesense Cloud (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Typesense Cloud at any time to end all access.

Children. Typesense Cloud (BYOK) is a general-audience service operated by the adult using the assistant, under Typesense Cloud's own age rules.

Changes. We will post changes here with a new effective date.

Typesense Cloud (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Typesense Cloud (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Typesense Cloud (BYOK) provides: Read your Typesense Cloud search clusters, capacity options, metrics, configuration changes, cloning history and invoices with your own cluster management API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Typesense Cloud credentials and only access data you are allowed to access. Typesense Cloud's terms apply to your use of Typesense Cloud; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Typesense Cloud. Typesense Cloud and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Typesense Cloud returns, lightly trimmed; it may be incomplete, delayed or changed by Typesense Cloud. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Typesense Cloud account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Typesense Cloud's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Typesense Cloud may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Typesense Cloud key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Typesense Cloud takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-typesense-cloud

Typesense Cloud (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-typesense-cloud.connectorbay.com/mcp
• REST API: https://byok-typesense-cloud.connectorbay.com/openapi.json
• Live status: https://byok-typesense-cloud.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Typesense Cloud (BYOK) never asks for them.