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

Particle (BYOK)

Read the devices, device groups and cloud variables of your Particle product fleet and call a function on one product device, with your own access token

Unify Dynamics LLC

Tools4read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderParticleunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

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

Which devices in my Particle product are running old firmware?
Tools called
list_product_devices
Which functions does device 0123456789abcdef01234567 of my Particle product expose?
Tools called
get_product_device
What is the temperature variable of device 0123456789abcdef01234567 in my Particle product?
Tools called
read_product_variable
Which device groups does my Particle product have?
Tools called
list_device_groups

About

Particle (BYOK) lets an AI assistant read your own Particle data through the Particle API with a key you supply (access token of a product team member (scopes devices:list, devices:get, groups:list, devices.variable:get, devices.function:call)). Read-only: 4 tools (list_product_devices, get_product_device, read_product_variable, list_device_groups). 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.particle.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Particle. Particle and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Particle API (api.particle.io) with a BYOK key; documentation: https://docs.particle.io/reference/cloud-apis/api/. 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

4 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data4 tools
  • List product devicesList devices of a product fleet with optional filters and sorting.
  • Get product deviceGet one device of a product fleet: firmware, desired firmware, groups, quarantine state, last contact and the names of the functions and variables…
  • Read product variableRead the current value of one cloud variable of a product device (for example a temperature or counter).
  • List device groupsList the device groups of a product (name, description, firmware version, color), optionally filtered by part of the name.

Information

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

Connect it to your agent

Three ways in, the same 4 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-particle-product-control.connectorbay.com/mcp
RESTPOST https://byok-particle-product-control.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-particle-product-control.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 access token of a product team member (scopes devices:list, devices:get, groups:list, devices.variable:get, devices.function:call) in the X-Upstream-Key header (get one at docs.particle.io).
  • Ask a question; the agent picks the right tool and answers from the live data.

Particle connector: questions and answers

What is the Particle connector?

Particle (BYOK) lets an AI assistant read your own Particle data through the Particle API with a key you supply (access token of a product team… It is a hosted MCP server with 4 tools such as List product devices, Get product device, Read product variable, List device groups, published by Unify Dynamics LLC. It is independent and not affiliated with Particle.

How do I connect Particle to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-particle-product-control.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-particle-product-control.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-particle-product-control.json.

Do I need a Particle account or API key?

Yes: this is a bring-your-own-key connector. Create a access token of a product team member (scopes devices:list, devices:get, groups:list, devices.variable:get, devices.function:call) at https://docs.particle.io/reference/cloud-apis/access-tokens/ and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Particle read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Particle 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

Are.na (BYOK)

Read your Are.na profile, channels, blocks, followers, feed and notifications with your own personal access token

Live · MCP + REST12 tools

Arize AX datasets, experiments, evaluators and tasks (BYOK)

Read your Arize AX datasets, experiments, evaluators, evaluation tasks and their runs with your own API key (global API host)

Live · MCP + REST10 tools

Arize AX prompts and annotation queues (BYOK)

Read your Arize AX prompt hub entries, prompt versions with model and labels, and annotation queues with your own API key (global API host)

Live · MCP + REST6 tools

Arize AX organizations, spaces, projects and monitors (BYOK)

Read your Arize AX organizations, spaces, projects, monitors and AI integration names with your own API key (global API host)

Live · MCP + REST9 tools

Artemis (BYOK)

Read Artemis on-chain fundamentals for crypto apps, chains and stablecoins and quarterly financials and valuation multiples for public equities with your own Artemis API key

Live · MCP + REST12 tools

Artifact Hub (BYOK)

Search Artifact Hub for Helm charts, operators, policies and other cloud native packages and read your account with your own API key

Live · MCP + REST8 tools

Documentation

Back to top

Particle (BYOK) — connector documentation

  • MCP endpoint: https://byok-particle-product-control.connectorbay.com/mcp
  • REST API: POST https://byok-particle-product-control.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-particle-product-control.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Particle access token of a product team member (scopes devices:list, devices:get, groups:list, devices.variable:get, devices.function:call), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-particle-product-control.connectorbay.com/health · Tool schemas: https://byok-particle-product-control.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-particle-product-control · agent@connectorbay.com

What Particle (BYOK) is for

Particle (BYOK) lets an AI assistant read your own Particle data through the Particle API with a key you supply (access token of a product team member (scopes devices:list, devices:get, groups:list, devices.variable:get, devices.function:call)). Read-only: 4 tools (list_product_devices, get_product_device, read_product_variable, list_device_groups). 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.particle.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Particle. Particle 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 in my Particle product are running old firmware?"
  • "Which functions does device 0123456789abcdef01234567 of my Particle product expose?"
  • "What is the temperature variable of device 0123456789abcdef01234567 in my Particle product?"
  • "Which device groups does my Particle product have?"

What it does

  • list_product_devices: List devices of a product fleet with optional filters and sorting. Needs a token with devices:list scope. Pages of 25 by default.
  • get_product_device: Get one device of a product fleet: firmware, desired firmware, groups, quarantine state, last contact and the names of the functions and variables it exposes. Needs devices:get scope.
  • read_product_variable: Read the current value of one cloud variable of a product device (for example a temperature or counter). The device must be online.
  • list_device_groups: List the device groups of a product (name, description, firmware version, color), optionally filtered by part of the name.

BYOK key

You bring your own Particle access token of a product team member (scopes devices:list, devices:get, groups:list, devices.variable:get, devices.function:call) (https://docs.particle.io/reference/cloud-apis/access-tokens/). 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.particle.io 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 Particle API (api.particle.io) with a BYOK key; documentation: https://docs.particle.io/reference/cloud-apis/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 Particle. Particle 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 Particle account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Particle (BYOK) — Privacy Policy

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

What Particle (BYOK) is. Particle (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Particle data: Read the devices, device groups and cloud variables of your Particle product fleet and call a function on one product device, with your own access token. You bring your own Particle access token of a product team member (scopes devices:list, devices:get, groups:list, devices.variable:get, devices.function:call); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Particle 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.particle.io, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Particle 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 Particle receives. The request we make on your behalf, including the key and the arguments, under Particle's own terms and privacy policy. Particle acts at your direction and is the only recipient of the data of your request besides our hosting provider.

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

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

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

Terms of service

Back to top

Particle (BYOK) — Terms of Service

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

  1. The Service. Particle (BYOK) provides: Read the devices, device groups and cloud variables of your Particle product fleet and call a function on one product device, with your own access 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 Particle credentials and only access data you are allowed to access. Particle's terms apply to your use of Particle; 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 Particle. Particle 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 Particle returns, lightly trimmed; it may be incomplete, delayed or changed by Particle. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Particle 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 Particle'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; Particle 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 Particle 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 Particle 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-particle-product-control

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

Get Particle (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Particle access token of a product team member (scopes devices:list, devices:get, groups:list, devices.variable:get, devices.function:call). Create one at https://docs.particle.io/reference/cloud-apis/access-tokens/, 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 Particle. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Particle.