OpenUI Cloud for AI agents
OpenUI Cloud by Thesys generates interactive user interfaces from prompts and manages the conversations and artifacts behind them. Product teams use it to prototype UI screens quickly. 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 OpenUI Cloud.
Generate a UI from a prompt
Create an interactive interface mockup from a description of the screen needed.
List saved artifacts read-only
Check previously generated UI artifacts before creating a new variation.
Delete a conversation with approval
Remove an old conversation thread only after confirming its artifacts are no longer needed.
8 OpenUI Cloud actions, graded by risk.
Every OpenUI Cloud action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
4Look things up. Allowed by default.
- openui_cloud.get_artifactGet Artifact
- openui_cloud.list_artifactsList Artifacts
- openui_cloud.list_conversationsList Conversations
- openui_cloud.list_conversation_itemsList Conversation Items
write
3Create and change things. Allow, or ask the user first.
- openui_cloud.create_conversationCreate Conversation
- openui_cloud.generate_uiGenerate UI
- openui_cloud.rename_conversationRename Conversation
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- openui_cloud.delete_conversationDelete Conversation
OpenUI Cloud in three steps.
- 01Your users connect OpenUI CloudThey add their OpenUI Cloud api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Conversation” can wait for the user, and “delete Conversation” can be denied outright.
- 03Any agent can actYour agent calls OpenUI Cloud through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('openui_cloud', { read: 'allow', write: 'ask', // create_conversation destructive: 'deny', // delete_conversation }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How OpenUI Cloud connects.
Users add their OpenUI Cloud 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 OpenUI Cloud 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 OpenUI Cloud from any agent.
OpenUI Cloud and Arc0, answered.
Can I use OpenUI Cloud with Claude, ChatGPT or Cursor?
Yes. Connect OpenUI Cloud 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 OpenUI Cloud actions you allow.
How do users connect OpenUI Cloud?
Users add their OpenUI Cloud 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 OpenUI Cloud actions can my agent take?
8 in total: 4 read, 3 write and 1 destructive, such as “create Conversation”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in OpenUI Cloud?
Yes. Actions like “delete Conversation” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call OpenUI Cloud too?
Yes. The same OpenUI Cloud connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug OpenUI Cloud into your agent.
Your users connect OpenUI Cloud once, under your brand. Your agent gets 8 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan