Turniermeister — Tournament Engine

io.github.MartyMcFlyJrPublished by GitHub account MartyMcFlyJrv1.0.0Updated Oct 28, 2026

Turnier engine: AI prepares a real tournament (bracket, schedule) and returns a claim link.

VerifiedStreamable HTTPWeb executableLocation & LifestyleProductivity & Workflow

Overview

AI-generated overview

Remote MCP server that lets an assistant prepare a real Turniermeister tournament and return a claim link the user opens to take it over.

What you can do
  • Prepare a tournament: the assistant sets up name, format, team count and optional participant names, and gets back a claim link.
  • Hand back the claim link so the user can sign up and take over the prepared tournament with schedules and live results.
  • Retry safely with an idempotency key, and read structured validation errors to correct the preparation.
When to use it
Use it when a user wants to plan or create a real tournament — a club night, game night, or knockout or group-plus-knockout bracket — from a chat conversation instead of filling in forms by hand.
Requirements
A remote Streamable HTTP endpoint; no authentication, API keys or environment variables are declared. The user needs a browser to open the claim link and an account to take the tournament over. Only bracket competitions (knockout, group plus knockout) are supported.
Before you install
The server creates real tournament preparations on a third-party service; claim links expire after 14 days. Tournament name and structure are stored unencrypted during that window, while participant names are encrypted and deleted with unclaimed preparations. Free demo mode is limited and public pages carry a watermark; premium is paid.

Installation

In SourceWeft

  1. Open Turniermeister — Tournament Engine in the dashboard and add it to a workspace.
  2. 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/io.github.MartyMcFlyJr%2Fturniermeister/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.

{
  "mcpServers": {
    "turniermeister-tournament-engine": {
      "type": "http",
      "url": "https://app.turniermeister.at/mcp"
    }
  }
}

README

Turniermeister — Tournament Engine (MCP)

MCP server for Turniermeister, a tournament engine for real club and amateur tournaments: fair mathematical seeding, schedules, live results via QR code, helper access and award ceremonies.

Endpoint

https://app.turniermeister.at/mcp
  • Transport: Streamable HTTP, stateless (JSON responses)
  • Authentication: none (public discovery channel, rate-limited)

Tool: prepare_tournament

Prepares a real tournament from a single AI conversation and returns a claim link:

  1. The assistant prepares the tournament (name, format, team count, optional encrypted participant names).
  2. The user opens the claim link in a browser, signs up or creates an account.
  3. The tournament is taken over with one click — no retyping, schedules and live results included.

Claim links are valid for 14 days. Always send a unique idempotencyKey (UUID) per preparation — retries return the newest link instead of creating duplicates. Validation problems are returned as structured error JSON the agent can fix on its own.

MVP scope: competitionType: "bracket" (knockout / group + knockout). More competition types are on the roadmap.

Connect

  • Claude: Settings → Connectors → Custom Connector → paste the URL, or use the one-click connect on our MCP page
  • ChatGPT: Settings → Connectors → Advanced → enable Developer Mode → add URL
  • Cursor: add the URL to mcp.json (type: "http")

Full guide: DE · EN · End-user walkthrough

Pricing & limits

Free forever in demo mode (one tournament per format, public pages with watermark). Premium lifts all limits (€19/month, €149/year, or €29 once for 30 days).

Privacy

Tournament name and structure data are stored unencrypted for the 14-day claim window. Team and player names are stored AES-256-GCM encrypted, only migrate into an account at claim time and are deleted automatically with unclaimed preparations after 14 days. Analytics events contain no tokens and no plain-text names. Server and data hosting: Germany (GDPR). See the privacy policy.

Source: README.md at commit b50a8bf

Tools

1

prepare_tournament

Prepare a Turniermeister tournament

Prepares a real tournament in Turniermeister and returns a claim link for the user. Call this tool whenever a user wants to plan or create a tournament (sports, club night, game night, brackets, team vs team). Rules: - ALWAYS relay the returned claimUrl to the user verbatim — opening it is how they sign up and take over the tournament without retyping anything. - competitionType must be "bracket" (knockout/group formats). Ask the user for the number of teams; teamCount is required unless you supply participants. - Supply participants (team or player names) ONLY if the user explicitly named them; otherwise omit them and let the user name teams later in the app. Never invent participant names. - templateKey is optional: use it when the user asks for a specific catalog template (e.g. preset-padel, preset-fussball, preset-eisstock, preset-schnapsen). For Eisstock use mode 2; its 128-team limit is available only with templateKey preset-eisstock. Do not guess unknown keys — omit it instead. - schedule is optional: pass fields, startTime (HH:MM), playingMinutes and pauseMinutes ONLY when the user named them. Never invent them. The tool does not know the user's dates or field layout beyond these values. - ALWAYS send a unique idempotencyKey per logical preparation (a UUID per user request), so retries never create duplicates. Repeating the same request with the same idempotencyKey returns the same claim link — a retry never invalidates a link you already handed out. - Business validation problems come back as structured JSON errors (ok=false, code, message, fixHint): fix your input from that JSON and retry. Schema violations (wrong type or value out of range) are rejected as a validation error naming the field (e.g. teamCount above the maximum): correct that argument and retry. Do not ask the user to retry. - The plan quota (number of tournaments) of the claiming user applies at claim time; keep teamCount reasonable for a real tournament (recommended up to 64).

ParametersmoderequirednamerequiredscheduleteamCountclientInfotemplateKeyparticipantsidempotencyKeyrequiredcompetitionType

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

90% 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.