Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Temporal Cloud (BYOK) — connector documentation

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

What Temporal Cloud (BYOK) is for

Temporal Cloud (BYOK) lets an AI assistant read your own Temporal Cloud data through the Temporal Cloud API with a key you supply (Temporal Cloud API key). Read-only: 7 tools (list_namespaces, get_namespace, get_namespace_capacity_info, list_regions, list_projects, get_usage, get_account). 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 saas-api.tmprl.cloud. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Temporal Cloud. Temporal 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 Temporal Cloud namespaces do we have and where do they run?"
  • "Show Temporal Cloud namespace payments.a2b3c"
  • "How close is Temporal Cloud namespace payments.a2b3c to its capacity?"
  • "Which regions does Temporal Cloud support?"
  • "What projects are defined in our Temporal Cloud account?"
  • "How many Temporal Cloud actions did we use in October 2026?"

What it does

  • list_namespaces: List Temporal Cloud namespaces in ascending name order with state, active region, endpoints, rate limit and dates; filter by name or project.
  • get_namespace: Get one namespace by its full name: state, active region, endpoints, actions-per-second limit and dates.
  • get_namespace_capacity_info: Show a namespace's current capacity mode, available capacity options and recent actions-per-second statistics (mean, p90, p99).
  • list_regions: List the cloud regions where Temporal Cloud namespaces can run, with provider, provider region and location.
  • list_projects: List projects used to group namespaces, with state and dates.
  • get_usage: Get usage summaries (actions, active storage, retained storage) per period, optionally grouped by namespace, for a time range.
  • get_account: Show the Temporal Cloud account id, state and account-level metrics.

BYOK key

You bring your own Temporal Cloud Temporal Cloud API key (https://cloud.temporal.io/keys). 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 saas-api.tmprl.cloud 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

Live from the Temporal Cloud API (saas-api.tmprl.cloud) with a BYOK key; documentation: https://docs.temporal.io/ops. 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 Temporal Cloud. Temporal 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 Temporal Cloud account.

Built for: Worldwide. Languages: English.