Tools
Every tool the registry exposes, generated from the contract on each deploy.
Every tool your agent sees through the MCP connection, grouped the way the
Clash Royale API agent docs
outline the game's surface — plus groups of our own. The same grouping rides each
tool's title (Players · Player profile), so clients that list tools
alphabetically cluster them.
This page is generated from the server's own tool registry
at build time, so it lists exactly what tools/list returns:
55 tools in 12 groups.
The machine-readable form is /tools.json.
Connecting
Point any MCP client at https://elixir.poapkings.com/mcp and complete the OAuth
flow. Access is approval-gated while the recorder grows —
request it first.
Authorization capabilities
The connection page lists these before you enter your sign-in code. Every OAuth
grant includes cr:read. A client that names no scope in particular is
offered every capability, ticked, on the consent page, where you can untick any of
them; a client that asks for less is offered the rest unticked. If a connected agent
needs a capability it does not have, Elixir MCP refuses the call and asks the client
to reconnect for that specific permission, or you change the connection's
capabilities under Account → Connections.
cr:read— Read recorded game data. Profiles, battles, clans, war, collections, and the live-fetch allowance.recordings:write— Change what you track. Track or stop tracking players and clans on your account.collections:write— Edit collections. Change membership in collections you own.account:write— Update account preferences. Change private nicknames and end-user identity mappings.feedback:write— Send feedback. File attributed feedback with the maintainer.account:email— Know your email address. Read the email on your Elixir account, so this app can sign you in as the same person. Offered only to an app that asks for it.
Connections created before this boundary shipped remain cr:read-only,
because that is what their original consent page promised. Owner-issued service
tokens are different: they are full-capability administrative credentials for
trusted headless integrations, shown once and revocable from the console.
What every response carries
Beside the fields a tool is for, every response carries the same four things:
applied, the one echo block saying what the tool actually used
(window, limit, sort, mode, segment, verbosity); notes[], one-sentence
caveats to repeat with the numbers; docs, a page#section
pointer into this documentation where the formulas live; and
meta, the envelope described on Reading a
response. 13 tools also declare an
outputSchema, rendered under each as "What comes back"; the argument
conventions they all share are on the
Protocol reference and, shorter, on
Choosing a tool.
The families
55 tools on one page is a wall, so each group is its own page. Every tool appears on exactly one of them.
- Account
- 6 tools —
elixir_my_players,elixir_nickname,elixir_my_identities,elixir_track_clan,elixir_track_player,elixir_identify - Players
- 9 tools —
badges_holders,badges_rarity,players_collection,players_search,players_profile,players_summary,players_timeline,elixir_coverage,players_names - Battles
- 10 tools —
battles_cards,battles_compare,battles_decks,battles_levels,battles_meta_cards,battles_meta_decks,battles_opponents,battles_performance,battles_query,battles_trends - Cards
- 2 tools —
cards_catalog,cards_synergy - Clans
- 6 tools —
clans_members_timeline,clans_participation,clans_pilot_scores,clans_roster,clans_standings,clans_timeline - War
- 4 tools —
war_current,game_clock,war_rivals,war_history - Rankings
- 5 tools —
rankings_clan_ladder,rankings_clans,rankings_timeline,rankings_players,game_events - Collections
- 3 tools —
collections_browse,collections_get,collections_edit - Live
- 1 tool —
live_fetch - Timeline
- 1 tool —
elixir_timeline - Service
- 2 tools —
elixir_collectors,elixir_data_insights - Help
- 6 tools —
elixir_changelog,elixir_docs,elixir_examples,elixir_my_feedback,elixir_feedback,elixir_updates