# Elixir MCP

> Elixir MCP records Clash Royale history the official game API does not keep - battles, progression, clan rosters, and war - and serves it to your own AI agent through an authenticated remote MCP server at https://elixir.poapkings.com/mcp. The official API answers only "what is true right now": a rotating ~30-battle log, no trophy timeline, no season history. This service keeps the record.

Access is approval-gated while the recorder grows; request it at https://elixir.poapkings.com/. All recorded GAME data is readable by every approved account, the same posture as the game's public API. ACCOUNT data is private to its owner. Roles never gate what you can read: they set how much the service records for you and how many calls per day your agent gets.

Corpus as of 2026-09-18: 258,519 battles recorded across 305,216 players and 6,784 clans, captured by 6 collectors, oldest battle 2026-01-03. These figures are baked at build time; https://elixir.poapkings.com/api/public/stats is live.

## Documentation
- [All documentation](https://elixir.poapkings.com/docs): index of every page below
- [Connect a client](https://elixir.poapkings.com/docs/quickstart): 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](https://elixir.poapkings.com/docs/about): 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](https://elixir.poapkings.com/docs/recording): 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.
- [Choosing a tool](https://elixir.poapkings.com/docs/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](https://elixir.poapkings.com/docs/protocol): 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](https://elixir.poapkings.com/docs/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](https://elixir.poapkings.com/docs/responses): 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](https://elixir.poapkings.com/docs/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](https://elixir.poapkings.com/docs/connections): 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](https://elixir.poapkings.com/docs/agents): 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](https://elixir.poapkings.com/docs/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](https://elixir.poapkings.com/docs/verify): 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.
- [The battle model](https://elixir.poapkings.com/docs/battles): 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.
- [Battle activity: a year of days and a weekly rhythm](https://elixir.poapkings.com/docs/activity): 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.
- [Time and clocks](https://elixir.poapkings.com/docs/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](https://elixir.poapkings.com/docs/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](https://elixir.poapkings.com/docs/methodology): The populations, denominators, shrinkage formula and limits behind the meta tools and Pilot Score. Descriptive evidence, not proof of skill or improvement.
- [Architecture](https://elixir.poapkings.com/docs/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](https://elixir.poapkings.com/docs/operators): 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](https://elixir.poapkings.com/docs/integrations): The REST API for platforms: admin-issued credentials, recorded profiles, asynchronous refreshes, a game clock, and automatic collection enrollment.
- [Roles and quotas](https://elixir.poapkings.com/docs/roles): 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](https://elixir.poapkings.com/docs/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](https://elixir.poapkings.com/docs/terms): Elixir MCP is free and unofficial. The terms covering use, the Supercell Fan Content Policy, data, availability, and account removal.
- [Tools: Account](https://elixir.poapkings.com/docs/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](https://elixir.poapkings.com/docs/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](https://elixir.poapkings.com/docs/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](https://elixir.poapkings.com/docs/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](https://elixir.poapkings.com/docs/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](https://elixir.poapkings.com/docs/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](https://elixir.poapkings.com/docs/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](https://elixir.poapkings.com/docs/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](https://elixir.poapkings.com/docs/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](https://elixir.poapkings.com/docs/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](https://elixir.poapkings.com/docs/tools/help): The Help tools your agent sees through Elixir MCP: what each one answers, what it takes, and which capability it needs.
- [The corpus](https://elixir.poapkings.com/data): the totals - battles, players, clans, war weeks and snapshots recorded so far
- [Growth over time](https://elixir.poapkings.com/data/growth): battles recorded per day, bucketed by when they were played
- [What we collect](https://elixir.poapkings.com/data/collect): each subject, how often it is collected, since when and how long it is kept
- [Recording now](https://elixir.poapkings.com/data/now): the live strip - last battle seen, battles this hour, collectors running
- [For machines](https://elixir.poapkings.com/data/machines): the public JSON and text surfaces, no key needed
- [What's new](https://elixir.poapkings.com/updates): every user-visible change, newest first, each on its own page
- [Example: Understand your own play](https://elixir.poapkings.com/examples/play): Not “you won 61%” — which deck, which mode, which week, and whether the grind is actually paying off.
- [Example: Pick your next deck](https://elixir.poapkings.com/examples/deck): What is winning in the recorded corpus, weighted by results rather than by how often you see it on a stream — with the sample sizes attached.
- [Example: Push with evidence](https://elixir.poapkings.com/examples/ladder): Trophy pushes stall for boring, findable reasons. A record of every battle makes the pattern visible instead of anecdotal.
- [Example: Follow your friends](https://elixir.poapkings.com/examples/friends): The people you play with, tracked because you asked — what they are on, how much they are playing, and what changed since you last looked.
- [Example: Win your river race](https://elixir.poapkings.com/examples/clan): The finished race, the one that just opened, and who has battled so far today — from a record the game's own API forgets after twenty weeks.
- [Example: Keep the roster healthy](https://elixir.poapkings.com/examples/roster): Who has gone quiet, who just arrived, and who the game itself has stopped counting — so a check-in happens before a race is lost.
- [Example: Scout the other clan](https://elixir.poapkings.com/examples/scout): Every race captures all five clans in the bracket, and a curated collection keeps the clans you care about recorded — so the comparison is always there to ask for.
- [Example: Write the weekly recap](https://elixir.poapkings.com/examples/recap): The numbers are already recorded; the writing is the only work. Your agent drafts it and you paste it into clan chat.
- [Example: Answer your clanmates](https://elixir.poapkings.com/examples/discord): An agent acts for one clan rather than for you: its own door, its own key, its own feed — and a map from a Discord id to a player tag.
- [Example: Publish your own stats](https://elixir.poapkings.com/examples/publish): Build a clan site or a bot on the record instead of on a second Clash key. Pull at build time; no scraping, no push.
- [Example: Run a collector](https://elixir.poapkings.com/examples/collector): Volunteer a machine that fetches for the corpus. It is named for a card, credited to you, and it raises what Elixir records for you.
- [The family](https://elixir.poapkings.com/family): the POAP KINGS products that read from this hub, and the Clash Royale things we like but are unconnected to
- [Family: Elixir Drop](https://elixir.poapkings.com/family/drop): A daily game that sharpens the instincts Clash actually rewards — elixir counting, trade maths, cycle timing. Built for the minutes between matches.
- [Family: Elixir Agent](https://elixir.poapkings.com/family/agent): The clan agent for POAP KINGS. It answers members about their own record — fame, attacks, decks, trophies — in the clan's own Discord.
- [Family: Discord bot](https://elixir.poapkings.com/family/discord): Stand up an agent for your own clan in minutes. Invite the bot, paste your clan tag, approve it in the console — it maps each Discord member to their player tag the first time they ask.
- [Family: CR Agent-first API docs](https://elixir.poapkings.com/family/crdocs): The Clash Royale API, documented for agents rather than for humans reading a portal — every endpoint, field and quirk in a shape a model can actually consume.
- [Family: Elixir MCP](https://elixir.poapkings.com/family/mcp): The hub. It records Clash Royale history and serves it to agents over MCP — and everything above reads from it rather than from each other.
- [Family: Royaledle](https://elixir.poapkings.com/family/royaledle): A daily Clash guessing game — one card, six tries, everybody gets the same puzzle. The good kind of five-minute habit, and the reason half the clan chat is spoiler-tagged every morning.
- [Family: RoyaleAPI](https://elixir.poapkings.com/family/royaleapi): The reference Clash Royale stats site, and the one everybody means when they say “go look it up”. Deck stats, player profiles, tournament coverage — the standard we measure our own numbers against.
- [Support Elixir](https://elixir.poapkings.com/support): free to use and independently run; what it costs, GitHub Sponsors, and why sponsoring changes nothing about an account
## Machine-readable
- [Full content bundle](https://elixir.poapkings.com/llms-full.txt): every documentation page and the whole tool reference in one fetch
- [Tool registry JSON](https://elixir.poapkings.com/tools.json): all 55 tools with groups, descriptions, arguments, and required OAuth capabilities
- [Public corpus stats JSON](https://elixir.poapkings.com/api/public/stats): live totals plus the full-history daily series; no authentication
- [Public service status JSON](https://elixir.poapkings.com/api/public/status): recording health; no authentication
- [Updates feed](https://elixir.poapkings.com/feed.xml): RSS 2.0 of what's new
- [Sitemap](https://elixir.poapkings.com/sitemap.xml)

## MCP connection
- Endpoint: https://elixir.poapkings.com/mcp (OAuth 2.1; tokens are audience-bound to this resource)
- Tools: 55 across 12 groups - Account (6), Players (9), Battles (10), Cards (2), Clans (6), War (4), Rankings (5), Collections (3), Live (1), Timeline (1), Service (2), Help (6)
- Capabilities: `cr:read` read recorded game data; `recordings:write` change what you track; `collections:write` edit collections; `account:write` update account preferences; `feedback:write` send feedback; `account:email` know your email address
- Read tools need only `cr:read`. The 6 state-changing tools each name their own capability, granted only if the client asks for it at connection time.

### Account
- `elixir_my_players` (My players): The players you track and WHO EACH ONE IS TO YOU: relationship (primary | alt | friend | watching), your private nickname if any, notify setting, recording status and current clan. That is what resolves "my alt" or "how are my friends doin…
- `elixir_nickname` (Nicknames): Give a player YOUR nickname, private to your account and visible only to you and your agents ('to me Raquaza is Tyler'). Nicknames ride along wherever names appear (search matches them, summaries and rosters show them). Pass nickname: null…
- `elixir_my_identities` (People you know): The humans you have learned, and which player each one is. Yours alone; one connection's mappings are invisible to every other. Useful for 'who am I to you?' and for spotting a mapping you got wrong.
- `elixir_track_clan` (Track a clan): Track a clan on your account: starts recording in one act (tracked means recorded), within your tier's clan slots. scope activity records roster and war; comprehensive additionally records every member's battles and profile, following memb…
- `elixir_track_player` (Track a player): Track a player on your account: claims the tag AND starts recording in one act (tracked means recorded), within your tier's player slots. Say who they are to you with relationship (primary = you, alt = also you, friend, watching); your fir…
- `elixir_identify` (Who is asking): Remember which player a human is, so you never have to ask twice. An agent serves many people through one connection and MCP carries no per-request identity, so YOU supply one: discord:1234, signal:..., telegram:..., whatever your surface …

### Players
- `badges_holders` (Badge holders): Who holds a badge: every recorded player in scope (the corpus by default, or a segment) with the named badge, with level and progress where tiered, names not just tags, and their current clan. Names must match the API's badge identifier ex…
- `badges_rarity` (Badge rarity census): Every badge observed across recorded profiles with its holder count, rarest first: the 'what is the rarest badge' question over the whole recorded population (default) or a segment (clan, collection, one player), with players_considered so…
- `players_collection` (Card collection): Full card collection as last recorded: levels (in-game 1-16 scale), counts, forms, star levels, collection level. evolutionLevel / maxEvolutionLevel are FORM bit fields (1 = Evolution, 2 = Hero, 3 = both), decoded into forms_unlocked / for…
- `players_search` (Find player by name): Name-to-tag resolution across the whole recorded corpus: case-insensitive substring on last-observed display names AND your private nicknames, nicknames ranked first ("tyler" finds the player you call Tyler). Unknown names return an honest…
- `players_profile` (Player profile): Latest recorded profile snapshot for a tag: trophies, Path of Legends, league stats, donations, lifetime counters, collection level, clan (with badge and the player's role), attributes (arena, best trophies, favourite card, account age) an…
- `players_summary` (Player summary): The headline in one call: current trophies and clan, last-30-days record and win rate, and the most-played deck with its record. Start here for “how am I doing?”; drill in with battles_performance / battles_decks.
- `players_timeline` (Player timeline): Time series from daily snapshots, one point per game day: trophies by default, or any of the day row's metrics (donations and donations_received, the weekly counters; the lifetime block: battle_count, wins, losses, three_crown_wins, star_p…
- `elixir_coverage` (Record coverage): How complete the record is for a tag: recording start, last successful poll per endpoint, battles captured (including appearances recorded before the tag was tracked), capture estimates over observation intervals ending in the last seven d…
- `players_names` (Resolve tags to names): Bulk tag-to-name resolution from the corpus: up to 100 tags in, for each the last-observed name and where it came from, plus an explicit unknown list. Costs nothing from the live lane; resolving a miss is then a deliberate players_profile(…

### Battles
- `battles_cards` (Card performance): Per-card win/loss attribution over recorded battles. perspective "mine": which of your cards carry. perspective "opponent": which enemy cards beat you (the nemesis question). Duels are excluded (no single deck).
- `battles_compare` (Compare players): Side-by-side of 2-4 recorded tags (any recorded player): latest snapshot topline plus a shared performance window.
- `battles_decks` (Deck performance): Battles grouped by exact deck identity (deck_hash): per-deck record, first/last used, win rate, share of battles. Deck identity is the exact card set played (some event modes field more or fewer than 8). Unbounded by default and says so in…
- `battles_levels` (Level Curve & Pilot Score): The Level Curve and Pilot Score: win rate by deck-average level gap across the recorded corpus, binned where the data lives, never extrapolated. Pass player_tag (or on_behalf_of) for a Pilot Score: actual minus the level-expected win rate,…
- `battles_meta_cards` (Meta cards (observed)): Observed card meta for a segment: the whole corpus (default), or segment.clan_tag / segment.player_tag / segment.collection. Per card AND form (forms never merge): usage share among decided player-battle observations, distinct players, raw…
- `battles_meta_decks` (Meta decks (observed)): Observed deck meta for a segment: the whole corpus (default), or segment.clan_tag / segment.player_tag / segment.collection. Per exact deck identity: decided player-battle observations (not unique matches), record, distinct players, usage …
- `battles_opponents` (Opponents faced): A player's recorded battles grouped by OPPONENT: per opponent the record (W/L/D), first and last meeting, the modes, clan at last meeting, and the opponent's name where the service has observed one (name_known). min_battles: 2 answers "who…
- `battles_performance` (Performance windows): Computed record over a window: W/L/D, win rate, crowns for/against, net trophies, three-crown rate, streaks. compare_from/compare_to or before_after runs a second window server-side for "since X vs before" questions (before_after wins over…
- `battles_query` (Query battles): The workhorse: recorded battles with filters and cursor pagination, both perspectives of every battle. Three addressing modes: player_tag (the usual sweep, defaults to the caller); battle_id alone (ONE battle, both sides); deck_hash alone …
- `battles_trends` (Segment trends): Weekly time series for a segment: the whole corpus (default), or segment.clan_tag / segment.player_tag / segment.collection. Per ISO week: battles, record, aggregate win rate, distinct active players, net trophies, the season the week star…

### Cards
- `cards_catalog` (Card catalog): Current card and tower-troop catalog: ids, names, rarities, elixir cost, icons, max levels and forms. Use it to resolve card ids instead of guessing; ids or query narrow it to the cards you mean, and verbosity compact keeps id, name, rarit…
- `cards_synergy` (Card synergy): What a card is played WITH, for a segment (the corpus by default) and window (default: the current season to date; season selects another): partner cards ranked by co-occurrence in decided head-to-head decks that contain the anchor, with c…

### Clans
- `clans_members_timeline` (Clan members' timeline): The members' daily series for a clan, yours by default: for every player the roster placed in the clan in the window (or player_tags), one point per game day with the roster's metrics (trophies, donations, donations_received, arena_id, cla…
- `clans_participation` (Clan participation by week): Every open member's participation, week by week, in ONE call: per ISO week the battles played, ranked battles and the donation counter at week end; per recorded war week the decks used and each war day's decks (null where the day was not p…
- `clans_pilot_scores` (Clan Pilot Scores): Every open member's Pilot Score in ONE call: each member with >= 30 decided leveled battles scored against the corpus Level Curve over the window (default 90 days), with tenure. Descriptive in-sample residuals, not a skill ranking or proof…
- `clans_roster` (Clan roster): A clan's roster, yours by default: roles, latest trophies and donations per member, activity recency (last recorded battle and the game's own last-seen), the member's tenure and badge count, the lifetime block as of the latest profile poll…
- `clans_standings` (Clan standings): Clan-relative performance, yours by default: every open member's recorded W/L/D, win rate, ladder trophy net and current streak in ONE call over a window (default 30 days). For a 24-hour member scan use days: 1, min_battles: 1; from/to als…
- `clans_timeline` (Clan timeline): A clan's daily series, yours by default, one point per game day from the roster: clan_score, clan_war_trophies, members, donations_per_week, required_trophies, and the aggregates over that day's member rows (total_member_trophies, avg_memb…

### War
- `war_current` (Current war): The current (latest recorded) river race for a clan, yours by default: standings across the five clans with banked fame and current-day period_points, per-member points and decks used, the war day and attendance so far. On a war day decks_…
- `game_clock` (Game clock): What time it is in Clash Royale, for nobody in particular: current season, week within the season, whether today is a training day or war day, when this day ends, and the next boundaries of each kind (war_day_closes_at, next_war_day_opens_…
- `war_rivals` (Scouting Report): The Scouting Report: observed war history for rival clans. Every recorded river race captures all five bracket clans, so rivals accumulate fingerprints across every race they shared with a recorded clan. Defaults to your clan's current bra…
- `war_history` (War history): Recorded war weeks for a clan, yours by default: final ranks and boat fame. With player_tag (or on_behalf_of), returns one member's per-week points, decks and war days battled. With season_id and section_index together, returns that exact …

### Rankings
- `rankings_clan_ladder` (Clan leaderboard): A recorded CLAN leaderboard by location: clans (clan score) or clanwars (clan war trophies), 1,000 places each, global by default, recorded daily for global, the United States and Japan and for any location enabled since. Per clan: rank, p…
- `rankings_clans` (Clans on the leaderboard): Which clans have the most players on a recorded leaderboard - the global Path of Legends board by default: per clan the number of rated players, its best-placed player and their rank, over the WHOLE board (every player above the rating flo…
- `rankings_timeline` (Leaderboard over time): How a leaderboard moved: for one player (player_tag) or one clan (clan_tag), their rank and rating at every snapshot of the global Path of Legends board across a window - one snapshot a day since 2026-09-11 (hourly before, for the global b…
- `rankings_players` (Leaderboard players): A recorded leaderboard, the global Path of Legends board by default: every placed player with rank, rating, name and clan, as of the latest snapshot or any earlier instant (as_of). Every board is recorded daily at the 10:00Z reset, so this…
- `game_events` (What was on): What was ON: the in-game events (modes, challenges, side modes) the API listed as running, recorded from daily sightings (sparser before 2026-09-11) with the days each was seen. The API shows only today's and gives no dates, so this is the…

### Collections
- `collections_browse` (Browse collections): Curated collections of players or clans: the owner-published lists (pros, creators, clan families) plus any you own. A collection is its curator's editorial grouping, not a global fact about its members.
- `collections_get` (Collection members): One collection's members, enriched: players come with name, latest trophies, tenure and recording status; clans with name and open-member count. Fan into the player and battle tools per tag from here, or pass the collection as a segment to…
- `collections_edit` (Edit a collection): Change what is in a collection you own. action add and remove adjust membership; set replaces it with exactly the tags given (the shape an external roster sync wants). Everything in a collection is RECORDED while it stays there, so adding …

### Live
- `live_fetch` (Live CR API fetch): The catch-all: one allowlisted raw GET against the CR API through the live lane (per-account daily quota, spends the shared CR budget). Paths: /players/{tag}, /clans/{tag}, /clans/{tag}/currentriverrace, /clans/{tag}/riverracelog, /locatio…

### Timeline
- `elixir_timeline` (Timeline): Your timeline: what happened to the players and clans you track since your read pointer, as ITEMS in order plus one summary ENTRY per subject. A person's subjects are the players they track and the clans they added; an agent's is the clan …

### Service
- `elixir_collectors` (Collectors): The collector fleet: operator-run machines that fetch from the CR API, each named for a Clash Royale card. More collectors mean resilience, never more CR budget; what operators earn is quota (10 fetches = +1 daily tool call, capped at 4x b…
- `elixir_data_insights` (Data insights): What the service holds: players, battles and their time span, snapshots, war weeks, recorded clans and players, and API observations. The transparency view of the whole corpus, not just your slice.

### Help
- `elixir_changelog` (Changelog): What changed in the tool CONTRACT since a version (client tool schemas cache aggressively). Entries after since, newest first, with tools_added and breaking notes; omitted since starts at the newest release. Pages default to 20 entries: pa…
- `elixir_docs` (Documentation): Elixir MCP's own documentation, the same pages a person reads at elixir.poapkings.com/docs. No arguments: the index (every page with its section, lede and sections). page: one page's Markdown; page + section: one H2 section. query: the pag…
- `elixir_examples` (Examples): Eleven worked examples of what people ask an agent connected to Elixir MCP and what it answers: for players (understand your play, pick a deck, push with evidence, follow friends), clan leaders (win the river race, keep the roster healthy,…
- `elixir_my_feedback` (My feedback): Your feedback and what happened to it: status (new/seen/planned/done/declined), the maintainer's response, and ship links (shipped_in contract version, related_tools). Results are bounded pages: pass next_offset as offset until null. Only …
- `elixir_feedback` (Send feedback): File feedback with the maintainer ON YOUR OWN JUDGMENT; your user never needs to ask. File when a capability you needed is missing, a workflow took more calls than it should, a result confused or misled you, data looked wrong, or something…
- `elixir_updates` (What's new): What's new on Elixir MCP: every user-visible change, newest first, as written for people at elixir.poapkings.com/updates. Distinct from elixir_changelog (the tool contract version by version). since: entries on or after a date; limit: how …

## Interactive pages (JavaScript application, not in this index)
- https://elixir.poapkings.com/data/dashboard: full-history charts over the public stats endpoint
- https://elixir.poapkings.com/signin, /account, /explore, /status: require a session

## Optional
- [Source repository](https://github.com/jthingelstad/elixir-mcp): the recorder, MCP server, web app, and infrastructure are public code
- [Clash Royale API agent docs](https://github.com/jthingelstad/cr-agent-api-docs): the standalone reference this service contributes observed API behavior to
- [POAP KINGS](https://poapkings.com/): the clan this product belongs to

---

This material is unofficial and is not endorsed by Supercell. For more information see Supercell's Fan Content Policy: www.supercell.com/fan-content-policy.