prepare_tournament — Turniermeister — Tournament Engine MCP Tool
prepare_tournament
(prepare tournament) is one of 1 tool on the
Turniermeister — Tournament Engine
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call prepare_tournament from your client
- Claude Code Turniermeister — Tournament Engine prepare_tournament run in your project directory
- Claude Desktop Turniermeister — Tournament Engine prepare_tournament ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Turniermeister — Tournament Engine prepare_tournament ~/.cursor/mcp.json
- VS Code Turniermeister — Tournament Engine prepare_tournament .vscode/mcp.json
- Zed Turniermeister — Tournament Engine prepare_tournament ~/.config/zed/settings.json
- Windsurf Turniermeister — Tournament Engine prepare_tournament ~/.codeium/windsurf/mcp_config.json
- Cline Turniermeister — Tournament Engine prepare_tournament ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Turniermeister — Tournament Engine prepare_tournament ~/.gemini/settings.json
- Grok Turniermeister — Tournament Engine prepare_tournament .mcp.json (in your project root)
- ChatGPT Turniermeister — Tournament Engine prepare_tournament Settings → Connectors → Advanced → Developer mode
- Claude.ai Turniermeister — Tournament Engine prepare_tournament Settings → Connectors → Add custom connector
- LangChain Turniermeister — Tournament Engine prepare_tournament pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http turniermeister https://app.turniermeister.at/mcp
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.