IONOS Mongo DB (BYOK)
Read your IONOS Cloud managed MongoDB clusters, snapshots, templates and available versions with your own API token
Read your Helium Console LoRaWAN devices, labels and recent device events, and switch a device's active flag on or off with your own Console API key
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
list_devicesget_deviceget_device_eventslist_labelsset_device_activeHelium Console (BYOK) lets an AI assistant read your own Helium Console data through the Helium Console API with a key you supply (Helium Console API key (Account, Profile; shown once and confirmed by email)). Reads and device changes: 5 tools (list_devices, get_device, get_device_events, list_labels, set_device_active). 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 console.helium.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Helium Console. Helium Console and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the Helium Console API (console.helium.com) with a BYOK key; documentation: https://docs.helium.com/api/console. Endpoints checked against that documentation on 2026-10-16.
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
5 tools, grouped by job. Read tools plus 1 device actions (Set device active), each run only with your confirmation.
https://byok-helium-console.connectorbay.com/mcpThree ways in, the same 5 tools.
https://byok-helium-console.connectorbay.com/mcpPOST https://byok-helium-console.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-helium-console.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at console.helium.com).Helium Console (BYOK) lets an AI assistant read your own Helium Console data through the Helium Console API with a key you supply (Helium Console… It is a hosted MCP server with 5 tools such as List devices, Get device, Get device events, List labels, Set device active, published by Unify Dynamics LLC. It is independent and not affiliated with Helium Console.
Add the MCP endpoint https://byok-helium-console.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-helium-console.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-helium-console.json.
Yes: this is a bring-your-own-key connector. Create a Helium Console API key (Account, Profile; shown once and confirmed by email) at https://console.helium.com/profile and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.
Yes, for 1 actions (Set device active). Each one runs only when the user approved that change in chat and the call carries confirm = yes; without it the connector refuses before contacting the vendor. Nothing is deleted, reset, paid or messaged.
Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.
Read your IONOS Cloud managed MongoDB clusters, snapshots, templates and available versions with your own API token
Read your IONOS Cloud managed PostgreSQL clusters, backups, versions and backup locations in any IONOS region with your own API token
Look up the country, network (ASN) and, with a Core plan, the city, coordinates and hosting flags of an IP address with BYOK
Browse IPUMS NHGIS datasets, tables, time series and shapefiles and check your IPUMS data extracts with your own IPUMS API key
Read your Ironclad Clickwrap sites, acceptance groups and contract definitions with your own access token
Read your Ironclad contract records schema, record list, legal entities and obligations with your own bearer token
https://byok-helium-console.connectorbay.com/mcpPOST https://byok-helium-console.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-helium-console.connectorbay.com/openapi.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-helium-console.connectorbay.com/health · Tool schemas: https://byok-helium-console.connectorbay.com/tools.jsonHelium Console (BYOK) lets an AI assistant read your own Helium Console data through the Helium Console API with a key you supply (Helium Console API key (Account, Profile; shown once and confirmed by email)). Reads and device changes: 5 tools (list_devices, get_device, get_device_events, list_labels, set_device_active). 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 console.helium.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Helium Console. Helium Console 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:
list_devices: List the organization's LoRaWAN devices with name, DevEUI, AppEUI, active flag, last connection, packet count, data credit usage and labels. Device keys are not returned.get_device: Get one device by UUID: name, DevEUI, AppEUI, last connection, packet count, data credit usage and labels.get_device_events: Get the last 100 events of a device (uplinks, joins, integration requests) with category, description and time. Use sub_category to filter.list_labels: List the organization's labels (groups of devices) with id and name.set_device_active: Switch one device's active flag in Console. Inactive devices are not served by the network (their uplinks are dropped), so this changes the device's service state; set active back to true to restore it. The device itself is not deleted or reset.You bring your own Helium Console Helium Console API key (Account, Profile; shown once and confirmed by email) (https://console.helium.com/profile). 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 console.helium.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.
Live from the Helium Console API (console.helium.com) with a BYOK key; documentation: https://docs.helium.com/api/console. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Helium Console. Helium Console and its logos are trademarks of their owners and are used only to say which service the connector works with. It reads your Helium Console 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.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Helium Console (BYOK) is. Helium Console (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Helium Console data: Read your Helium Console LoRaWAN devices, labels and recent device events, and switch a device's active flag on or off with your own Console API key. You bring your own Helium Console Helium Console API key (Account, Profile; shown once and confirmed by email); the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one Helium Console 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 console.helium.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 Helium Console 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 Helium Console receives. The request we make on your behalf, including the key and the arguments, under Helium Console's own terms and privacy policy. Helium Console acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer Helium Console 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 Helium Console 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. Helium Console (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 Helium Console at any time to end all access.
Children. Helium Console (BYOK) is a general-audience service operated by the adult using the assistant, under Helium Console's own age rules.
Changes. We will post changes here with a new effective date.
Effective 24 October 2026. These terms govern use of the Helium Console (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-helium-console.connectorbay.com/mcphttps://byok-helium-console.connectorbay.com/openapi.jsonWhen 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. Helium Console (BYOK) never asks for them.