Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Adafruit IO MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Read Adafruit IO feeds, data, groups and dashboards; publish a data point or create a feed.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http adafruit-io-mcp-by-usefulapi https://adafruit-io.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# adafruitio_get_user, adafruitio_get_throttle, adafruitio_list_feeds and 14 more
Adafruit IO MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http adafruit-io-mcp-by-usefulapi https://adafruit-io.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
17 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
The Adafruit IO account this key belongs to: id, name, username, time zone, created/updated times, plus the data rate limit when reported. GET /api/v2/user.
No parameter schema on file.
The account's data rate limit (data-record modifications per minute: 30 on free accounts, 60 on Plus) and the current active data rate. Check it before publishing many points. GET /api/v2/{username}/throttle.
No parameter schema on file.
List all of the account's feeds with key, name, description, unit, visibility, enabled flag, last value and last update. GET /feeds.
No parameter schema on file.
One feed by key: name, description, unit, visibility, last value, status settings and the groups it belongs to. GET /feeds/{feed_key}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| feed_key | string | yes | Feed key (the URL-safe key shown in Adafruit IO, for example 'temperature'; 'group-key.feed-key' also works). |
A feed with its details block: first and last data point and the number of stored points. GET /feeds/{feed_key}/details.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| feed_key | string | yes | Feed key (the URL-safe key shown in Adafruit IO, for example 'temperature'; 'group-key.feed-key' also works). |
Data points of a feed (max 1000 per call). Newest first, except that with start_time the API returns the oldest page after that time. Filter by time range and limit; to read further back call again with the reply's next_page_args (the same filters plus before). GET /feeds/{feed_key}/data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| feed_key | string | yes | Feed key (the URL-safe key shown in Adafruit IO, for example 'temperature'; 'group-key.feed-key' also works). |
| start_time | string | no | ISO 8601 date or date-time, e.g. 2026-10-01T00:00:00Z. |
| end_time | string | no | ISO 8601 date or date-time, e.g. 2026-10-01T00:00:00Z. |
| limit | integer | no | Maximum records to return, 1-1000 (default 100). |
| include | string | no | Comma-separated fields to return: value, lat, lon, ele, id, created_at. |
| before | string | no | Pagination token: next_before from the previous reply (keep the same other arguments). |
The most recent data point of a feed (value, location, created_at). GET /feeds/{feed_key}/data/last.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| feed_key | string | yes | Feed key (the URL-safe key shown in Adafruit IO, for example 'temperature'; 'group-key.feed-key' also works). |
| include | string | no | Comma-separated fields to return: value, lat, lon, ele, id, created_at. |
One stored data point of a feed by its id. GET /feeds/{feed_key}/data/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| feed_key | string | yes | Feed key (the URL-safe key shown in Adafruit IO, for example 'temperature'; 'group-key.feed-key' also works). |
| data_id | string | yes | Data point id (the id field of a data point). |
Aggregated chart data for a feed: values sliced by resolution minutes over the last hours (or a start/end range), using avg, sum, min, max, val or val_count. Good for trends without downloading every point. GET /feeds/{feed_key}/data/chart.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| feed_key | string | yes | Feed key (the URL-safe key shown in Adafruit IO, for example 'temperature'; 'group-key.feed-key' also works). |
| hours | integer | no | Hours of history (ignored when start_time and end_time are given). |
| resolution | no | Slice size in minutes. | |
| field | string | no | Aggregation (default avg). |
| start_time | string | no | ISO 8601 date or date-time, e.g. 2026-10-01T00:00:00Z. |
| end_time | string | no | ISO 8601 date or date-time, e.g. 2026-10-01T00:00:00Z. |
List the account's groups (named sets of feeds) with their feeds. GET /groups.
No parameter schema on file.
One group by key with its feeds. GET /groups/{group_key}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| group_key | string | yes | Group key. |
List the account's dashboards with key, name, description and visibility. GET /dashboards.
No parameter schema on file.
One dashboard by key. GET /dashboards/{dashboard_key}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboard_key | string | yes | Dashboard key. |
The blocks (widgets: gauges, toggles, charts, sliders...) of a dashboard with their feeds, position and properties. Integration secrets in properties are removed. GET /dashboards/{dashboard_key}/blocks.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dashboard_key | string | yes | Dashboard key. |
The account's activity log (feed/data/dashboard changes), optionally within a time range. GET /activities.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_time | string | no | ISO 8601 date or date-time, e.g. 2026-10-01T00:00:00Z. |
| end_time | string | no | ISO 8601 date or date-time, e.g. 2026-10-01T00:00:00Z. |
| limit | integer | no | Maximum entries, 1-1000. |
WRITE: publish one data point (a value) to a feed. This can drive REAL DEVICES: anything subscribed to the feed (relays, motors, lights, heaters, locks, dashboard toggles) will receive and may act on the value, and it cannot be undone from here. Only publish a value the user has asked for. Counts against the account's data rate limit (30 per minute on free accounts, 60 on Plus). POST /feeds/{feed_
| Parameter | Type | Required | Notes |
|---|---|---|---|
| feed_key | string | yes | Feed key (the URL-safe key shown in Adafruit IO, for example 'temperature'; 'group-key.feed-key' also works). |
| value | yes | The value to publish (text or number, up to 1000 characters). | |
| lat | number | no | Latitude of the reading. |
| lon | number | no | Longitude of the reading. |
| ele | number | no | Elevation of the reading in meters. |
WRITE: create a new, empty feed (private by default), optionally inside an existing group. Adds a feed only; it does not change or delete anything existing, and fails if the name is taken. POST /feeds.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Feed name (the key is derived from it). |
| description | string | no | Optional description. |
| group_key | string | no | Optional existing group key to create the feed in. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Adafruit IO MCP by usefulapi or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Adafruit IO MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.