Integration

Demio integration

Demio webinar API v1: list the events of the account, read one event with all its sessions, read a single session, register someone and get back their personal join link, and pull the participation report of a finished session. The key and the secret travel in two dedicated headers.

Connect Demio How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Demio.Built from the 6 Demio tools below, on the connection you add once.

Common Demio use cases

choosing the session to register a lead for
publishing the upcoming webinar list on a site
registering a lead captured on your own landing page
sending the replay only to the people who did not attend
validating newly entered credentials before scheduling a job
checking whether a session already finished before asking for its report
pushing the attendee list into a CRM after a webinar
listing every past session before pulling their reports
confirming you are on a live account rather than a sandbox
reading the start time of a session to schedule a reminder

What you can do with Demio

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Event, 2 operations

get_eventGet eventGETRetrieves a Demio event with all of its sessions.
list_eventsList eventsGETLists Demio events with their next session.

Credential, 1 operation

pingPingGETChecks that the Demio key and secret are accepted.

Participant, 1 operation

list_session_participantsList session participantsGETReturns the participation report of a Demio session.

Registrant, 1 operation

register_participantRegister participantPUTRegisters someone for a Demio session and returns their join link.

Session, 1 operation

get_event_sessionGet event sessionGETRetrieves a single session of a Demio event.

Use Demio from Claude Code, Cursor or Codex

Connect Demio in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Demio operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Demio

Create your workspace
Sign up free. Nothing to install.
Connect Demio once
Add your Demio connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Demio integration FAQ

What can you do with the Demio integration?

LiveContext exposes 6 operations on Demio, covering event, credential, participant and registrant. Common uses include choosing the session to register a lead for, publishing the upcoming webinar list on a site and registering a lead captured on your own landing page.