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

Cumulocity Telemetry (BYOK) — connector documentation

  • MCP endpoint: https://byok-cumulocity-telemetry.connectorbay.com/mcp
  • REST API: POST https://byok-cumulocity-telemetry.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-cumulocity-telemetry.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Cumulocity Telemetry tenant ID and user name written as tenantID/username (for example t0071234/alice), sent in the X-Upstream-Key header and the password of that user in X-Upstream-Key-2 of every request (never stored, logged or cached)
  • Health: https://byok-cumulocity-telemetry.connectorbay.com/health · Tool schemas: https://byok-cumulocity-telemetry.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-cumulocity-telemetry · agent@connectorbay.com

What Cumulocity Telemetry (BYOK) is for

Cumulocity Telemetry (BYOK) lets an AI assistant read your own Cumulocity Telemetry data through the Cumulocity Telemetry API with a key you supply (tenant ID and user name written as tenantID/username (for example t0071234/alice)). Read-only: 8 tools (get_current_tenant, list_alarms, get_alarm, list_events, get_event, list_measurements, list_applications, list_bulk_operations). 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 *.cumulocity.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Cumulocity Telemetry. Cumulocity Telemetry 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 Cumulocity tenant am I connected to?"
  • "Which active critical alarms does my Cumulocity tenant have?"
  • "Show Cumulocity alarm 9001"
  • "What events did Cumulocity device 12345 report today?"
  • "Show Cumulocity event 7001"
  • "What temperature readings did Cumulocity device 12345 send in the last day?"

What it does

  • get_current_tenant: Show the tenant you are connected to: name, domain name, parent tenant and whether it may create sub-tenants.
  • list_alarms: List alarms with type, text, severity, status, occurrence count and the device they belong to, newest first. Filter by device, severity, status, type or time.
  • get_alarm: Get one alarm by id with type, text, severity, status, count, times and its device.
  • list_events: List events reported by devices with type, text, time and the device they belong to, newest first. Filter by device, type or time.
  • get_event: Get one event by id with type, text, time and its device.
  • list_measurements: List measurements (sensor readings) reported by devices for one device, type and time range, newest first. Each item carries the series values as reported by the device.
  • list_applications: List applications installed or available in the tenant (hosted web apps, microservices, external apps) with name, type, availability, context path and description.
  • list_bulk_operations: List bulk operations (one operation scheduled for every device in a group) with group, start date, status and progress counters.

BYOK key

You bring your own Cumulocity Telemetry tenant ID and user name written as tenantID/username (for example t0071234/alice) (https://cumulocity.com/docs/standard-tenant/users/). 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 *.cumulocity.com 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 Cumulocity Telemetry API (*.cumulocity.com) with a BYOK key; documentation: https://cumulocity.com/api/core/. 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 Cumulocity Telemetry. Cumulocity Telemetry 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 Cumulocity Telemetry account.

Built for: Worldwide. Languages: English.