- Home
- MCP servers
- Twitch
Twitch
- javascript
0
GitHub Stars
javascript
Language
7 months ago
First Indexed
3 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": {
"mcp-mirror-mtane0412_twitch-mcp-server": {
"command": "npx",
"args": [
"@mtane0412/twitch-mcp-server"
],
"env": {
"TWITCH_CLIENT_ID": "YOUR_CLIENT_ID",
"TWITCH_CLIENT_SECRET": "YOUR_CLIENT_SECRET"
}
}
}
}You run a Twitch MCP Server to interact with the Twitch API via MCP clients. It exposes endpoints to fetch channel and stream data, search categories, access emotes and badges, manage clips and videos, and retrieve comments from archived videos, all through a lightweight, structured MCP interface that can be queried by any compatible client.
How to use
You connect to the Twitch MCP Server from an MCP client to request data such as channel details, live stream info, top games, and user data. You can filter live streams by game or language, fetch global emotes and chat badges, access clips and videos from channels, and even retrieve comments from archived videos. Use the MCP client to call the available endpoints and display the results in your UI or workflows.
How to install
Before you begin, ensure you have Node.js installed (v18 or higher is recommended) and a Twitch Developer Account with a Client ID and Client Secret.
npm install @mtane0412/twitch-mcp-server
# Create a local environment file or set environment variables directly
# TWITCH_CLIENT_ID and TWITCH_CLIENT_SECRET are required
# Example using a .env file:
TWITCH_CLIENT_ID=your_client_id
TWITCH_CLIENT_SECRET=your_client_secret
# If you prefer a shell export, you can set them like this:
# export TWITCH_CLIENT_ID=your_client_id
# export TWITCH_CLIENT_SECRET=your_client_secret
# Start the MCP server
npx @mtane0412/twitch-mcp-server
Configuration and startup notes
The server requires two environment variables to authenticate with Twitch: TWITCH_CLIENT_ID and TWITCH_CLIENT_SECRET. You can provide them via a .env file or directly in your shell environment. A simple .env example is shown in the install steps.
Troubleshooting and debugging
If you run into issues starting the server, check that your environment variables are accessible to the process. For debugging, you can use the MCP Inspector tool if you need browser-based debugging utilities; this is typically run via npm with a script like npm run inspect.
Notes and security
Keep your Twitch Client Secret secure. Do not commit it into version control. Rotate credentials if you suspect a leak, and prefer environment variables over hard-coded values in all deployment workflows.
Available tools
getChannelInfo
Fetches channel profile data including description, creation date, and other metadata.
getStreamInfo
Retrieves current stream details such as title, game, viewer count, and start time.
getTopGames
Returns a list of top games/categories currently active on Twitch.
searchCategories
Search for games or categories by keyword.
searchChannels
Search for channels by name or description keywords.
getLiveStreams
Get live streams with optional filters like game and language.
getGlobalEmotes
Fetches the global emotes available on Twitch.
getGlobalChatBadges
Retrieves global chat badges supported by Twitch.
getUserInfo
Get information about a Twitch user.
getClipsFromChannel
Fetch clips published by a specific channel.
getChatSettings
Retrieve chat configuration settings.
getVideosFromChannel
Get videos published on a specified channel.
getCommentsFromArchivedVideos
Access comments from archived videos via GraphQL.