Memfault (BYOK)

Memfault (BYOK) — connector documentation

• MCP endpoint: https://byok-memfault.connectorbay.com/mcp
• REST API: POST https://byok-memfault.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-memfault.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Memfault Memfault organization auth token (starts with oat_; an Administrator creates it under Admin, Organization Auth Tokens), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-memfault.connectorbay.com/health · Tool schemas: https://byok-memfault.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-memfault · agent@connectorbay.com

What Memfault (BYOK) is for

Memfault (BYOK) lets an AI assistant read your own Memfault data through the Memfault API with a key you supply (Memfault organization auth token (starts with oat_; an Administrator creates it under Admin, Organization Auth Tokens)). Read-only: 12 tools (list_projects, get_project, list_devices, get_device, list_releases, get_release, list_cohorts, list_cohort_devices, list_deployments, list_issues, get_issue, list_installs). 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.memfault.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Memfault. Memfault 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 Memfault projects does my organization have?"
• "How many devices does Memfault project sensor-fw have?"
• "Which devices in my Memfault project were seen most recently?"
• "Show Memfault device SN-0001"
• "Which firmware releases exist in my Memfault project?"
• "Show Memfault release 1.4.0"

What it does

• list_projects: List the projects in an organization with name, slug, platform, OS and device count. The project client key is not returned.
• get_project: Get one project: name, platform, OS, device count and dates. The project client key is not returned.
• list_devices: List the devices in a project with serial number, hardware version, cohort, last seen time, last seen release and latest install.
• get_device: Get one device by serial number: hardware version, cohort, last seen release, latest install and latest trace.
• list_releases: List the firmware releases of a project with version, revision, minimum version, device count, notes and artifact names.
• get_release: Get one firmware release by version: revision, device count, notes and artifacts.
• list_cohorts: List the cohorts (device groups that receive releases together) with name, slug, device count and last deployment.
• list_cohort_devices: List the devices in one cohort with serial number, hardware version and last seen time.
• list_deployments: List release deployments with cohort, release, rollout percent, status, type and who deployed.
• list_issues: List crash and error issues with title, message, status, trace and device counts, first and last seen and the releases they appear in.
• get_issue: Get one crash or error issue with counts, status, first and last seen and affected releases.
• list_installs: List firmware installs on devices with device serial, release, status and install times.

BYOK key

You bring your own Memfault Memfault organization auth token (starts with oat_; an Administrator creates it under Admin, Organization Auth Tokens) (https://docs.memfault.com/docs/ci/authentication). 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.memfault.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

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

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

Built for: Worldwide. Languages: English.

Memfault (BYOK) — Privacy Policy

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

What Memfault (BYOK) is. Memfault (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Memfault data: Read your Memfault embedded-device fleet: projects, devices, releases, cohorts, deployments, firmware installs and crash issues with your own organization auth token. You bring your own Memfault Memfault organization auth token (starts with oat_; an Administrator creates it under Admin, Organization Auth Tokens); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Memfault 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.memfault.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 Memfault 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 Memfault receives. The request we make on your behalf, including the key and the arguments, under Memfault's own terms and privacy policy. Memfault acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Memfault 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 Memfault 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. Memfault (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 Memfault at any time to end all access.

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

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

Memfault (BYOK) — Terms of Service

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

1. The Service. Memfault (BYOK) provides: Read your Memfault embedded-device fleet: projects, devices, releases, cohorts, deployments, firmware installs and crash issues with your own organization auth token. 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 Memfault credentials and only access data you are allowed to access. Memfault's terms apply to your use of Memfault; 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 Memfault. Memfault 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 Memfault returns, lightly trimmed; it may be incomplete, delayed or changed by Memfault. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Memfault 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 Memfault'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; Memfault 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 Memfault 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 Memfault 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-memfault

Memfault (BYOK) support

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

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