How drio Works - drio Docs

A plain-language architecture overview for operators, buyers, and technical reviewers.

drio is designed so non-technical teams can shape the app experience while technical teams still get clear control points for APIs, auth, and deployment review.

In Plain Language

Your team defines what the assistant should do, how it should look, and which systems it should call. drio turns that configuration into an MCP-compatible runtime that AI clients can use.

Mermaid diagram source:

flowchart LR
  clients["AI clients<br/>ChatGPT · Claude · Cursor"]
  endpoint["drio MCP endpoint"]
  config["App configuration<br/>tools · widgets · branding"]
  upstream["Connected APIs and data"]

  clients -->|MCP| endpoint
  endpoint --> config
  endpoint --> upstream

What drio Handles For You

app structure, tool definitions, and widget rendering
the MCP endpoint used by supported AI clients
branded runtime output for rich content experiences
the builder workflow for configuring tools and API mappings

What Stays In Your Team's Control

which systems the app is allowed to call
whether access is public, shared, or user-specific
how the app should be reviewed, tested, and rolled out
whether the management API is used directly by engineering

Runtime Request Flow

When a user asks the assistant to do something:

the AI client calls your drio MCP endpoint
drio resolves the right app and tool definition
the configured upstream API or data source is called
the response is mapped into the selected widget
the result is returned to the AI client as structured content

Mermaid diagram source:

flowchart LR
  client["AI client"]
  endpoint["drio endpoint"]
  tool["Tool definition"]
  api["Connected API"]
  widget["Widget output"]

  client --> endpoint
  endpoint --> tool
  tool --> api
  api --> widget
  widget --> client

Questions Technical Reviewers Usually Ask

How does auth work?

The answer depends on the app:

shared or public data can use simpler access patterns
protected per-user systems require delegated OAuth

See Add sign-in for protected systems and Delegated OAuth configuration.

What is the management API for?

The management API is separate from the end-user MCP endpoint. It is used to inspect, create, and publish apps programmatically.

See API overview.

Where should rollout ownership live?

drio supports a split model:

GTM and marketing own use case, copy, widget choice, and launch readiness
technical teams review auth, protected APIs, and deeper automation

Use This Page As A Handoff Summary

If you are handing the project to a technical reviewer, send them these pages: