For platforms & integrators
Your tool runs the stream. We'd like to keep the event.
OneStarLive is an events layer for Twitch creators. We want to build a Model Context Protocol (MCP) server and a REST API on top of it, so that AI agents, AI assistants and stream-automation tools can create and run real Twitch stream events directly.
On the roadmap
None of that integration exists yet. This page is a description of what we intend to build, published early and on purpose — we would rather design it with a few partners than guess at it alone and hand you something shaped wrong. If you build in this space, the useful thing you can do right now is tell us what you'd need.
Why we think this is worth building
If your software schedules streams, drives OBS, sets up scenes or handles a creator's going-live routine, you already do the hard part. You produce the intent. What you probably don't have is anywhere for it to live afterwards.
A scene switch isn't an object. A poll that closes when the stream ends leaves nothing behind. The stream happens, it's good, and then it's gone — and everything the audience did during it goes with it. That's the gap we keep running into from our side too, and it's the one we think an events layer underneath your tool would close.
What already works
This part isn't roadmap. It's running in production today, for creators using OneStarLive directly, and it's what any integration would write into.
Every event has a public page, before and after
From the moment an event is created it has a shareable page — the date, the schedule entry, a way for viewers to say they're coming. Afterwards that same URL becomes the recap: the clips made during the stream, the VOD, how a vote landed, what a goal reached. Same link throughout.
What the audience does outlives the broadcast
Bits goals, votes on outcomes and reactions attach to the event, not to the live session. A poll is still readable a month later on a page anyone can open without signing in.
Events are listed on Explore
Explore is our public listing of what's live now and what's coming up across every creator on OneStarLive, arranged by category, region and who a visitor already follows. Events created through an integration would appear there on the same terms as any other — so a creator using your tool gets found, not just automated.
Creators keep control of that: anyone can opt out of public listing per event or per account, and the opt-out is enforced in the database query rather than filtered out afterwards.
What we want to build
Two front doors onto the same thing. A REST API for tools that already speak HTTP, and an MCP server exposing the same operations as tools an agent can call directly, so you don't have to write an integration layer per operation.
We want both to sit on one shared internal service so they can't drift apart. Being honest about the order of work: that service doesn't exist yet either — today the event logic lives inside a much larger controller, and pulling it out is the first real piece of this and the thing everything else waits on.
How we think connecting would work
The MCP server would be a remote endpoint that an MCP-compatible client — an AI assistant, an agent framework, or a desktop tool that speaks Model Context Protocol — adds like any other MCP server. We're planning to authenticate it with a OneStarLive MCP key: a key issued to you, which the server would exchange for a short-lived token scoped to the creator who authorised it.
The intent is that no Twitch credentials pass through your product, and that a key never reaches a creator who hasn't connected their own account. There's no endpoint URL to publish yet, and no keys to issue.
The operations we have in mind
Roughly what we think an agent would need. This list is a starting point, not a specification — if something obvious is missing for your use case, that's exactly the kind of thing worth telling us now.
| Operation | What it would do |
|---|---|
| Create Event | Bring an event into existence with a title, category and optional goal or vote. |
| Schedule Event | Give it a date and time, and put it on the creator's channel schedule. |
| Transition to Live | Move the event into its live state and announce it. |
| End Event | Close it out and trigger the recap. |
| Send reminders | Fire the starting-soon, going-live or wrap-up announcement to whichever destinations the creator has connected, Discord included. |
| Add Clip | Attach a clip or marker so it reaches the recap. |
| Promote Event | Raise an event's prominence on discovery surfaces. Furthest out of these. |
One thing we can build on rather than invent: the event lifecycle is already a real state machine with declared legal transitions, and every announcement is already logged per destination as sent, skipped or failed. So an agent shouldn't be able to put an event into a state that makes no sense — an event that already ended won't end twice, and a reminder won't go out for a stream three weeks away. Exposing that log back to your tool is part of what we'd want the API to do.
How we'd want the relationship to work
- The creator authorises it. A partner key shouldn't grant blanket access. The creator connects their own account and the key acts only inside what they've allowed.
- You keep your surface. We're not trying to move your users into our product. The event page is where their audience goes, not where they work.
- Attribution without oversharing. We should be able to tell you what your integration produced without handing over creator data that isn't yours.
Money, since you'll ask
OneStarLive is free for creators today. Two paid layers are on the roadmap and neither is priced: promotional credits that raise an event's prominence on Explore, and a monthly subscription for creators who want more than the free tier. We haven't worked out partner terms at all, and we'd rather figure them out in a conversation than publish a rate card at you.
Talk to us
We're at the stage where the input is worth more than the announcement. If you're building something that would use an events layer, tell us what you'd need from it — what you'd want to call, what you'd want back, and what would make it not worth integrating.
Email contact@onestarlive.com. Say what your tool does and where an event object would fit in it. A real person reads it.