AI & MCP
Lumio exposes a remote Model Context Protocol (MCP) server at https://api.lumio.vision/mcp. AI assistants such as Claude Code, Claude.ai, ChatGPT and Grok can use it to read channel information and, with your consent, carry out channel actions. The connection uses OAuth; you do not paste a Lumio API key into the assistant.
Each AI connection belongs to you and reaches only the channels you select. For each channel, effective access is limited by the permissions you granted, your current role in that channel, its enabled features and the channel's write switch. Losing apikeys:create, leaving a channel, or removing it from the connection cuts off that channel without granting access to any other one. The feature:mcp_server flag is available in every plan, including Free; other tools still respect their own feature flags.
Connect and manage an app
Open Settings → You → AI → AI & MCP, or use /dashboard/settings/ai. The page shows the server address, setup steps for supported assistants and your connected apps. It appears when at least one of your channels has feature:mcp_server and you hold apikeys:create there. If an app remains connected after no channel qualifies, the page stays visible with a lock and offers Disconnect.
The sign-in and consent page shows each channel's eligibility and the requested permission groups. Only eligible channels you own and the Read group are selected initially; member channels need an explicit tick. If no eligible channel is selected, Allow stays disabled until you choose one. Chat, event, music and write groups require an explicit choice. Each of the channels, rights and high-risk sections has a Select all / Deselect all control when it contains at least two selectable choices. These controls skip ineligible channels and leave each channel's Write & change switch off. For a channel you do not own, enable that switch separately to allow writing. Sensitive groups require a fresh identity confirmation: with 2FA enabled, use a passkey, authenticator app code or recovery code; without 2FA, use an existing platform sign-in or email password. An ordinary grant can last up to 90 days, with a 30-day sliding refresh window; a high-risk grant is limited to 30 and 7 days respectively.
The app list shows its verification status, destination host, connected and last-used times, rights, expiry and channels. You can change the channel list, switch writing per channel, or disconnect. The Permissions dialog is read-only: disconnect and reconnect to grant different rights. Disconnect offers to switch off automations the app created or last changed (selected by default) and to uninstall extensions it installed (off by default; extension data can be restored for 30 days). A security revocation also switches off affected automations and sends a locked security notice.
What an AI app may do
With the relevant grant, role, feature and write switch, tools can read status, chat, events and music; send chat, moderate, manage playlists, automations, overlays, widgets, extensions and bot settings. Some operations have extra limits: automation nodes need the rights they act with (webhook, OBS and Streamer.bot nodes need automations:edit, a ban needs chat:ban); extension installs must be eligible and cannot purchase an extension or grant it more rights than the app has. Every tool and its exact guard is listed in the MCP reference.
In the Read group, lumio_channel_connections lists a selected channel's connected platforms, including accounts that need reconnection. It requires connections:read and feature:connections for that channel. lumio_login_connections lists your own Lumio sign-in accounts, including multiple accounts on the same platform; it takes no channel and requires no channel permission. lumio_channel_status reports recorded stream status per platform. A platform appears there only after it has reported status, so an empty status result does not mean the channel has no platform connections.
Overlay and widget creation returns a browser-source URL. An AI app can also request an existing URL for a resource it may edit; if none exists, Lumio creates one when writing is enabled for that channel. The URL is a credential for that overlay or widget, so share it only with people who should see its output. Rotate or revoke it in the webapp.
An AI app cannot create credentials, change roles or membership, manage billing, alter OAuth clients, run extension server functions, or use channels outside its grant. Chat and other third-party text is returned as untrusted data, not instructions. Disconnect an app at any time under AI & MCP.
Test-event effects
An app with events:create and Write & change can call lumio_event_test. Its optional show_on_stream setting is off by default. Test events can start bot modules and automations configured to react to tests. A bot may post a chat reply or chat:send message beginning with [Test] even when the test stays off stream. Moderation is always skipped, and OBS, overlays and other stream picture or sound actions run only when show_on_stream is true. This is a residual effect of granting events:create; review an app's channel permissions and connected bot settings before allowing it to send tests.