Adafruit IO MCP for AI. Monitor and manage all your sensor data streams.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Connect to your AI in seconds.
Adafruit IO connects your AI client directly to live IoT data streams. Use this MCP to manage all your sensor readings, feeds, groups, and dashboards from a single conversation.
Need to check if a temperature reading is spiking? Want to list all available sensors in a group? This tool gives your agent the ability to read specific data points, list entire feed structures, or even view active alert triggers—all without writing boilerplate API code.
What your AI can do
Get dashboard
Retrieves the full details for a single, specified dashboard view.
Get data
Pulls one specific data point reading from an active sensor feed.
Get feed
Retrieves all metadata for a defined data feed, including its purpose and structure.
Retrieve specific measurements or historical readings from any active data feed.
List all available sensor feeds and get details about a single, defined data stream.
View groupings of sensors or feeds and retrieve specific group information.
List all available dashboards and pull up the details for a single dashboard view.
View existing alert triggers or list out every active trigger rule defined in your system.
Ask an AI about this
Waiting for input…
Adafruit IO: 10 Tools for Data Management
These tools give your agent full access to the entire Adafruit IO resource model. You can query every aspect of your sensor network, from listing feeds to checking individual triggers.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Adafruit IO on VinkiusGet Dashboard
Retrieves the full details for a single, specified dashboard view.
Get Data
Pulls one specific data point reading from an active sensor feed.
Get Feed
Retrieves all metadata for a defined data feed, including its purpose and structure.
Get Group
Gets the specific contents and members of a named group in your system.
Get Trigger
Checks the parameters and rules for one particular alert trigger.
List Dashboards
Generates a list of every dashboard you have created in Adafruit IO.
List Data
Fetches a list of all available metrics for a defined data feed.
List Feeds
Lists every single data feed that is currently active in your account.
List Groups
Returns an exhaustive list of all organizational groups you've set up for your...
List Triggers
Provides a comprehensive list of every alert or trigger rule configured in the...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The Adafruit IO integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Adafruit IO, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Adafruit IO. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 10 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Sifting through sensor readings manually is tedious.
Right now, checking your system means logging into the platform's web UI. You click on a group to see which sensors are reporting; then you have to check separate dashboards for different metrics—the temperature tab here, the pressure chart there. If you need to know if an alert rule is active, it requires navigating through multiple setup menus and copying down IDs just to track everything.
With this MCP, your agent handles that whole process in a single conversation. You simply tell it what you want: 'Show me all data points for the main facility group.' It runs the necessary checks—listing groups, fetching dashboards, reading specific feeds—and gives you a clean answer immediately.
The Adafruit IO MCP provides complete control over your sensor metrics.
You no longer have to write code just to map out what’s available. You can start by calling `list_feeds` to see every data stream, then use `get_group` on the top-level organization, and finally confirm status using `list_triggers`. Every piece of information is surfaced without you having to manually build the sequence of API calls.
What’s different now is that your AI agent knows the entire language of the platform. It doesn't just retrieve a value; it understands how groups relate to feeds, and how those feed values connect to active triggers.
What your AI can actually do with this
Your AI client handles the complexity of real-world sensor networks. Instead of having to write multiple functions just to check what’s going on with a group of devices, this MCP lets your agent interact with the entire data model via natural language. You can ask it to list all available feeds and then drill down to retrieve specific measurements from any of those sources.
It's how you monitor everything—from basic temperature readings to complex dashboard status updates—all through one connection. When paired with Vinkius, your agent gets immediate access to this connectivity, making managing diverse hardware data much simpler than juggling multiple SDK calls or logging into a separate portal. You manage the entire lifecycle of your IoT data: grouping, viewing dashboards, getting raw sensor metrics, and even checking which triggers are set up for alerts.
019dd0b2-cab1-7349-a115-0dc4855ae500 
Here's how it actually works
The bottom line is you get immediate access to every element of your IoT setup—feeds, groups, dashboards, and triggers—without writing any underlying hardware connection code.
You connect your Adafruit IO account using your AIO Key to Vinkius. Your AI client handles the secure authentication.
Your agent sends a request (e.g., 'Show me all feeds for weather data'). The MCP maps that request to the appropriate internal tool calls.
The system executes the necessary API calls and returns structured, plain-language data back to your AI client.
Who is this actually for?
The embedded systems engineer who gets tired of calling out dozens of API endpoints just to check a single device status. The DevOps architect who needs to automate alerts based on live sensor metrics, not just scheduled checks.
They use this MCP to define the entire data model—setting up groups and feeds—and then test connectivity by listing all available dashboards.
This engineer uses it to monitor system health. They'll ask the AI client to check every active trigger or list out data points from multiple sources before a scheduled run.
They use this MCP to ingest and validate sensor readings in real-time, retrieving specific measurements using tools like get_data for immediate processing.
What Changes When You Connect
Stop writing boilerplate API calls. Your agent can list all feeds using list_feeds and then immediately get the details for any single feed with get_feed, all in one prompt.
Define and check alert rules easily. Instead of navigating multiple menus, you can use list_triggers to see every active alert, or use get_trigger to verify a specific threshold's settings.
Get granular status updates instantly. Need the current reading? Use get_data. If you need to check all potential metrics for that sensor first, run list_data before asking for the point value.
See your whole picture at once. You can get a full overview by calling list_dashboards, allowing your agent to pull up status from multiple sources simultaneously.
Organize your chaos with confidence. Use list_groups and get_group to structure related sensors, letting your AI client know exactly where to look for data.
See it in action
Checking a facility's full status before maintenance.
A facilities manager asks their agent: 'What’s the operational status of all HVAC units?' The agent responds by calling list_groups to find the HVAC group, then using get_dashboard and get_data on that specific group's dashboard feed to report back current temperature readings and system flags.
Validating a new sensor deployment.
An embedded developer needs to confirm if the new moisture sensor is reporting correctly. The agent first uses list_feeds to find the 'moisture' feed, then calls list_data on that feed to see what metrics are available before using get_data to pull a real-time reading.
Auditing alert rules after a system change.
The operations team wants to know if any critical alerts were left behind. They prompt the agent to run list_triggers, and then, for each potential rule found, they use get_trigger to verify the exact threshold value.
Creating a report on all available sensor types.
The architect asks: 'What sensors are we tracking?' The agent calls list_groups first to narrow down the area, and then uses get_group repeatedly until it has gathered sufficient metadata from every group.
The honest tradeoffs
Treating everything as one data source.
A user asks their agent to 'Give me the temperature and list all dashboard names.' The AI struggles because it mixes a specific request (get_data) with a general listing function (list_dashboards).
Break it into two distinct steps. First, ask for the full context: 'List all available dashboards using list_dashboards.' Second, address the data point directly: 'Now, retrieve the latest reading from the temperature feed using get_data.'
Forgetting to list what's available.
A developer tries to read a specific sensor metric without knowing if that feed exists or if it has data points. The request fails with an opaque error message.
Always check the structure first. Before calling get_data, run list_feeds to confirm the stream name, and then use list_data on the resulting feed to ensure the metric you want is supported.
Confusing data points with feeds.
A user asks for 'the humidity reading' but doesn't know if that's a whole feed or just one point. The agent fails to pull the correct context.
Start by listing the structures: Use list_feeds to get all possible feeds, then use get_feed on the relevant name to confirm it holds humidity data.
When It Fits, When It Doesn't
Use this MCP if your system relies on real-time or structured sensor metrics from a centralized platform. You need an agent that can navigate the full hierarchy—from listing all groups, down to checking specific alerts using get_trigger, and finally pulling raw values with get_data. Don't use it if your process is purely about user management, internal ticketing, or general business logic that doesn't involve hardware monitoring. If you only need basic data retrieval without needing to check triggers, stick to a simpler messaging tool; this MCP handles the entire infrastructure layer.
Questions you might have
How do I list all my IoT sensor feeds using list_feeds? +
Just ask your agent to run list_feeds. It will return a comprehensive list of every data stream you have active in Adafruit IO, letting you know what sensors are connected.
Can I check an alert threshold using get_trigger? +
Yes. To view the exact parameters and rules for any single alert, use get_trigger. This lets your agent pull up specific details about how thresholds were set.
What is the difference between list_data and get_data? +
Use list_data when you need to know what metrics a feed supports. Use get_data when you want the actual, current value of one specific metric.
How do I find out what groups are available? (Using list_groups) +
Simply request that your agent runs list_groups. It will return a complete inventory of all organizational groupings you've set up for your hardware data.
Before running any tool like `get_data`, what credentials does the Adafruit IO MCP require? +
You must provide your AIO Key during setup. This key authenticates your agent's connection to your specific IoT account, ensuring that every action you take is scoped only to data belonging to you.
I need to see all available dashboards; how do I use `list_dashboards`? +
list_dashboards returns a comprehensive list of every dashboard tied to your account. This output gives you the precise names or IDs needed for subsequent calls, such as when you want to call get_dashboard.
If I run `get_dashboard` with an ID that doesn't exist, what should my agent expect? +
The MCP will return a standard API error code and message. Your client needs to check for these specific failure codes before attempting to process the dashboard data.
How do I use `list_triggers` to see all active automation rules? +
list_triggers pulls a complete inventory of every defined trigger rule. From this list, you can identify the specific ID needed for the get_trigger tool to confirm its current status or settings.
Where do I find my AIO Key? +
Your AIO Key can be found by clicking the golden 'AIO Key' button on any page in Adafruit IO.
What access does this MCP need? +
It requires your Username and AIO Key to access your feeds and dashboards.
How do I send data to a feed? +
You can use the agent to create a new data point in a specific feed using the feed key.
We've already built the connector for Adafruit IO. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 10 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.