Sleipnir Multistream

tv.sleipnirPublished by sleipnir.tvOfficial publisherv1.0.1Updated Oct 24, 2026

Multistream relay control: check live status, switch destinations, manage teams, generate overlays.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Remote MCP server for Sleipnir Multistream that lets an assistant check live stream status, switch relay destinations, manage teams and generate overlays.

What you can do
  • Check live status of multistream relays and destinations.
  • Switch or change where a stream is relayed.
  • Manage teams and their members.
  • Generate overlays for streams.
When to use it
Useful when you run multistreaming through Sleipnir and want an assistant to inspect live status, adjust relay destinations, handle team settings or produce overlays without opening the web app.
Requirements
A remote MCP endpoint at sleipnir.tv over streamable HTTP. Authentication is required: either a Sleipnir personal access token sent as an Authorization bearer header, or OAuth 2.1 via the server's discovery endpoint. A Sleipnir account is needed.
Before you install
The server requires a Sleipnir personal access token or OAuth authorization, which grants access to your streaming account. Switching destinations and managing teams change live configuration, so confirm actions before they run. No tool list is published, so review the available tools after connecting.

Installation

In SourceWeft

  1. Open Sleipnir Multistream 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/tv.sleipnir%2Fsleipnir/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": {
    "sleipnir-multistream": {
      "type": "http",
      "url": "https://sleipnir.tv/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

2
  1. v1.0.1LatestOct 22, 2026
  2. v1.0.0Sep 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.