royaltea-public

Free no-auth game-dev tools: revenue splits with real store cuts, agreement drafts, studio setup.

¿Debería usar esto?

Calidad y seguridad

B
Calidad de la descripción
92%
Integridad del esquema
84%
Calidad de los nombres
88%
Riesgo de envenenamiento
80%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Hallazgos (3)

  • HIGHTool poisoning patterns detected
  • MEDIUMTool 'prepare_studio_setup' description contains placeholder texten prepare_studio_setup
  • INFOTool description contains placeholder or incomplete texten prepare_studio_setup

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~1,452Tokens (definiciones de herramientas)
~2.4 KBTamaño de respuesta típico
Impacto moderado en la atención (1.13% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "royaltea-public": {
      "url": "https://api.royalty.technology/api/public-mcp"
    }
  }
}

Puntos de conexión remotos

https://api.royalty.technology/api/public-mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (5)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢calculate_revenue_split(revenue, platform, lifetimeRevenue, unrealEngine, lifetimeGross, ...)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "revenue": {
      "type": "number",
      "description": "Gross revenue / player spend to model (e.g. 50000)"
    },
    "platform": {
      "type": "string",
      "enum": [
        "steam",
        "epic",
        "epic_first_run",
        "apple",
        "google_play",
        "console",
        "itch",
        "direct"
      ],
      "description": "Storefront the revenue comes from. Omit if the money is already net of platform fees."
    },
    "lifetimeRevenue": {
      "type": "number",
      "description": "Revenue already earned on this platform in the tiering period (drives Steam $10M/$50M tiers and Epic/Apple/Google $1M thresholds). Default 0."
    },
    "unrealEngine": {
      "type": "boolean",
      "description": "Game built on Unreal Engine? Applies the 5% royalty on gross above $1M lifetime (waived on Epic)."
    },
    "lifetimeGross": {
      "type": "number",
      "description": "Lifetime gross so far (for the Unreal $1M royalty threshold). Default 0."
    },
    "publisherCut": {
      "type": "number",
      "description": "Optional % a publisher takes off the top after platform fees (0-100)"
    },
    "expenses": {
      "type": "number",
      "description": "Optional costs to subtract before the contributor pool (marketing, tools, etc.)"
    },
    "poolPercentage": {
      "type": "number",
      "description": "% of net revenue that goes to the contributor pool vs staying with the studio (default 100)"
    },
    "platformCutOverride": {
      "type": "number",
      "description": "For itch/direct: the storefront cut fraction 0-1 (e.g. 0.05)."
    },
    "contributors": {
      "type": "array",
      "description": "The people sharing the contributor pool. `points` is a relative weight (bigger = larger share); if you only know rough effort, use 1-10.",
      "items": {
        "type": "object",
        "properties": {
          "name": {
            "type": "string"
          },
          "points": {
            "type": "number",
            "description": "Relative contribution weight"
          },
          "role": {
            "type": "string",
            "description": "Optional role (e.g. Programmer, Artist)"
          }
        },
        "required": [
          "name"
        ]
      }
    }
  },
  "required": [
    "revenue",
    "contributors"
  ]
}
🟢get_platform_cuts(platform)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "platform": {
      "type": "string",
      "enum": [
        "steam",
        "epic",
        "epic_first_run",
        "apple",
        "google_play",
        "console",
        "itch",
        "direct"
      ],
      "description": "Optional: one platform; omit for all."
    }
  }
}
🟢draft_revenue_agreement(companyName, contributorName, projectName, services, contributorSharePercent, ...)

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'.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "companyName": {
      "type": "string",
      "description": "The studio/company granting the revenue share"
    },
    "contributorName": {
      "type": "string",
      "description": "The person (or company) receiving the revenue share"
    },
    "projectName": {
      "type": "string",
      "description": "The project/game the agreement covers"
    },
    "services": {
      "type": "string",
      "description": "What the contributor will do (Schedule A — e.g. \"gameplay programming and tools\")"
    },
    "contributorSharePercent": {
      "type": "number",
      "description": "The contributor's flat % of revenue (use this OR revenueTiers)"
    },
    "revenueTiers": {
      "type": "array",
      "description": "Tiered revenue share (Schedule B): different % across revenue bands.",
      "items": {
        "type": "object",
        "properties": {
          "from": {
            "type": "number"
          },
          "to": {
            "type": "number",
            "description": "null/omit for \"and above\""
          },
          "contributorSharePercent": {
            "type": "number"
          }
        },
        "required": [
          "from",
          "contributorSharePercent"
        ]
      }
    },
    "contributorIsCompany": {
      "type": "boolean"
    },
    "companyState": {
      "type": "string",
      "description": "Governing-law state/jurisdiction (e.g. \"Delaware\")"
    },
    "effectiveDate": {
      "type": "string",
      "description": "e.g. 2026-08-01; defaults to a placeholder"
    }
  },
  "required": [
    "companyName",
    "contributorName",
    "projectName"
  ]
}
⚪prepare_studio_setup(studioName, projectName, collaborators, splitNote, contactEmail)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "studioName": {
      "type": "string",
      "description": "Name for the new studio/workspace"
    },
    "projectName": {
      "type": "string",
      "description": "Optional first project name"
    },
    "collaborators": {
      "type": "array",
      "description": "The people on the project (added as placeholders they can later claim). `points` is their relative revenue weight.",
      "items": {
        "type": "object",
        "properties": {
          "name": {
            "type": "string"
          },
          "email": {
            "type": "string"
          },
          "role": {
            "type": "string"
          },
          "points": {
            "type": "number"
          }
        },
        "required": [
          "name"
        ]
      }
    },
    "splitNote": {
      "type": "string",
      "description": "Optional human summary of the intended split/terms"
    },
    "contactEmail": {
      "type": "string",
      "description": "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."
    }
  },
  "required": [
    "studioName"
  ]
}
🟢explain_royaltea

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.

Esquema de entrada

{
  "type": "object",
  "properties": {}
}

Prompts recomendados

retrieve_data
Get details about [item] from royaltea-public
Herramientas esperadas: get_platform_cuts
fetch_info
Fetch [information type] using royaltea-public
Herramientas esperadas: get_platform_cuts

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada5 herramientas
verificadoversión no registrada5 herramientas