A no-auth remote MCP server that lets an assistant model game revenue splits with real storefront cuts, draft revenue-share agreements, and prepare studio setup
What you can do
Calculate take-home revenue from a game or app sale, applying storefront cuts, optional Unreal royalty, publisher cut and expenses, then splitting the contributor pool fairly. Look up and cite current platform revenue cuts and tiers for Steam, Epic, Apple, Google Play, console and itch.io. Draft a plain-English revenue-share agreement template between a studio and a contributor. Turn a studio plan into a one-click setup link that creates the studio, project and collaborators on signup. Explain what RoyalTea is and how it helps creative teams track contributions and split revenue.
When to use it
Useful when a game or app developer wants to estimate real take-home pay under different storefronts, needs a starting revenue-share agreement, or wants to hand collaborators a ready-made studio setup link.
Requirements
Remote streamable HTTP endpoint; no authentication, environment variables or headers declared.
Before you install
Agreement output is a clearly labeled template, not legal advice. The setup tool returns a link that, when opened and signed up for, creates a studio, project and placeholder collaborators on RoyalTea, so review the plan before sharing it.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/technology.royalty%2Froyaltea-public/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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>, what does each person actually take home'. No account needed.
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.
Parametersplatform
draft_revenue_agreement
Draft Revenue Agreement
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 RoyalTea. Use for 'draft a rev-share agreement for X to do Y for Z% of revenue'.
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.
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.
Takes no parameters.
Version history
1
v1.0.0LatestSep 16, 2026
Score
83%
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.