Connect your AI to Atrio
Connect Atrio to Claude, ChatGPT, or Gemini once. After that, right inside your AI tool, you can say "send this artifact to Atrio" — and it's hosted at a private, permissioned link with no copy-paste. Your agent can also pull back the artifacts and data you're allowed to see, and reason over them in your own AI session, on your own plan.
Your connector URL
Add this as a custom MCP connector in your AI tool:
https://app.atrio.cc/api/mcp
You'll be asked to sign in to Atrio the first time. That's how your agent proves who it is — after that it can only reach what your account is permitted to, and every data action is recorded in your audit log. There are no API keys to paste and nothing is public: identity is always verified before any data or AI feature is reachable.
What your agent can do
Once connected, these tools are available to your AI automatically — you don't need to memorise them, your agent discovers and uses them on its own:
| Tool | What it does |
|---|---|
| Who am I | Confirms which Atrio workspace and plan the connection is signed in as. |
| Save an artifact | Hosts an artifact your AI just built at a shareable Atrio link. |
| Attach data | Sends the dataset behind an artifact so trusted viewers can explore it. |
| List artifacts | Shows the artifacts in your workspace you're allowed to see. |
| Get an artifact's data | Pulls the underlying data back so your agent can answer questions about it. |
| Secure upload | A signed slot for large artifacts and datasets that are too big to send inline. |
Permissions are resolved on every single call, so a connected agent only ever sees what you're entitled to at that moment — not the whole workspace.
Setting it up
Claude
- Open Settings → Connectors.
- Click Add custom connector.
- Paste the Atrio URL above and save.
Available on Claude Pro, Max, Team, and Enterprise. On Team/Enterprise an owner can add it once for
the whole workspace. Claude can also send large, data-heavy artifacts end-to-end — an owner
allows *.atrio.cc once under network egress so its sandbox can upload directly.
ChatGPT
- Open Workspace settings → Permissions & roles → Connected data.
- Turn on Developer mode (custom MCP connectors).
- Add a connector and paste the Atrio URL above.
Custom MCP connectors are on ChatGPT Business, Enterprise, and Edu (an admin enables Developer mode). ChatGPT runs the connector on OpenAI's side; for a very large artifact, paste its HTML into Atrio instead.
Gemini
- In Gemini Enterprise, add a custom MCP server data store.
- Allow Atrio's connector domain and paste the URL above.
- An admin may need to override the policy that blocks custom MCP data stores.
Custom remote-MCP support is a Gemini Enterprise (Google Cloud) feature.
Interactive artifacts (Team+)
New apps (JSON state, forms, timelines): window.atrio inside hosted artifacts (push_site with platform API).
Site platform API.
Artifacts can contain interactive HTML, scripts and assets. Applications that depend on an external server still need that server; uploading HTML does not transfer its backend.
Don't have an AI tool with connectors?
You don't need one. Every Atrio artifact shared with data can be interrogated right in the browser with "Ask the data" — no setup, no connector. And you can always paste an artifact's HTML straight into Atrio to host it.
Standing instruction
Paste this into a Claude Project, a ChatGPT custom instruction, or an AGENTS.md so the agent
hosts what it builds here without being asked each time:
Atrio hosts what you build. When you produce an artifact, report, or web page for the user, publish it with push_dashboard (or push_site for multi-file builds), attach the underlying data with attach_dataset, and paste the tool response `message` field verbatim (includes viewer_url). For a saved draft, return the tool message with preview_url; do not claim it is published. For published artifacts, viewer_url is the same link as in the Atrio library — give users only viewer_url (or paste message); never add workspace, open, or /v/ token links in chat. Never shorten URLs, never invent paths. If the user has several workspaces, call atrio_whoami and pass workspace_id. At the start of a session about an existing Atrio page, call list_feedback to see comments people left; after addressing them, publish a new version and resolve_feedback. Use publish:false to save a draft. To wrap an app that already has an https address, call register_external_artifact. That stores the address only — it does not import the app or connect its backend.
Troubleshooting
- "Connection expired" / asked to reconnect? Open the Atrio connector and click Connect again to re-authenticate. Your artifacts, data, and permissions are unchanged — reconnecting just refreshes the sign-in.
- Your tool asks for an "OAuth Client ID", or says automatic registration isn't supported? Most tools register themselves automatically and won't ask. If yours does, add Atrio through its custom / advanced connector option — there's no client secret (it connects as a public app). Still stuck? Email hello@atrio.cc with the reference code your tool shows and we'll trace it.
Ready? Start a free 14-day trial — no card required.