Adafruit IO MCP integration for AI agents.
Connect AI agents to Adafruit IO through 5 structured actions, including get current user, create feed data, and get feed. Review authentication, inputs, wor…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Adafruit IO integration exposes
The Adafruit IO Agent App exposes 5 provider-backed actions for data and developer tools work. Its current contract lets an authorized agent get the current adafruit io user for the connected api key, create a new data point on an adafruit io feed, and get one adafruit io feed by feed key. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Adafruit IO account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Adafruit IO capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_current_userREADGet the current Adafruit IO user for the connected API key.
create_feed_dataWRITECreate a new data point on an Adafruit IO feed.
INPUTS: username / feedKey / value / createdAt / lat
get_feedREADGet one Adafruit IO feed by feed key.
INPUTS: username / feedKey
list_feed_dataREADList data points for an Adafruit IO feed.
INPUTS: username / feedKey / startTime / endTime / limit
list_feedsREADList Adafruit IO feeds for a username.
INPUTS: username
INPUT CONTRACTS
Know what the action needs before it runs.
create_feed_data
usernameOPTIONAL- The Adafruit IO username. Defaults to the connected account username.
feedKeyREQUIRED- The Adafruit IO feed key.
valueREQUIRED- The data value to send to the feed.
createdAtOPTIONAL- The creation timestamp to attach to the data point.
latOPTIONAL- The latitude value to attach to the data point.
get_feed
usernameOPTIONAL- The Adafruit IO username. Defaults to the connected account username.
feedKeyREQUIRED- The Adafruit IO feed key.
list_feed_data
usernameOPTIONAL- The Adafruit IO username. Defaults to the connected account username.
feedKeyREQUIRED- The Adafruit IO feed key.
startTimeOPTIONAL- Return records created after this timestamp.
endTimeOPTIONAL- Return records created before this timestamp.
limitOPTIONAL- The maximum number of data records to return.
list_feeds
usernameOPTIONAL- The Adafruit IO username. Defaults to the connected account username.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Current User
Get the current Adafruit IO user for the connected API key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_current_userControl Create Feed Data
Create a new data point on an Adafruit IO feed. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_feed_dataVerify with Get Feed
Get one Adafruit IO feed by feed key. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_feedSAFETY BOUNDARY
Operate Adafruit IO with explicit limits
- Authorize Adafruit IO with API key and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Adafruit IO rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Adafruit IO task completed successfully.
CONNECTION MODEL
API key
Adafruit IO API key sent in the X-AIO-Key header. View or regenerate it from your Adafruit IO account page: https://io.adafruit.com/.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Adafruit IO.