mcpbeat Sign in

Turniermeister — Tournament Engine MCP Server

by martymcflyjr Your server? Claim it
answering

Turniermeister — Tournament Engine is answering right now. Last checked 9 min ago. It exposes 1 tools. Last commit 6 Sep 2026.

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

Uptime history 58 days of history · worst day 91%
58 days agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
145 ms
Response time
average over 24h
0
Stars
last commit 6 Sep 2026

What changed 8

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 10 September 2026. No other catalogue keeps this.

12 Oct a tool description was rewritten prepare_tournament
12 Oct a tool changed the parameters it asks for prepare_tournament
11 Oct a tool description was rewritten prepare_tournament
4 Oct a tool description was rewritten prepare_tournament
4 Oct a tool changed the parameters it asks for prepare_tournament
10 Sep a tool changed the parameters it asks for2 times that day prepare_tournament
10 Sep a tool description was rewritten prepare_tournament
and 1 more, back to 10 September 2026

Nothing serious here today

Today is the operative word: we check Turniermeister — Tournament Engine every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add turniermeister --transport http https://app.turniermeister.at/mcp
Settings → Connectors → Add custom connector, then paste this address
https://app.turniermeister.at/mcp
~/.codex/config.toml
[mcp_servers.turniermeister]
url = "https://app.turniermeister.at/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "turniermeister": {
      "url": "https://app.turniermeister.at/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "turniermeister": {
      "type": "http",
      "url": "https://app.turniermeister.at/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

prepare
prepare_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).

Endpoints

URLTransportStateLatencyChecked
https://app.turniermeister.at/mcp streamable-http answering 112 ms 9 min ago

Alternatives to Turniermeister — Tournament Engine

same job, measured the same way
Zovo Tournament Maker
by theluckystrike

Make a tournament bracket in the chat, record results by clicking the winners, and print it.

2 tools answering
Lease Schedule
by theluckystrike

Lease schedules with a residual: the payment, the interest split and the journal per month.

9 tools local only
Reclaim.ai MCP by usefulapi
by usefulapi

Read tasks, habits, events and scheduling links; create and update Reclaim tasks and habits.

15 tools answering
ScreenParty
by huitongdesk-screenparty

Create watch-together rooms, scheduled watch parties and branded class links. No sign-up.

7 tools answering
P
Print Shop by Bottle Your Brand
by bottleyourbrand

Turn your AI images into die-cut vinyl stickers. Print specs, sizing, and a ready-to-order link.

4 tools answering
Make Bracket Online MCP
by rocnubie

Create, run, and share brackets for decisions, tournaments, and group votes with no sign-up

local only
QRX
by qrx

Turn a prompt and a link into a branded, print-ready QR code that always scans.

154 installs/wk 7 tools answering
W
Whenly — group scheduling for AI agents
by workers-notdown-app-whenly

Agent creates a group-scheduling poll, gets a shareable link, and reads the best meeting time.

2 tools answering

Turniermeister — Tournament Engine — questions

Answers built from our own checks of this server.

What can Turniermeister — Tournament Engine do?
It exposes 1 tools, read directly from the server on our last check. Among them: prepare_tournament. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Turniermeister — Tournament Engine working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 145 ms. The bar chart above shows every period we have measured.
How do I connect Turniermeister — Tournament Engine?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Turniermeister — Tournament Engine need an API key?
No. Turniermeister — Tournament Engine completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Turniermeister — Tournament Engine?
It answers our handshake in 145 ms on average, which is faster than 82% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Turniermeister — Tournament Engine open source?
We cannot say either way: 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.