DashboardAnalyticsAI AgentsSecurityGet StartedChangelogDeutsch

Get started · four gates, one ground

Pick one gate. Ignore the rest.

You don't need all of this — you need one section that matches how you work. Every path requires Node.js 20 or newer, and none of them ever puts your password in a chat.

First: Node.js

Open nodejs.org, click the big LTS button, run the installer, leave the defaults. Then open a terminal (Terminal on macOS, Command Prompt on Windows) and check:

bash
$ node -v
v22.19.0   # v20 or newer is fine

If the command is not found, Node isn't installed yet — or the terminal was open before the installer ran and needs a restart.

How do you work?

Four gates
Block A

I chat with Claude as a desktop app

Download kicktipp.mcpb from the latest release and double-click it. Fill in your Kicktipp email and password in Desktop's form (leave community blank and pick the pool later; tick read-only if the agent should only look).

Then fully quit Claude Desktop — on a Mac, closing the window is not enough; use Claude → Quit — reopen, start a new chat, and ask "What's my Kicktipp status?"

Block B

I use a terminal agent (Claude Code, Codex, …)

Attach the MCP server once:

$claude mcp add kicktipp -- npx -y -p kicktipp-agent kicktipp-agent-mcp

In a new chat, say "Set up my Kicktipp account". You'll get a http://127.0.0.1 link — open it, sign in, pick your pool. Codex, Cursor and other clients: the configs are here.

Block C

I want the kicktipp command myself

$npm install -g kicktipp-agent
$kicktipp login --web

The login prints a localhost link (on Windows, paste it into a browser yourself). Sign in, pick your pool, done. Then kicktipp today shows today's matches and kicktipp tui opens the dashboard.

Block D

I want the source in a folder

git clone https://github.com/christianheidorn/kicktipp-agent.git cd kicktipp-agent npm install && npm run build npm link

npm link makes the kicktipp command use this folder's build. For MCP clients, point them at node …/dist/server.js instead of npx.

Five commands worth knowing

After setup
bash
$ kicktipp today       # today's matches, and which still need a bet
$ kicktipp tui         # the full-screen dashboard (--demo works without login)
$ kicktipp bet         # the prediction grid for this matchday
$ kicktipp sync        # cache the season, unlocks the analytics
$ kicktipp deadline    # countdown to kickoff; --check exits 2 when urgent

Optionally, kicktipp set-player tells the leaderboard which row is you.

German interface, German host

The CLI defaults to English and kicktipp.com. If your Tipprunde lives on kicktipp.de and you'd rather read German:

bash
$ kicktipp set-lang de   # German UI, permanently
$ kicktipp set-site de   # start on kicktipp.de, permanently

Both sites work either way — missing pages are retried on the other host and language automatically, so mixed communities just work.

Never miss a kickoff

kicktipp remind turns the deadline check into automation: a ready-made cron line or systemd user units (--install writes them), an .ics calendar with an alarm per kickoff, and kicktipp set-notify wires alerts to Notification Center, a webhook like ntfy.sh, or any command of yours.

More than one pool? More than one account?

kicktipp -c other-pool schedule targets a different community for one command. Profiles (kicktipp -p work stats) keep separate accounts with their own sessions. And if you run the community: the admin commands place bets for members without a login of their own — with a type-their-name-back confirmation before anything is submitted.

Two minutes to kick-off.

Or zero — paste the setup prompt into your agent and watch.