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

Cumulocity Operations (BYOK) — connector documentation

  • MCP endpoint: https://byok-cumulocity-operations.connectorbay.com/mcp
  • REST API: POST https://byok-cumulocity-operations.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-cumulocity-operations.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Cumulocity Operations 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-operations.connectorbay.com/health · Tool schemas: https://byok-cumulocity-operations.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-cumulocity-operations · agent@connectorbay.com

What Cumulocity Operations (BYOK) is for

Cumulocity Operations (BYOK) lets an AI assistant read your own Cumulocity Operations data through the Cumulocity Operations API with a key you supply (tenant ID and user name written as tenantID/username (for example t0071234/alice)). Reads and device changes: 6 tools (list_devices, get_device, list_operations, get_operation, restart_device, request_configuration_upload). 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 Operations. Cumulocity Operations 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 devices are in my Cumulocity tenant and what operations do they support?"
  • "Show the Cumulocity device 12345"
  • "Which operations are pending for Cumulocity device 12345?"
  • "Did Cumulocity operation 20180 succeed?"
  • "Restart Cumulocity device 12345"
  • "Ask Cumulocity device 12345 to upload its current configuration"

What it does

  • list_devices: List devices of the tenant (managed objects with the c8y_IsDevice fragment) with id, name, type, owner, last update and the operations each device supports.
  • get_device: Get one device by id: name, type, owner, timestamps and supported operations.
  • list_operations: List device operations (commands sent to devices) with status PENDING, EXECUTING, SUCCESSFUL or FAILED, newest first, for one device or the whole tenant.
  • get_operation: Get one operation by id to see whether the device has executed it (status and failure reason).
  • restart_device: Create a restart operation (c8y_Restart) for one device. The device picks it up and reboots, so this changes the device state and the device is briefly offline. The device must support the operation (see c8y_SupportedOperations from list_devices). Not for doors, locks, gates, alarms, cameras, vehicles or safety limits.
  • request_configuration_upload: Create a c8y_SendConfiguration operation asking one device to upload its current configuration to the platform. The device runs the request and updates its stored configuration record, which changes the device's reported state. The device must support the operation (see c8y_SupportedOperations from list_devices). Not for doors, locks, gates, alarms, cameras, vehicles or safety limits.

BYOK key

You bring your own Cumulocity Operations 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 Operations 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 Operations. Cumulocity Operations and its logos are trademarks of their owners and are used only to say which service the connector works with. It reads your Cumulocity Operations data and can change device state only when a specific action is approved and confirmed (confirm = yes); it never deletes, resets, sends messages or creates paid resources.

Built for: Worldwide. Languages: English.