Skip to main content
Four tools can return a rich, interactive view instead of raw JSON, for a host capable of rendering one. These are the same four surfaces that carry the most structure in the product, which is why they are the ones worth rendering rather than describing.

​
Text is the designed fallback

A host that cannot render a view gets the same data as text. That is not an error and not a degraded response — the underlying tool result is identical, only the presentation differs.Support for interactive MCP views is still settling across hosts. On claude.ai today the views render as text. ChatGPT likewise.
There is nothing to configure, and no capability to request. Your host either renders the view or it shows the text.

​
Permissions still apply

A view is a rendering of a tool result, not a way around the tool’s gate.
  • Team today and Roster week show only what your credential’s scope permits.
  • Approvals shows only requests you could actually open and decide.
  • Payslip is your own, always — there is no view that shows somebody else’s pay.

​
If a view does not render

Almost always: your host does not support interactive MCP views. This is the expected fallback.
The view’s built assets may be missing from the deployment. That is a server-side build step, not something you can fix from the client — report it to whoever operates your OnTime instance.