Official descriptionClash Royale history recorder + remote MCP server. Unofficial; not endorsed by Supercell.
Config template (adjust for your client)
claude mcp add elixir-mcp -- npx -y elixir-mcp
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
1 ★ · jthingelstad/elixir-mcp · read from the repository page · (checked 2026-10-16 20:00:20)
Source
read directly from its GitHub page · type: open-source project
Harvest history
first seen 2026-10-10 · last seen 2026-10-16 · seen 6× · listed by 1 sources
Score
score 103 · 1 ★ · 1 sources · repo
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository jthingelstad/elixir-mcp;first catalogued 2026-10-10;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
Clash Royale history, recorded, and served to your own agent. The Clash Royale API only answers "what is true right now": no trophy timelines, no battle archive beyond a rotating log of about 30 battles, no per-season history. Elixir MCP records those observations continuously and keeps them. It records the players and clans its accounts track and the members of the clans it tracks. The record is served on one origin: the Console, Ladder and Elixir Clan in the browser, an authenticated remote MCP server for agents, and a versioned JSON API. - Web: - MCP: https://elixir.poapkings.com/mcp - JSON API: https://elixir.poapkings.com/api/v1 **What the service does is documented publicly**, at ; this repository does not describe product behavior. Want to help run the fetch fleet? See the operator guide. Repository An npm workspaces monorepo. | Path | What it holds | | --- | --- | | apps/site | The static half of the site (Eleventy): home, docs, updates, and the machine-readable surfaces | | apps/web | The application half (React): the Console, Ladder (src/ladder) and the shell Elixir Clan's views run in | | services/ | The Lambdas, each only its door (entry, handler, routes): collector, email-relay, jobs, mcp, migrate, scheduler, timeline-sync, web-api | | packages/ | What more than one Lambda or app runs, imported by name: auth, claims, client, clan, clan-engine, clan-state, clan-web (Elixir Clan), collector-door (the collectors' config, lease and submit), contracts (the tool and API contract), design, docs, ingest, ledger, mail, outbox, record, syndication (the timeline cross-posted to Discord), tools (the tool registry), ui | | acceptance/ | The read-only acceptance suite run against the live service | | db/migrations | The ordered schema migrations | | infra/ | The CloudFormation template and the build, deploy and maintenance scripts | | scripts/ | The setup hook for a session's own worktree | | docs/ | Engineering invariants, the decision ledger, how production is operated, and one note per change | For contributors: AGENTS.md holds the golden rules and points to each area's own guide (Console, Ladder, Clan, tools, site, infra); docs/ENGINEERING.md the build invariants, docs/DECISIONS.md the ratified decisions and docs/OPERATIONS.md how production is operated.