Demio for AI agents
Demio runs live and automated webinars, giving marketers a way to host sessions, engage an audience, and track results for lead generation. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Demio.
Check event attendance
List participants for an event date to see who actually showed up.
Generate a join link
Create a join link for a registrant so they can enter a live session.
Check upcoming event dates
List upcoming event dates before deciding when to schedule a new webinar.
6 Demio actions, graded by risk.
Every Demio action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
5Look things up. Allowed by default.
- demio.get_eventDemio: Get Event by ID
- demio.list_eventsList Demio Events
- demio.list_event_datesList Event Dates
- demio.list_event_date_participantsList Event Date Participants
- demio.pingDemio API Ping
write
1Create and change things. Allow, or ask the user first.
- demio.create_join_linkDemio Create Join Link
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Demio in three steps.
- 01Your users connect DemioThey add their Demio api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “demio Create Join Link” can wait for the user to approve.
- 03Any agent can actYour agent calls Demio through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('demio', { read: 'allow', write: 'ask', // create_join_link destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Demio connects.
Users add their Demio api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Demio connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Demio from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Demio and Arc0, answered.
Can I use Demio with Claude, ChatGPT or Cursor?
Yes. Connect Demio to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Demio actions you allow.
How do users connect Demio?
Users add their Demio api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Demio actions can my agent take?
6 in total: 5 read, 1 write and 0 destructive, such as “demio Create Join Link”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Demio?
Yes. Allow read actions and deny writes in the Demio policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Demio too?
Yes. The same Demio connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Demio into your agent.
Your users connect Demio once, under your brand. Your agent gets 6 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan