Game Development

turniermeister.de

Prepares a real tournament in Turniermeister and generates a claim link for the user.

1 endpoint1 known toolsFirst detected September 7, 2026Last detected September 7, 2026

ENDPOINT 1

https://app.turniermeister.at/mcp

No auth detected

MCP server metadata

Name: turniermeister
Version: 1.0.0

Capabilities

tools.listChanged

Server instructions

Turniermeister is a tournament engine for real club and amateur tournaments (brackets, schedules, scoring). Use the prepare_tournament tool when a user wants to create or plan a tournament: it pre-configures the tournament and returns a claim link the user opens in a browser to sign up and take over the tournament without retyping anything.

Known tools 1

prepare_tournament

Prepares a real tournament in Turniermeister and returns a claim link for the user.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.turniermeister]
url = "https://app.turniermeister.at/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: turniermeister
Remote MCP URL: https://app.turniermeister.at/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "turniermeister": {
      "url": "https://app.turniermeister.at/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "turniermeister": {
      "type": "http",
      "url": "https://app.turniermeister.at/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "turniermeister",
  "transport": "streamable-http",
  "url": "https://app.turniermeister.at/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.