# How to connect Adafruit IO to OpenClaw (paste one key, 21 tools) > Connect Adafruit IO to OpenClaw with ClawLink: paste your Adafruit IO key once and 21 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/adafruit-io The usual route to Adafruit IO access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Adafruit IO setup: install one ClawHub skill, connect Adafruit IO in the browser, and OpenClaw can call real Adafruit IO actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Adafruit IO. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Adafruit IO** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect adafruit-io # connect Adafruit IO (browser OAuth) npx -y @useclawlink/cli actions adafruit-io # list available actions npx -y @useclawlink/cli run adafruit-io --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Adafruit IO in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Adafruit IO API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Adafruit IO, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Adafruit IO is connected in the dashboard, that agent calls the same 21 Adafruit IO tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Adafruit IO MCP for OpenClaw Looking for a Adafruit IO MCP server for OpenClaw? ClawLink connects Adafruit IO to OpenClaw and exposes 21 Adafruit IO tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Adafruit IO integration](https://claw-link.dev/hermes/adafruit-io) works the same way. ## What the OpenClaw Adafruit IO integration can do 21 Adafruit IO tools are ready for OpenClaw once the account is connected. The 16 below are the ones people reach for most; your agent can call all 21. ### 16 of 21 Adafruit IO tools for OpenClaw | Tool | What it does | |---|---| | **Get account status** `adafruit_io_get_account_status` | Return compact identity, plan limits, and current data-write throttle usage for the connected | | **Get dashboards** `adafruit_io_get_dashboards` | List dashboards, or retrieve one dashboard and its blocks by key | | **Get data point** `adafruit_io_get_data_point` | Retrieve one feed data point by its exact ID | | **Get feeds** `adafruit_io_get_feeds` | List feeds, or retrieve one feed by key with optional data summary details | | **Get groups** `adafruit_io_get_groups` | List groups with feed summaries, or retrieve one group by key | | **List feed data** `adafruit_io_list_feed_data` | Return one newest-first page of feed data with an opaque cursor for the next older page | | **Add feeds to group** `adafruit_io_add_feeds_to_group` | Sequentially add 1-10 existing feeds to one group using one documented provider request per feed | | **Create dashboard** `adafruit_io_create_dashboard` | Create a dashboard for visualizing and controlling feed data | | **Create feed** `adafruit_io_create_feed` | Create a feed, optionally within an existing group | | **Create group** `adafruit_io_create_group` | Create a group for organizing feeds | | **Publish feed data** `adafruit_io_publish_feed_data` | Publish one or multiple timestamped values to a feed, using the batch endpoint only when | | **Remove feeds from group** `adafruit_io_remove_feeds_from_group` | Sequentially remove 1-10 feeds from one group using one documented provider request per feed | | **Update dashboard** `adafruit_io_update_dashboard` | Update an existing dashboard by exact dashboard key | | **Update data point** `adafruit_io_update_data_point` | Replace the value and optional metadata of one existing feed data point | | **Update feed** `adafruit_io_update_feed` | Update an existing feed by exact feed key | | **Update group** `adafruit_io_update_group` | Update an existing group by exact group key | ## Example prompts **Get Account Status** > Pull the relevant data from Adafruit IO, summarize it in plain English, and point out anything that needs attention. **Get Dashboards** > Pull the relevant data from Adafruit IO, summarize it in plain English, and point out anything that needs attention. **Get Data Point** > Pull the relevant data from Adafruit IO, summarize it in plain English, and point out anything that needs attention. **Get Feeds** > Pull the relevant data from Adafruit IO, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Adafruit IO working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Adafruit IO API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Adafruit IO account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Adafruit IO. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Adafruit IO actions to the runtime in a format your agent can reliably use. | 21 tools for Adafruit IO are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Adafruit IO to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Adafruit IO in the browser, and the 21 tools above work from chat. There is no SDK and no config file, and the Adafruit IO key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Adafruit IO skill but can't call the tools The ClawHub skill teaches OpenClaw about Adafruit IO, but the calls run through the ClawLink plugin and your connected account. Make sure Adafruit IO is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Adafruit IO from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Adafruit IO tools Adafruit IO tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Adafruit IO call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Adafruit IO returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Adafruit IO has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Adafruit IO integration? Yes. ClawLink is the fastest way to connect OpenClaw to Adafruit IO: link your Adafruit IO account once in the browser and OpenClaw can call the Adafruit IO API through 21 ready-made tools — no custom code or token handling. ### How do I add Adafruit IO to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Adafruit IO skill from ClawHub, then you click Connect in the dashboard to authorize Adafruit IO. OpenClaw calls the tools from the next message — no config files, and the Adafruit IO key you paste is stored server-side instead of in your environment. ### How long does it take to connect Adafruit IO to OpenClaw? About two minutes. Sign in, click Connect next to Adafruit IO in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Adafruit IO up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Adafruit IO working from chat. ### OpenClaw installed the Adafruit IO skill but can't call the tools The ClawHub skill teaches OpenClaw about Adafruit IO, but the calls run through the ClawLink plugin and your connected account. Make sure Adafruit IO is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [Connect GitHub](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.