Twitch MCP Server

Created By
TomCoolsa year ago
A Model Context Protocol (MCP) server which allows MCP Clients (such as Claude) to connect to Twitch Chat.
Overview

what is Twitch MCP Server?

Twitch MCP Server is a Model Context Protocol (MCP) server that enables MCP Clients, such as Claude, to connect to Twitch Chat.

how to use Twitch MCP Server?

To use the Twitch MCP Server, you need to build it locally using Maven and then run it with the appropriate configuration for your Twitch channel and API key.

key features of Twitch MCP Server?

  • Integration with Twitch Chat for real-time communication.
  • Supports multiple MCP Clients.
  • Built using Quarkus for efficient performance.

use cases of Twitch MCP Server?

  1. Connecting AI chatbots to Twitch Chat for enhanced interaction.
  2. Enabling automated responses in Twitch streams.
  3. Facilitating real-time data exchange between Twitch and other applications.

FAQ from Twitch MCP Server?

  • Can I use this server with any Twitch channel?

Yes! You can configure it to connect to any Twitch channel by providing the channel name and API key.

  • Is there a pre-built version available?

No, currently you need to build it locally as it is not pushed to Maven Central.

  • What technologies are used in this project?

The project is built using Java, Quarkus, and follows the Model Context Protocol.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
TomCools
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago