Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Helium Console (BYOK) icon

Helium Console (BYOK)

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

Tools5reads + 1 confirmed actions
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderHelium Consoleunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which Helium devices are active and when did they last connect?
Tools called
list_devices
Show Helium device e3d7f0e2-6f4a-4a40-9d0a-1d4f2a3b5c6d
Tools called
get_device
What events did Helium device e3d7f0e2-6f4a-4a40-9d0a-1d4f2a3b5c6d report recently?
Tools called
get_device_events
Which labels do I have in Helium Console?
Tools called
list_labels
Deactivate Helium device e3d7f0e2-6f4a-4a40-9d0a-1d4f2a3b5c6d
Tools called
set_device_active

About

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 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.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

5 tools, grouped by job. Read tools plus 1 device actions (Set device active), each run only with your confirmation.

OpenAPI
Read your data5 tools
  • List devicesList the organization's LoRaWAN devices with name, DevEUI, AppEUI, active flag, last connection, packet count, data credit usage and labels.
  • Get deviceGet one device by UUID: name, DevEUI, AppEUI, last connection, packet count, data credit usage and labels.
  • Get device eventsGet the last 100 events of a device (uplinks, joins, integration requests) with category, description and time.
  • List labelsList the organization's labels (groups of devices) with id and name.
  • Set device activeSwitch one device's active flag in Console.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-helium-console.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 5 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-helium-console.connectorbay.com/mcp
RESTPOST https://byok-helium-console.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-helium-console.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your Helium Console API key (Account, Profile; shown once and confirmed by email) in the X-Upstream-Key header (get one at console.helium.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

Helium Console connector: questions and answers

What is the Helium Console connector?

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.

How do I connect Helium Console to Claude, ChatGPT or Cursor?

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.

Do I need a Helium Console account or API key?

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.

Can Helium Console change my devices?

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.

Is the Helium Console connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

IONOS Mongo DB (BYOK)

Read your IONOS Cloud managed MongoDB clusters, snapshots, templates and available versions with your own API token

Live · MCP + REST5 tools

IONOS PostgreSQL (BYOK)

Read your IONOS Cloud managed PostgreSQL clusters, backups, versions and backup locations in any IONOS region with your own API token

Live · MCP + REST5 tools

IPinfo (BYOK)

Look up the country, network (ASN) and, with a Core plan, the city, coordinates and hosting flags of an IP address with BYOK

Live · MCP + REST4 tools

IPUMS (BYOK)

Browse IPUMS NHGIS datasets, tables, time series and shapefiles and check your IPUMS data extracts with your own IPUMS API key

Live · MCP + REST9 tools

Ironclad Clickwrap (BYOK)

Read your Ironclad Clickwrap sites, acceptance groups and contract definitions with your own access token

Live · MCP + REST8 tools

Ironclad Records (BYOK)

Read your Ironclad contract records schema, record list, legal entities and obligations with your own bearer token

Live · MCP + REST6 tools

Documentation

Back to top

Helium Console (BYOK) — connector documentation

  • MCP endpoint: https://byok-helium-console.connectorbay.com/mcp
  • REST API: POST 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.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Helium Console Helium Console API key (Account, Profile; shown once and confirmed by email), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-helium-console.connectorbay.com/health · Tool schemas: https://byok-helium-console.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-helium-console · agent@connectorbay.com

What Helium Console (BYOK) is for

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 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:

  • "Which Helium devices are active and when did they last connect?"
  • "Show Helium device e3d7f0e2-6f4a-4a40-9d0a-1d4f2a3b5c6d"
  • "What events did Helium device e3d7f0e2-6f4a-4a40-9d0a-1d4f2a3b5c6d report recently?"
  • "Which labels do I have in Helium Console?"
  • "Deactivate Helium device e3d7f0e2-6f4a-4a40-9d0a-1d4f2a3b5c6d"

What it does

  • 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.

BYOK key

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.

Data 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.

What it is not

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.

Privacy policy

Back to top

Helium Console (BYOK) — Privacy Policy

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.

Terms of service

Back to top

Helium Console (BYOK) — Terms of Service

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

  1. The Service. Helium Console (BYOK) provides: 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. It is accessed through an AI assistant or directly over MCP or HTTP, and can read the device data and change device state, but only through actions you approve in chat and confirm.
  2. Your own key, your own account. You must use your own Helium Console credentials and only access data you are allowed to access. Helium Console's terms apply to your use of Helium Console; 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 Helium Console. Helium Console 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 Helium Console returns, lightly trimmed; it may be incomplete, delayed or changed by Helium Console. Check important facts at the source.
  5. Device changes. The Service changes the state of a Helium Console device only through an action you approve in chat and pass with confirm = yes. It does not delete, reset, wipe, send messages or create paid resources.
  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 Helium Console'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; Helium Console 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 Helium Console 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 Helium Console 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-helium-console

Helium Console (BYOK) support

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

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. Helium Console (BYOK) never asks for them.

Get Helium Console (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Helium Console Helium Console API key (Account, Profile; shown once and confirmed by email). Create one at https://console.helium.com/profile, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Helium Console. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Helium Console.