Skip to content
Talk to sales Start building
Twitch logo

Twitch MCP server

Twitch is the world's leading live streaming platform for gamers and the things we love!

Twitch is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Start building See the Twitch integration
Tools
1
Works with
Any MCP client
Auth
OAuth 2.0
License
MIT, open source
Updated
September 2026

About the Twitch MCP server

Connect Twitch once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Twitch and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Twitch tools your AI can run

Once connected, your assistant can call any of these Twitch actions by asking in plain language.

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Triggers

Twitch events your agent can watch

These start a run the moment something happens in Twitch, so work gets picked up on its own.

  • Streamer(s) Go Live

    Triggers when a stream from a list of streamers has started

    1 field

Give your assistant Twitch

Connect Twitch once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Get your server URLTalk to sales

Twitch MCP, answered.

No. That is the point of it. One Activepieces server exposes Twitch alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Twitch in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 1 tool, including Custom API Call, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.