RaidRunner

net.raidrunnerPublished by raidrunner.netOfficial publisherv1.0.0Updated Oct 25, 2026

Manage your Twitch raid-train schedule from an AI assistant: claim, release & trade slots via OAuth.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

A remote MCP server that lets an assistant manage a Twitch raid-train schedule by claiming, releasing and trading slots through OAuth.

What you can do
Claim raid-train slots on a Twitch raid schedule through the assistant, using an OAuth-linked account. Release slots you hold and trade slots with other participants. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful for Twitch streamers or raid-train organizers who want to manage their raid schedule conversationally instead of through the web interface.
Requirements
A remote streamable HTTP endpoint at raidrunner.net; no local package or runtime is needed. OAuth authentication is required, so a RaidRunner account and an OAuth sign-in flow are needed. Network access to the endpoint is required.
Before you install
The server acts on a live raid schedule: claiming, releasing and trading slots change shared state and may affect other participants. OAuth grants the server access to your RaidRunner account, so review the scopes requested during sign-in. No tool list or documentation is provided, so verify what each action does before use.

Installation

In SourceWeft

  1. Open RaidRunner in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/net.raidrunner%2Fraidrunner/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "raidrunner": {
      "type": "http",
      "url": "https://raidrunner.net/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.