What OKO MCP does
OKO MCP is a package that connects an AI client to your OKO account over the Model Context Protocol. The client acts as the organizer behind the key, within the permissions you gave the key.
It can create, duplicate, move, restore and delete events. It can set up the video, forms, polls, the call to action, cards, banners and images. It can run the chat and moderation, start and end analytics sessions, and read analytics, session reports, geography and form leads. It can manage workspaces and invitations, publish Telegram posts, and read your plan and lumen balance.
Access to OKO MCP is part of every plan. The operations you run through it cost what they cost in the cabinet.
Connect it
- Have an active OKO organizer account. The package cannot create one.
- Open “OKO MCP” in the sidebar of the cabinet. This install center is at /app/mcp.
- Choose your client: “Claude Code”, “Codex” or “Other MCP”.
- Create a key and pick its permissions: “Webinar operator”, “Full access”, “Read-only” or “Customize”. OKO shows the full secret once, so copy it into a secret manager or a local environment variable.
- Warm the package up once in a terminal with npx -y @okostream/mcp@latest --help, and wait for the line "OKO MCP Server". It needs Node.js 20.18.1 or newer. Skipping this step can make the AI client abort the first install on a timeout.
- Add the package to your client. For Claude Code the command is claude mcp add oko --scope user --env OKO_API_KEY=<your key> -- npx -y @okostream/mcp@latest. The install center prepares the ready command or config with your key already in it.
- Check the connection. Ask your AI client: "Use OKO to show who I am and list my latest webinars."
What it cannot do
It does not host, start or stop video. Your video runs in your own player. The session tools of OKO MCP start and end analytics sessions only.
It does not create accounts, accept the terms or take a payment. Plans and lumens are bought only in the cabinet, and no tool asks for a password or a card. It can read your balance, but it cannot buy lumens.
It cannot turn on the live control room. You buy the control room in Analytics.
It has no platform-owner privileges and no general access to the database. A key reaches only what you can reach, and only through the permissions you gave it.
Keys, permissions and confirmation
Each key has a label and a set of permissions, such as reading events, writing the setup, controlling live blocks, moderating the chat or writing Telegram posts. Under “Access keys” you see when each key was last used.
To stop a key, press “Revoke”. Access closes immediately.
Actions that spend lumens, publish a page, delete something, post to Telegram or change a live setting show a preview first. They run only after you confirm.
Frequently asked questions
Which AI clients work with OKO MCP?
The install center has steps for Claude Code, Codex and a generic option for other clients. Any MCP client that can run a command with arguments and environment variables can run the package. The extension for Claude Desktop is no longer distributed.
Does OKO MCP cost anything?
Access is part of every plan and has no separate fee. The operations you run through it cost the same lumens as in the cabinet.
Can Claude publish a page or spend my lumens without asking me?
No. Publishing, starting a session and posting to Telegram show the charge first and take nothing until you confirm. Your key's permissions limit what the client can do at all.
How do I cut off an AI client?
Revoke its key under “Access keys” in “OKO MCP”. Access closes at once, and you can create a new key for the next client.