Twitch

Runs a Twitch-based MCP server that connects to a channel using an API key, enabling MCP-based control and automation.
  • other

6

GitHub Stars

other

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "tomcools-twitch-mcp": {
      "command": "jbang",
      "args": [
        "--quiet",
        "-Dtwitch.channel=YOUR_CHANNEL_NAME",
        "-Dtwitch.auth=YOUR_API_KEY",
        "be.tomcools:twitch-mcp:1.0.0-SNAPSHOT:runner"
      ]
    }
  }
}

The Twitch MCP Server lets you run a Twitch integration as a Model Context Protocol (MCP) server. It connects to Twitch using your channel and API key, exposes actions via MCP, and can be managed with an inspector or Claude Desktop UI for convenient operation.

How to use

You run the MCP server locally and connect to it from an MCP client. Start the inspector to manage MCP servers and then load a configuration that starts the Twitch MCP runner. Use the client’s UI to start, stop, and monitor the Twitch MCP server and interact with it as you would with any other MCP endpoint. The Twitch MCP server is designed to read your Twitch channel and API key from runtime flags, so keep those credentials secure and never share them.

How to install

Prerequisites you need before installing and running the Twitch MCP Server: install Java with a compatible JDK, install Maven to build the project locally, and ensure you have a tool to start MCP configurations (the examples use JBang). You will also want Node.js to run the MCP Inspector during testing.

Step-by-step commands to prepare and run the Twitch MCP Server locally:

mvn install

# Start the local MCP inspector (in a separate terminal)
npx @modelcontextprotocol/inspector

# Create an MCP configuration to run the Twitch MCP runner via JBang
# The following configuration is used in the inspector or in Claude Desktop

```json
{
  "mcpServers": {
    "twitch_mcp_tomcools": {
      "command": "jbang",
      "args": [
        "--quiet",
        "-Dtwitch.channel=YOUR_CHANNEL_NAME",
        "-Dtwitch.auth=YOUR_API_KEY",
        "be.tomcools:twitch-mcp:1.0.0-SNAPSHOT:runner"
      ]
    }
  }
}

If you are configuring Claude Desktop, paste the same configuration into claude_desktop_config.json

{
  "mcpServers": {
    "twitch_mcp_tomcools": {
      "command": "jbang",
      "args": [
        "--quiet",
        "-Dtwitch.channel=YOUR_CHANNEL_NAME",
        "-Dtwitch.auth=YOUR_API_KEY",
        "be.tomcools:twitch-mcp:1.0.0-SNAPSHOT:runner"
      ]
    }
  }
}

Start the server and verify it appears in the UI

Open the inspector UI and locate the Twitch MCP server named twitch_mcp_tomcools. Start it and monitor the console output for successful connection messages and activity from your Twitch channel.

## Additional content

Notes and considerations: the Twitch MCP server is built with a Quarkus-based MCP runner and is intended to be run locally. Keep the API key secure and rotate credentials if exposure is suspected. The inspector provides a convenient way to manage multiple MCP servers from a single interface, while Claude Desktop offers an integrated UI to control and monitor your MCP runners. If you modify channel or API key values, restart the MCP server to apply changes.

## Available tools

### inspector

Local MCP inspector service used to manage and monitor MCP servers from a centralized UI.

### claude\_integration

Claude Desktop integration to load MCP configurations and start Twitch MCP servers from a JSON config.
Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational