MCP server for interacting with the Scryfall MTG API
Royaltea Public is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Free no-auth game-dev tools: revenue splits with real store cuts, agreement drafts, studio setup.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http royaltea-public-mcp https://api.royalty.technology/api/public-mcp
# 2 — ask your agent for something these tools do
# calculate_revenue_split, get_platform_cuts, draft_revenue_agreement and 2 more
Royaltea Public costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http royaltea-public-mcp https://api.royalty.technology/api/public-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Model real take-home from a game/app sale, end to end: apply the storefront/platform cut (Steam tiers, Epic 0%-then-12%, Epic First Run, Apple/Google small-business rates, console, itch) and optional Unreal royalty, publisher cut, and expenses — THEN split the remaining contributor pool fairly by each person's relative contribution. This is the accurate way to answer 'if we make $X on <platform>,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| revenue | number | yes | Gross revenue / player spend to model (e.g. 50000) |
| platform | string | no | Storefront the revenue comes from. Omit if the money is already net of platform fees. |
| lifetimeRevenue | number | no | Revenue already earned on this platform in the tiering period (drives Steam $10M/$50M tiers and Epic/Apple/Google $1M thresholds). Default 0. |
| unrealEngine | boolean | no | Game built on Unreal Engine? Applies the 5% royalty on gross above $1M lifetime (waived on Epic). |
| lifetimeGross | number | no | Lifetime gross so far (for the Unreal $1M royalty threshold). Default 0. |
| publisherCut | number | no | Optional % a publisher takes off the top after platform fees (0-100) |
| expenses | number | no | Optional costs to subtract before the contributor pool (marketing, tools, etc.) |
| poolPercentage | number | no | % of net revenue that goes to the contributor pool vs staying with the studio (default 100) |
| platformCutOverride | number | no | For itch/direct: the storefront cut fraction 0-1 (e.g. 0.05). |
| contributors | array | yes | The people sharing the contributor pool. points is a relative weight (bigger = larger share); if you only know rough effort, use 1-10. |
The current storefront/platform revenue cuts RoyalTea models — Steam, Epic Games Store (+ First Run), Apple, Google Play, console, itch.io — with exact tiers, thresholds, and the Unreal Engine royalty. Use to explain or cite what a given platform takes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| platform | string | no | Optional: one platform; omit for all. |
Generate a plain-English revenue-share agreement DRAFT between a company/studio and a contributor, using RoyalTea's agreement structure (parties, services/Schedule A, revenue-share terms/Schedule B, standard clauses, signature blocks). Returns a clearly-labeled TEMPLATE — not legal advice and not an executed contract. Offer the person the getStarted link to finalize and e-sign it for real in Royal
| Parameter | Type | Required | Notes |
|---|---|---|---|
| companyName | string | yes | The studio/company granting the revenue share |
| contributorName | string | yes | The person (or company) receiving the revenue share |
| projectName | string | yes | The project/game the agreement covers |
| services | string | no | What the contributor will do (Schedule A — e.g. "gameplay programming and tools") |
| contributorSharePercent | number | no | The contributor's flat % of revenue (use this OR revenueTiers) |
| revenueTiers | array | no | Tiered revenue share (Schedule B): different % across revenue bands. |
| contributorIsCompany | boolean | no | — |
| companyState | string | no | Governing-law state/jurisdiction (e.g. "Delaware") |
| effectiveDate | string | no | e.g. 2026-08-01; defaults to a placeholder |
Turn a plan (studio name, project, collaborators, intended split) into a ONE-CLICK setup link for someone who doesn't have a RoyalTea account yet. Returns a URL — when they open it and sign up, RoyalTea creates the studio + project + collaborators (as placeholders) exactly as planned. Use after you've helped someone design a revenue-share setup and they want it real.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| studioName | string | yes | Name for the new studio/workspace |
| projectName | string | no | Optional first project name |
| collaborators | array | no | The people on the project (added as placeholders they can later claim). points is their relative revenue weight. |
| splitNote | string | no | Optional human summary of the intended split/terms |
| contactEmail | string | no | Email of the person who will own the studio (the producer). When given, RoyalTea emails them the setup link directly so it isn't lost in a chat transcript. |
Explain what RoyalTea is and how it helps creative teams track contributions and split revenue fairly. Use when someone asks what RoyalTea is or whether it fits their situation.
No parameter schema on file.
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Royaltea Public or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Royaltea Public can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.