Docs - Elixir MCP

Elixir MCP records the Clash Royale history the official API doesn't keep, and serves it to your own agent. If you just want that working, the quickstart is five minutes. If you are trying to work out whether you want a personal connection or an agent for your clan, read users, agents and integrations first — it's the distinction everything else rests on. Building a client or an agent? The protocol reference, agent guide and limits are written for you.

Start here

Connect a client: From nothing to a working connection: request access, add your player, then connect Claude.ai, Claude Desktop, Claude Code, or any MCP client to https://elixir.poapkings.com/mcp, with the exact steps for each and an honest note on ChatGPT.
About Elixir MCP: Elixir MCP records the Clash Royale history the official API does not keep - battles, progression, and clan life - and serves it to your own AI agent through a remote MCP server.
Recording and coverage: What is recorded when you track a player or a clan, how one recording is shared by everyone who wants it, what activity and comprehensive scope poll, how often each subject is fetched, how to read freshness and completeness, and what live_fetch can reach.

Using it

Choosing a tool: Which tool answers which shape of question, the three call sequences most answers follow (how am I doing, scout a bracket, name to tag to drill), and the conventions every tool shares on one screen: defaults, windows, verbosity, notes and docs, live reads and the timezone argument.
Protocol reference: The wire contract for the MCP door: transport, OAuth discovery and registration, scopes, per-principal URLs, error codes, the response cap, versioning and the tools/list cache-buster, cursors, and the meta envelope.
Tools: Every tool your agent sees through the Elixir MCP connection, generated from the live registry: groups, arguments, and the OAuth capability each one requires.
Reading a response: Every Elixir MCP response carries a meta envelope: when it was computed, how far back the record goes, how fresh it is, whether capture was incomplete, and the id of the call that produced it.
Limits: Every quota and rate limit in one table, with the exact refusal each produces: the hourly bucket, daily tool calls, live fetches, slots, agents, OAuth registration, sign-in codes, the collector door and the REST API.
Users, agents and integrations: Three kinds of connection to Elixir MCP, what each one is for, and which you want. A user is you. An agent acts for a clan. An integration serves its own users.
Building an agent: A clan agent is a principal you own with its own key, URL, event cursor and feedback inbox. Creating one, what initialize tells it, resolving which human is asking with on_behalf_of and elixir_identify, consuming the event feed with a private cursor, and the key lifecycle.
The timeline: elixir_timeline: what happened to the players and clans you track since your read pointer, as items in order (battle sessions, named moments, roster and war moments, presence) plus one summary entry per subject; who is a subject for a person and for an agent; the window and read-pointer semantics; what the timeline never does.
Verify: proving a player is yours: How Elixir proves that an account controls a Clash Royale player: play one battle with a deck we name, what a verified claim proves and does not, why the battle log and not the profile is the proof, and what is read.
Battle activity: a year of days and a weekly rhythm: The battle-activity graphic on each player you track: a year of UTC days and a 24-by-7 rhythm rebuilt nightly from the record, what a not-recorded day means and why it is never drawn as zero, how the decayed histogram is computed, and what it will drive next.
Tools: Account: The Account tools your agent sees through Elixir MCP: what each one answers, what it takes, and which capability it needs.
Tools: Players: The Players tools your agent sees through Elixir MCP: what each one answers, what it takes, and which capability it needs.
Tools: Battles: The Battles tools your agent sees through Elixir MCP: what each one answers, what it takes, and which capability it needs.
Tools: Cards: The Cards tools your agent sees through Elixir MCP: what each one answers, what it takes, and which capability it needs.
Tools: Clans: The Clans tools your agent sees through Elixir MCP: what each one answers, what it takes, and which capability it needs.
Tools: War: The War tools your agent sees through Elixir MCP: what each one answers, what it takes, and which capability it needs.
Tools: Collections: The Collections tools your agent sees through Elixir MCP: what each one answers, what it takes, and which capability it needs.
Tools: Live: The Live tools your agent sees through Elixir MCP: what each one answers, what it takes, and which capability it needs.
Tools: Timeline: The Timeline tool your agent sees through Elixir MCP: what each one answers, what it takes, and which capability it needs.
Tools: Service: The Service tools your agent sees through Elixir MCP: what each one answers, what it takes, and which capability it needs.
Tools: Help: The Help tools your agent sees through Elixir MCP: what each one answers, what it takes, and which capability it needs.

The record

The battle model: What one recorded battle holds and from whose side, the six mode groups and the API battle types each folds, how duels and boat battles are shaped, which battles count as decided and in which denominators, how a deck's identity is computed with card forms, and how war weeks, points and fame relate.
Time and clocks: The three timestamps a response can carry (computed, observed, played) and which one freshness reads; the 10:00 UTC policy day every clan shares and the war-day, week, section, season and Colosseum vocabulary built on it; and how from/to windows, date-only bounds, days and weeks sugar and the timezone argument resolve on every windowed tool.
Glossary: The words Elixir MCP uses, each in a sentence or two: recorded and tracked, claims and relationships, scope and segment, decided battles and head-to-head, the policy day and war vocabulary, forms and deck identity, principals and budgets, and the response fields that carry caveats.
How the numbers are made: The populations, denominators, shrinkage formula and limits behind the meta tools and Pilot Score. Descriptive evidence, not proof of skill or improvement.
Architecture: How Elixir MCP is built: the collector fleet, the recording pipeline, the Postgres corpus, and the authenticated remote MCP server behind one hostname.
Running a collector: A collector fetches Clash Royale data for Elixir MCP with your own API key and posts it back over HTTPS. No AWS access, no queues, two secrets. What you need, how to enroll, and what it earns you.
Integrations: The REST API for platforms: admin-issued credentials, recorded profiles, asynchronous refreshes, a game clock, and automatic collection enrollment.

Policy

Roles and quotas: Roles never gate what you can read. Every approved account reads all recorded game data; tiers set how much Elixir MCP records for you and how many calls your agent gets per day.
Privacy: What Elixir MCP stores, why, and what it never stores: public Clash Royale game data plus history, your email address and what we use it for, and anonymous analytics with no account attached.
Terms: Elixir MCP is free and unofficial. The terms covering use, the Supercell Fan Content Policy, data, availability, and account removal.

For agents

elixir_docs, elixir_examples, elixir_updates: This documentation, the worked examples and What's new, read over the MCP connection itself: the index, one page, one section, or a word search. Start with Choosing a tool and the glossary.
elixir://docs/<slug> and friends: The same pages as MCP resources (elixir://docs, elixir://docs/<slug>#<section>, elixir://examples, elixir://changelog, elixir://updates, elixir://cards), listed lazily by clients that cache tools/list; the eleven examples are also prompts.
/llms.txt: What this service is and where everything lives, in one short file.
/llms-full.txt: Every documentation page and the whole tool reference in one fetch.
/tools.json: The tool registry as JSON: names, groups, descriptions, arguments, and the capability each one requires.
/api/public/stats: Live corpus totals and the full-history daily series. No authentication.
Updates: Every contract version and what shipped in it — the same list elixir_changelog returns.