01
Records continuously
Every battle stored once, no matter how many clanmates observed it — plus daily snapshots, war weeks, and roster history, kept indefinitely.
← Back home
Meet Elixir →
What Elixir MCP does
A memory the game never had
02
Serves your agent
Connect Claude or any MCP client to one URL and ask questions the game can't answer: win-rate trends, trophy graphs, deck history with receipts.
03
Runs on collectors
Operator-run machines with card-name identities do the fetching — a Mac in a closet, a NAS at a cabin. Running one earns your agent extra daily calls.
04
Powers clan routines
A daily Clan Pulse digest and war-day events feed scheduled agents: who's quiet, who has decks left today, who joined and left — facts, never judgments.
05
Stays honest
Every number ships its sample size, coverage tools disclose exactly how complete the record is, and capture gaps are measured and published.
06
Built in the open
The recorder, the MCP server, the web app, and the collector are all public code — and the data dashboard is public too.
Access is request-approved while the recorder grows — request it on the site →
Under the hood
Built like real software
Elixir MCP is a serverless recorder with one deliberate exception: the cloud has no route to the Clash Royale API at all. Only the collector fleet holds IP-bound keys, leasing work from a queue the service prioritizes by expected yield — and the whole fleet shares one global rate budget, so more collectors mean resilience, never more API load.
Cloud
AWS Lambda · SQS · RDS
Agent door
Remote MCP · OAuth 2.1
Collectors
Go · self-updating
Data store
PostgreSQL + S3 archive
Tool surface
35 contract-versioned tools
Quality gates
CI-gated public monorepo
Meet the agent it feeds
Elixir, our clan agent, reads recorded game facts from Elixir MCP — standings, war intelligence, and player history with receipts.