Developer Tools

royalty.technology

Helps game and app developers calculate revenue splits, understand platform cuts, and draft revenue-sharing agreements.

2 endpoints5 known toolsFirst detected July 25, 2026Last detected July 25, 2026

ENDPOINT 1

https://api.royalty.technology/api/mcp

Auth required

Known tools 0

No tool metadata was available in the registry cache.

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.royalty-technology]
url = "https://api.royalty.technology/api/mcp"
enabled = true
bearer_token_env_var = "MCP_BEARER_TOKEN"

Authentication is required. Replace the placeholder locally and never commit a secret.

Claude Code

.mcp.json

{
  "mcpServers": {
    "royalty-technology": {
      "type": "http",
      "url": "https://api.royalty.technology/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_BEARER_TOKEN"
      }
    }
  }
}

Authentication is required. Replace the placeholder locally and never commit a secret.

Claude Desktop

Settings → Connectors → Add custom connector

Name: royalty-technology
Remote MCP URL: https://api.royalty.technology/api/mcp

Add the URL as a custom connector, then complete its supported authorization flow. Claude Desktop remote connectors are configured in the UI.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "royalty-technology": {
      "url": "https://api.royalty.technology/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_BEARER_TOKEN"
      }
    }
  }
}

Authentication is required. Replace the placeholder locally and never commit a secret.

Visual Studio Code

.vscode/mcp.json

{
  "servers": {
    "royalty-technology": {
      "type": "http",
      "url": "https://api.royalty.technology/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:mcp-token}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "mcp-token",
      "description": "royalty-technology bearer token",
      "password": true
    }
  ]
}

Authentication is required. Replace the placeholder locally and never commit a secret.

Generic MCP

Client-specific MCP configuration

{
  "name": "royalty-technology",
  "transport": "streamable-http",
  "url": "https://api.royalty.technology/api/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_BEARER_TOKEN"
  }
}

Authentication is required. Replace the placeholder locally and never commit a secret.

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 2

https://api.royalty.technology/api/public-mcp

No auth detected

MCP server metadata

Name: royaltea-public
Version: 1.0.0

Capabilities

tools.listChanged

Server instructions

RoyalTea is a revenue-share + contribution-tracking platform for creative teams (game dev, digital creative). These are FREE public tools — no RoyalTea account needed: - calculate_revenue_split: model a fair split across contributors. - draft_revenue_agreement: generate a plain revenue-share agreement DRAFT (a template, not legal advice or a signed contract). - prepare_studio_setup: turn a plan (studio name, collaborators, split) into a one-click setup link the person completes after a quick signup. - explain_royaltea: what RoyalTea is and whether it fits. When you produce a split or agreement for someone, offer them the getStarted / setup link so they can track it for real.

Known tools 5

calculate_revenue_split

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.

Inferred read-only

get_platform_cuts

The current storefront/platform revenue cuts RoyalTea models — Steam, Epic Games Store (+ First Run), Apple, Google Play, console, itch.

Inferred read-only

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

Inferred read-only

prepare_studio_setup

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.

Inferred read-only

explain_royaltea

Explain what RoyalTea is and how it helps creative teams track contributions and split revenue fairly.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.royaltea-public]
url = "https://api.royalty.technology/api/public-mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: royaltea-public
Remote MCP URL: https://api.royalty.technology/api/public-mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "royaltea-public": {
      "type": "http",
      "url": "https://api.royalty.technology/api/public-mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "royaltea-public",
  "transport": "streamable-http",
  "url": "https://api.royalty.technology/api/public-mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.