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: 47 tools in 11 groups. The machine-readable form is /tools.json.

Connecting

Point any MCP client at https://elixir.poapkings.com/mcp and complete the OAuth flow. Create an account by verifying your email — create one first.

Authorization capabilities

The connection page lists these before you enter your sign-in code. Every OAuth grant includes cr:read, and a client that names no scope asks for it alone. The consent page offers every other standard capability as a checkbox: unticked on your own connection, and on an agent's connection every write but recordings:write starts ticked. If a connected agent needs a capability it does not have, Elixir 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. Read what Elixir records: player profiles, battles, clans, war and your timeline, plus your live-fetch allowance.
  • recordings:write — Change what you track. Start or stop tracking players and clans for you. Each player or clan tracked uses one of your tracking slots.
  • account:write — Update account preferences. Remember who is talking to it (link a chat user to their player, so "my deck" means theirs) and set your private nicknames.
  • feedback:write — Send feedback. Send feedback to the Elixir maintainer for you, when something is wrong or missing.
  • 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 the Elixir family's own apps, when they ask for it.
  • clans:attest — Record what you do in your clan. Tell Elixir what you did in your clan through this app (a departure you classified, a promotion, an award, a message to the clan), labelled as yours. Offered only to the Elixir family's own apps, when they ask for it.

An agent's key is different: it carries the capabilities it was issued with (every one unless its owner narrowed them), edited on the agent's Settings page, and is shown once and revocable from the website. Integration keys work only at the JSON API, never here.

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), on every tool but six (elixir_my_players, elixir_my_identities, elixir_coverage, elixir_collectors, elixir_data_insights, and elixir_examples without an example); 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. 47 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

47 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
7 tools — battles_cards, battles_compare, battles_decks, battles_opponents, battles_performance, battles_query, battles_trends
Cards
3 tools — cards_catalog, cards_archetype, cards_card
Clans
7 tools — clans_members_timeline, clans_participation, clans_roster, clans_standings, clans_timeline, clans_my_view, clans_context
War
4 tools — war_current, game_clock, war_rivals, war_history
Game
1 tool — game_events
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_send_feedback, elixir_updates

Help for 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.

Read more

The page you are on rides along. Every item is answered, and the answer comes to your email and your timeline.