Twitch MCP Server

Twitch MCP Server using Helix API

Local serverstdio

What is the Twitch MCP server?

Twitch MCP server exists for a simple reason — assistants are far more useful when they can act on Twitch directly instead of describing what you should do. Twitch MCP Server using Helix API.

What you get

A Model Context Protocol (MCP) server that interacts with the Twitch API. This server utilizes the Twitch Helix API to retrieve channel information, stream details, game data, and more.

  • Get channel information (profile, description, creation date, etc.)
  • Get stream information (title, game, viewer count, start time, etc.)
  • Get list of top games
  • Search categories/games
  • Search channels
  • Get live streams (filterable by game and language)

What the assistant can call

Once Twitch is connected, these are the calls the assistant has available:

  • Debugging — Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP

Configuration and credentials

You will need 2 environment variables: TWITCH_CLIENT_ID, TWITCH_CLIENT_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Node.js (v18 or higher recommended) - Twitch Developer Account - Twitch API Client ID and Client Secret - Twitch GraphQL Client ID (for video comments feature)

Setting it up

@mtane0412/twitch-mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Twitch's toolset — Debugging — is a fair guide to whether it matches your workflow. It is maintained by mtane0412; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the twitch mcp server does with a few real requests.

Available tools

ToolWhat it does
DebuggingSince MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script:

How to install the Twitch MCP server

{
  "mcpServers": {
    "twitch-1": {
      "command": "npx",
      "args": ["-y", "@mtane0412/twitch-mcp-server"],
      "env": {
        "TWITCH_CLIENT_ID": "your-value",
        "TWITCH_CLIENT_SECRET": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Node.js (v18 or higher recommended) - Twitch Developer Account - Twitch API Client ID and Client Secret - Twitch GraphQL Client ID (for video comments feature)
VariableDescriptionRequired
TWITCH_CLIENT_IDConfiguration value read at startup.Optional
TWITCH_CLIENT_SECRETCredential the server authenticates with.Yes

Example prompts to try

  • Use Twitch to Debugging.

Frequently asked questions

It connects Twitch to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Debugging) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Twitch directly.