AI & Machine Learning · OpenUI Cloud + Claude
OpenUI Cloud MCP with Claude: Turn Prompts into Interactive Business Interfaces
The short answer
Claude works with OpenUI Cloud through the Model Context Protocol (MCP), a secure standard that lets Claude use the tool with permissions your organisation controls. Once connected, Claude can ask OpenUI Cloud to generate interactive interfaces, manage conversations, create artifacts and query UI outputs using natural language.
What is OpenUI Cloud?
OpenUI Cloud is an API platform from Thesys for generating interactive user interfaces, conversations and artifacts. It turns written prompts into rich, app-like screens through OpenAI-compatible APIs. Product teams, developers and operations leaders use it to build chatbots, agent front ends and internal tools without designing every screen by hand. It suits organisations that want interfaces produced quickly from descriptions of what people need.
How Claude connects to OpenUI Cloud through MCP
The Model Context Protocol (MCP) is an open standard that lets Claude securely use other software, reading information and taking actions with permissions the organisation controls. Think of it as a universal adapter between Claude and the tool. For OpenUI Cloud, connection is made using an API key that your team issues and can revoke at any time.
Once connected, Claude can work with OpenUI Cloud in plain language. For example, it can request a new interactive interface for a given purpose, manage ongoing conversations, create artifacts such as reusable interface components, and query the outputs it has produced. Capabilities depend on the access your team grants, and we typically start with read-only or limited permissions.
Permissions and approvals keep people in charge. Access is scoped to the minimum needed for each workflow. Actions that publish interfaces to end users, change live content or share data outside the organisation can require a named person to approve them first. Every action is logged so your team can review what was done and by whom.
What you can automate
Customer support screens
A support lead describes the screens agents need for a refund or order-change request. Claude asks OpenUI Cloud to generate a clear, interactive form with the right fields and status views. Agents get a consistent tool in minutes, and the team reviews the design before it reaches live staff.
Internal reporting dashboards
A finance manager asks for a monthly spend summary with filters by department and region. Claude requests an interactive dashboard from OpenUI Cloud and queries the outputs in plain language to answer follow-up questions. Managers explore the numbers without waiting for a developer to build each view.
Sales chatbot front ends
A sales operations team wants a chatbot that can show product comparisons, quote options and booking buttons. Claude generates these interactive responses through OpenUI Cloud, keeping the conversation state in view. Prospects get richer answers than plain text, and the team controls which offers can be shown.
Onboarding guides for new staff
An HR team describes a step-by-step onboarding checklist with forms and progress tracking. Claude creates the interface and stores it as a reusable artifact for future hires. New employees follow a consistent path, and HR updates the artifact in one place when policies change.
Field inspection forms
An operations manager needs a mobile-friendly inspection form with photo fields and dropdown checks. Claude requests the interface and refines it through conversation based on feedback from supervisors. Inspections are recorded in a standard format that is easier to review later.
An end-to-end workflow: Support escalation console
TriggerA customer case is escalated to a senior agent in the ticketing system.
Claude reads the escalation details from the ticketing system and summarises the customer's history.
Claude asks OpenUI Cloud to generate an interactive case console showing the summary, order details and suggested actions.
The senior agent reviews the console and can ask Claude to adjust the layout or add a field through conversation.
When the agent chooses a resolution, Claude records the outcome back in the ticketing system after the agent confirms.
Claude saves the console as an artifact so the same format can be reused for similar escalations.
OutcomeSenior agents resolve escalations with a consistent, clear view of each case. Typical teams report less time spent switching between screens, though results vary by workflow and volume.
How we set it up
Free automation audit
We review how your teams work today and identify the interfaces and workflows worth automating with OpenUI Cloud. You leave with a clear list of priorities and an estimate of effort.
Secure connection
We connect Claude to OpenUI Cloud using the API key sign-in method, stored in your secrets manager with least-privilege access. Your team keeps control of the key and can rotate or revoke it at any time.
Workflow design
We design the end-to-end workflow across OpenUI Cloud and your other systems, such as Microsoft 365, your CRM, ERP or ticketing tool. People approve any action that publishes or changes live content.
Testing with real cases
We test the workflow against real past requests to check the interfaces are accurate, useful and well-formed. We adjust prompts and permissions until results meet your standard.
Launch and training
We launch with monitoring and audit logs turned on, then train your team on how to request interfaces, review outputs and handle exceptions.
Who benefits
- Product managers
- Test interface ideas in hours rather than weeks, using plain-language requests.
- Operations leaders
- Give teams standard tools for recurring tasks without long development queues.
- IT and security heads
- Control access with scoped API keys and full audit logs.
- Customer support managers
- Provide agents with clear, consistent screens for complex cases.
Security and control
- Use a dedicated API key with least-privilege access, stored in a secrets manager and rotated on a set schedule.
- Require named human approval before any generated interface is published to customers or live staff.
- Keep audit logs of every request, generated interface and action so reviews are possible.
- Test generated interfaces against real cases before launch and review them regularly for accuracy.
- Restrict which data Claude can pass to OpenUI Cloud, avoiding sensitive personal information unless your policy allows it.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host their Claude workflows in a region that matches their data handling requirements. In India, deployments can be designed to meet the Digital Personal Data Protection Act, 2023. Businesses in the UAE and Saudi Arabia can align their setup with local data protection laws. We choose the hosting region with you so the workflow meets your legal and contractual obligations.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the OpenUI Cloud MCP server do?
The OpenUI Cloud MCP server lets Claude use OpenUI Cloud through a standard, secure connection. Claude can request interactive interfaces, manage conversations, create artifacts and query outputs using natural language. Your team controls what Claude is allowed to do, and every action can be logged for review.
Is connecting OpenUI Cloud to Claude secure?
Security depends on how the connection is set up. We use a dedicated API key with least-privilege access, stored in a secrets manager. Sensitive actions can require human approval, and audit logs record activity. We design these controls with your IT or security team before launch.
What can Claude do with OpenUI Cloud once connected?
Typically, Claude can generate interactive interfaces from a description, keep track of ongoing conversations, create reusable artifacts and answer questions about outputs already produced. The exact actions available depend on the permissions your team grants and the workflow we design together.
How long does setup take?
Many projects move from the free audit to a tested launch within a few weeks, depending on the number of workflows and systems involved. A single well-defined interface can be quicker. We give you a realistic timeline after the audit, once we understand your requirements.
What access or plan is needed to use OpenUI Cloud with Claude?
In general, you need an OpenUI Cloud account and an API key that your team creates and manages. The sign-in method is API key. We confirm your account setup and the permissions needed during the audit, so you only grant the access the workflow requires.