Build MCP Apps
Ask the workspace agent to create an HTML app, connect it to permitted tools, validate every state, and prepare it for sharing.
#Build the HTML file with the agent
- 01
Describe the job
Name the viewer, decisions the app should support, required data, and any actions it may take.
- 02
Name the connections
Tell the agent which available connection tools the app may call.
- 03
Create the file
Ask the agent to build a self-contained HTML file in Workspace Files.
- 04
Inspect HTML source
Open HTML source and review labels, actions, data limits, and error handling.
- 05
Open Preview
Interact with the app in the workspace and refine it with the agent.
#Static report or MCP App
| Type | How it gets data |
|---|---|
| Static interactive HTML report | Uses data already gathered and saved into the HTML. It does not call tools after opening. |
| MCP App | Calls permitted connection tools at runtime to load current information or perform an action. |
#Validate loading, success, empty, and error states
- Loading clearly shows that the app is waiting for a tool result.
- Success shows useful data with source and freshness context.
- Empty explains that the call succeeded but returned nothing relevant.
- Error explains what failed and gives the viewer a safe next action.
- Live, sample, and cached data are labeled accurately.
- Queries and result sets are bounded so the interface stays responsive.
#Protect actions with permissions and confirmation
The app uses the current viewer’s connections and effective permissions. Require a clear confirmation before a control sends, creates, updates, deletes, or otherwise changes external data. Handle a denied or unavailable tool as a normal app state.