Integration

Adafruit IO integration

Adafruit IO is Adafruit's IoT data platform: devices publish sensor readings to feeds, and dashboards and actions react to them. Record values on a feed (one at a time, in batches, or one per feed of a group), read a feed's data, its last value, first and last data points and chart aggregates, update or delete data points, manage feeds, groups and dashboards, list, inspect, start, stop and delete actions (automations built in the Actions editor), and read the account activity log, your user and your data rate limit. Data writes count against your data rate (30 points per minute on the free plan, 60 on IO+). Dashboard blocks and layouts, feed sharing, webhook receivers, permissions, key regeneration, data exports and the deprecated triggers routes are not exposed. Authentication is your Adafruit IO key sent in the X-AIO-Key header, together with your Adafruit IO username, which every path uses.

Connect Adafruit IO How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Adafruit IO.Built from the 41 Adafruit IO tools below, on the connection you add once.

What you can do with Adafruit IO

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Feed, 7 operations

create_feedCreate feedPOSTCreates a feed, optionally inside a group (group_key). Creating feeds does not count against your data rate.
create_group_feedCreate group feedPOSTCreates a feed inside a group.
delete_feedDelete feedDELETEDeletes a feed and its data.
get_feedGet feedGETReturns one feed with its key, last value, status and settings.
list_feedsList feedsGETReturns all of your feeds with their key, last value, status and settings.
list_group_feedsList group feedsGETReturns the feeds of a group.
update_feedUpdate feedPUTUpdates a feed's settings.

Data, 6 operations

create_dataCreate dataPOSTRecords a new value on a feed, optionally with a location (lat, lon, ele) and a past created_at. Counts against your data rate limit.
create_group_dataCreate group dataPOSTRecords one value on each of several feeds of a group in one request, creating feeds that do not exist in the group yet. Each feed counts as one action against your data rate.
delete_data_pointDelete data pointDELETEDeletes one data point of a feed. Counts against your data rate limit.
get_data_pointGet data pointGETReturns one data point of a feed.
list_feed_dataList feed dataGETReturns a feed's data points, newest first: 100 by default, at most 1000. Use start_time and end_time to select a time range.
update_data_pointUpdate data pointPUTReplaces a data point's value and optional location. Counts against your data rate limit.

Dashboard, 5 operations

create_dashboardCreate dashboardPOSTCreates a new, empty dashboard.
delete_dashboardDelete dashboardDELETEDeletes a dashboard and all of its blocks, and returns the deleted dashboard.
get_dashboardGet dashboardGETReturns one dashboard with its blocks and layout.
list_dashboardsList dashboardsGETReturns all of your dashboards, without their blocks.
update_dashboardUpdate dashboardPUTUpdates a dashboard. Only the fields you include are changed.

Group, 5 operations

create_groupCreate groupPOSTCreates a group, a set of feeds you publish to or read together.
delete_groupDelete groupDELETEDeletes a group, and with it every feed that belongs to no other group (with its data). The default group cannot be deleted.
get_groupGet groupGETReturns one group with its feeds.
list_groupsList groupsGETReturns all of your groups, each with its feeds.
update_groupUpdate groupPUTUpdates a group and returns it.

Dynamic action, 4 operations

delete_actionDelete actionDELETEDeletes an action and its run history, and returns the deleted action.
get_actionGet actionGETReturns one action with its definition and the logs of its recent runs. To see why an action is not running, read run_status, validation_status, bytecode_validation_errors and last_run_log.
list_actionsList actionsGETReturns your actions (automations built in the Actions editor), ordered by id, with their run and validation status.
update_actionUpdate actionPUTRenames, starts or stops an action, and returns it. Send only the fields to change.

Activitie, 3 operations

delete_all_activitiesDelete all activitiesDELETEDeletes every activity record of your account, for all object types. This cannot be undone.
list_activitiesList activitiesGETReturns the log of objects you created or deleted (feeds, groups, dashboards, blocks, actions, tokens), newest first. The last 10,000 actions are kept; updates are not logged.
list_activities_by_typeList activities by typeGETReturns the create and delete log for one type of object, newest first.

Last value, 2 operations

get_group_last_valuesGet group last valuesGETReturns the most recent value of every feed in a group in one request. Feeds are keyed as group_key.feed_key when the group is not your default group; feeds without data are null.
get_last_valueGet last valueGETReturns the most recent value of a feed as a data record, without paging through the data list. Works with read-only access, so also on public feeds. Fails with 404 when the feed has never received data.

Add, 1 operation

add_feed_to_groupAdd feed to groupPOSTAdds one of your existing feeds to a group and returns the updated group. The feed is taken from your default group unless feed_key names its group as group_key.feed_key.

Batch, 1 operation

create_data_batchCreate data batchPOSTRecords several values on a feed in one request. Each record counts against your data rate limit; if there is not enough room left for the whole batch nothing is saved (429).

Chart, 1 operation

get_feed_chart_dataGet feed chart dataGETReturns a feed's data aggregated into time slices for charting, with the parameters used. The resolution is chosen automatically from the time range or hours unless given.

Detail, 1 operation

get_feed_detailsGet feed detailsGETReturns a feed with details of its stored data (first and last data points and the number of points).

First, 1 operation

get_first_dataGet first dataGETReturns the oldest stored data point of a feed.

Last, 1 operation

get_last_dataGet last dataGETReturns the most recent data point of a feed.

Remove, 1 operation

remove_feed_from_groupRemove feed from groupPOSTRemoves a feed from a group and returns the updated group. A feed cannot be removed from its last group.

Throttle, 1 operation

get_throttleGet throttleGETReturns your data rate limit (data points per minute) and how many data actions you have used in the current minute.

User, 1 operation

get_current_userGet current userGETReturns the user that owns the Adafruit IO key (id, name, username, time zone).

Use Adafruit IO from Claude Code, Cursor or Codex

Connect Adafruit IO in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Adafruit IO operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Adafruit IO

Create your workspace
Sign up free. Nothing to install.
Connect Adafruit IO once
Add your Adafruit IO connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.