MCP server · 28 tools · any client
Works with your agent.
Claude Desktop, Claude Code, Codex, Cursor, Copilot, Windsurf — if it speaks MCP, it can run your Kicktipp. The server runs on your machine, and no agent ever sees your password. Try the session: the first prompt turns the lights on.
Local server, localhost login
How it worksYour agent does not log into Kicktipp. It starts a small program on your computer — the MCP server — and that program talks to kicktipp.com or kicktipp.de. The agent sees pool data: matches, tables, deadlines. It never sees credentials.
Signing in happens once, in a normal browser. Tell the agent to set up your Kicktipp account; it calls connect_account and hands you a http://127.0.0.1:…/setup?token=… link. Open it, sign in, pick your community. The password goes into that local page — never into the chat — and lands in ~/.config/kicktipp-agent/config.ini with mode 600. The full trust story is on the security page.
Shortcut: copy this prompt into any capable agent and let it do the whole installation for you.
Pick your client
Same server, same toolsOnly the wiring differs. Every path uses npx, so there is nothing to clone or build.
Claude Desktop
Download kicktipp.mcpb from the latest release and double-click it. Desktop shows a settings form; fill in email and password (they go to the OS keychain), quit Desktop fully, start a new chat.
The least terminal-heavy path — no commands at all.
Claude Code
One command attaches the server; a new chat picks it up.
$claude mcp add kicktipp -- npx -y -p kicktipp-agent kicktipp-agent-mcpThen say "Set up my Kicktipp account" and open the localhost link.
Codex CLI
Add this to ~/.codex/config.toml and restart Codex:
[mcp_servers.kicktipp]
command = "npx"
args = ["-y", "-p", "kicktipp-agent", "kicktipp-agent-mcp"]Cursor, Copilot, Windsurf & the rest
Any client with an MCP config (.cursor/mcp.json, .vscode/mcp.json, or equivalent) takes the standard block under mcpServers:
"kicktipp": {
"command": "npx",
"args": ["-y", "-p", "kicktipp-agent", "kicktipp-agent-mcp"]
}No env block needed — the server reads its own config.
Trying it for the first time? Turn on read-only mode. Tick read-only on the setup page (or set read_only = true). Betting tools are then never even registered — the agent provably cannot submit anything. Recommended for the first session.
The squad: 28 tools
Structured resultsEvery tool returns structured data an agent can reason over, and cached season data is also exposed as MCP resources. Dry-run flags let an agent validate a slip without submitting it.
get_statusCheck credentials and configurationconnect_accountOpen the localhost setup pageget_today_matchesToday's matches with bet statusget_betsMatches and current bets for a matchdayget_scheduleMatch schedule with resultsget_leaderboardPlayer rankings for a matchdayget_overviewSeason overview across all matchdaysget_tableLeague table (football standings)get_rulesGame rules and scoring systemget_communitiesList communities the user belongs toget_playersList players in the communityget_bonus_questionsBonus questions with answer optionsget_deadlineCountdown and matches that still need a betsync_historyFill the local cache for analytics toolsget_statsSeason analytics for a playerget_rival_analysisGap, swing, and overtake conditionssuggest_betsOdds-based slip, read-only, never submitsget_standings_scenariosProject the table under hypothetical resultswhatifReplay the season under a different strategyget_bet_logWhat this agent submitted, from the recordplace_betsPlace match bets by fixture nameplace_bonus_betsPlace bonus question answersset_communitySet the active communityset_playerSet which player you areset_notifyConfigure the notification backendlist_membersSpielleiter: list community membersget_bets_for_memberSpielleiter: bets for a memberplace_bets_for_memberSpielleiter: place bets for a memberIn read-only mode, the playing tools don't appear in the roster at all — and the submitting functions refuse independently, in case a client caches the list. Everything an agent does submit is written to the local bet log, with undo.
Your agent is ready to tip.
One config block. One localhost login. Zero passwords in chat.