Bolt Iot for AI agents
Bolt IoT is a platform that hobbyists and businesses use to connect sensors and actuators to the internet and read or write to them remotely. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Bolt Iot.
Read a sensor value
Run an analog or serial read on a connected Bolt device to check a sensor value in real time.
Check device online status
Read-only lookup of whether a Bolt device is online before sending it a command.
Require approval before writing to a pin
Treat a digital or serial write to a device's pin as needing confirmation since it changes real hardware.
6 Bolt Iot actions, graded by risk.
Every Bolt Iot action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
1Look things up. Allowed by default.
- bolt_iot.check_device_statusCheck Bolt device online status
write
5Create and change things. Allow, or ask the user first.
- bolt_iot.analog_readAnalog Read
- bolt_iot.serial_readBolt IoT Serial Read
- bolt_iot.serial_writeBolt IoT Serial Write
- bolt_iot.digital_writeBolt IoT Digital Write
- bolt_iot.serial_write_readBolt IoT Serial Write & Read
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Bolt Iot in three steps.
- 01Your users connect Bolt IotThey add their Bolt Iot api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “analog Read” can wait for the user to approve.
- 03Any agent can actYour agent calls Bolt Iot through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('bolt_iot', { read: 'allow', write: 'ask', // analog_read destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Bolt Iot connects.
Users add their Bolt Iot api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Bolt Iot connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Bolt Iot from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Bolt Iot and Arc0, answered.
Can I use Bolt Iot with Claude, ChatGPT or Cursor?
Yes. Connect Bolt Iot to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Bolt Iot actions you allow.
How do users connect Bolt Iot?
Users add their Bolt Iot api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Bolt Iot actions can my agent take?
6 in total: 1 read, 5 write and 0 destructive, such as “analog Read”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Bolt Iot?
Yes. Allow read actions and deny writes in the Bolt Iot policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Bolt Iot too?
Yes. The same Bolt Iot connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Bolt Iot into your agent.
Your users connect Bolt Iot once, under your brand. Your agent gets 6 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan