NRF Cloud (BYOK)

NRF Cloud (BYOK) — connector documentation

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

What NRF Cloud (BYOK) is for

NRF Cloud (BYOK) lets an AI assistant read your own NRF Cloud data through the NRF Cloud API with a key you supply (nRF Cloud API key (Account section of nrfcloud.com)). Read-only: 10 tools (list_devices, get_device, list_device_tags, list_firmware, list_fota_jobs, get_fota_job, list_fota_executions_for_device, get_pending_fota_execution, list_bulk_operations, get_bulk_operation). 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 api.nrfcloud.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by NRF Cloud. NRF 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 devices are registered in my nRF Cloud account?"
• "What firmware is nRF Cloud device nrf-352656100123456 running?"
• "Which device groups exist in my nRF Cloud account?"
• "Which firmware bundles have I uploaded to nRF Cloud?"
• "Which firmware update jobs are running in nRF Cloud?"
• "How far along is nRF Cloud firmware update job 5f3e9c1a-1c2b-4d5e-8f70-123456789abc?"

What it does

• list_devices: List the devices of the account with id, name, tags, type, sub type, firmware support and creation and update times. Paged.
• get_device: Get one device's metadata: id, name, tags, type, firmware versions and timestamps. Its reported state is not returned.
• list_device_tags: List all device tags (device groups) of the account. Paged.
• list_firmware: List firmware bundles uploaded to the account (or Nordic's modem firmware when modem_only is true) with type, version, size and update time. Paged.
• list_fota_jobs: List firmware-over-the-air update jobs with status, targets, execution statistics and firmware type and version. Paged.
• get_fota_job: Get one firmware update job: status, targets, per-state execution counts and firmware details.
• list_fota_executions_for_device: List the firmware update executions of one device with job, status and firmware type and version. Paged.
• get_pending_fota_execution: Get a device's oldest pending (queued or in progress) firmware update execution, optionally for one firmware type.
• list_bulk_operations: List device onboarding and key or certificate registration operations with status and times. Paged.
• get_bulk_operation: Get one onboarding or registration operation: endpoint, status and request and completion times.

BYOK key

You bring your own NRF Cloud nRF Cloud API key (Account section of nrfcloud.com) (https://nrfcloud.com/). 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 api.nrfcloud.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.

Notices

Read-only. Device state, device messages and location services are not exposed (they can contain positions, and location lookups are charged by nRF Cloud).

Data sources

• https://api-docs.nrfcloud.com/ (the API this connector calls, with a BYOK key)

Live from the NRF Cloud API (api.nrfcloud.com) with a BYOK key; documentation: https://api-docs.nrfcloud.com/. 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 NRF Cloud. NRF 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 NRF Cloud account.

Built for: Worldwide. Languages: English.

NRF Cloud (BYOK) — Privacy Policy

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

What NRF Cloud (BYOK) is. NRF Cloud (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own NRF Cloud data: Read your Nordic nRF Cloud devices, device tags, firmware, firmware-over-the-air jobs and executions and onboarding operations with your own API key. You bring your own NRF Cloud nRF Cloud API key (Account section of nrfcloud.com); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one NRF 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 api.nrfcloud.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If NRF 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 NRF Cloud receives. The request we make on your behalf, including the key and the arguments, under NRF Cloud's own terms and privacy policy. NRF 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 NRF 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 NRF 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. NRF 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 NRF Cloud at any time to end all access.

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

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

NRF Cloud (BYOK) — Terms of Service

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

1. The Service. NRF Cloud (BYOK) provides: Read your Nordic nRF Cloud devices, device tags, firmware, firmware-over-the-air jobs and executions and onboarding operations with your own 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 NRF Cloud credentials and only access data you are allowed to access. NRF Cloud's terms apply to your use of NRF 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 NRF Cloud. NRF 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 NRF Cloud returns, lightly trimmed; it may be incomplete, delayed or changed by NRF Cloud. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your NRF 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 NRF 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; NRF 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 NRF 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 NRF 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-nrfcloud

NRF Cloud (BYOK) support

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

• MCP endpoint: https://byok-nrfcloud.connectorbay.com/mcp
• REST API: https://byok-nrfcloud.connectorbay.com/openapi.json
• Live status: https://byok-nrfcloud.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. NRF Cloud (BYOK) never asks for them.