Connect AI to RoyalTea (MCP)

Quick start

• Add RoyalTea as a connector (recommended). In Claude (web or desktop), open Settings → Connectors → “Add custom connector” and paste the server URL below. Approve the one-click consent screen — no token to copy or store.
• Or use a personal API token. For scripts and clients without OAuth support, create an rtpat_ token in RoyalTea under Preferences → AI & API Access and pass it as a bearer header.

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

Claude Code (terminal):

claude mcp add --transport http royaltea https://api.royalty.technology/api/mcp \
  --header "Authorization: Bearer rtpat_YOUR_TOKEN"

Any Streamable-HTTP MCP client (JSON config):

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

What the assistant can (and can’t) do

A connected client operates with your identity and your permissions. It is a capable teammate, with money and legal actions deliberately kept in the app.

It can: create, update, organize, and delete tasks & subtasks; write descriptions, comments, and labels; log time and record contributions; create and manage milestones; create projects, invite teammates, and plan meetings; read revenue, distributions, payouts, and royalty configuration; preview a distribution; search the marketplace; read notifications, messages, and governance.

It can’t: run or finalize a distribution (only preview), change royalty weights or split configuration, move money or trigger payouts, sign or approve agreements, or act outside the studios you belong to. Those guardrails are enforced on the server for every call — not just hidden in the UI.

Tool reference — 77 tools (44 read, 33 write)

All tools are scoped to your access. The two destructive tools (delete_task, delete_milestone) are annotated so clients prompt before running them. Most tools accept an optional studioId; omit it if you belong to exactly one studio.

Read (44)

• Studios & projects: list_studios, list_projects, get_project_summary, analyze_project_health, suggest_next_actions
• Tasks & boards: list_tasks, search_tasks, get_task_details, get_board_columns, list_labels
• Milestones: list_milestones, get_milestone_progress
• Team & people: get_team_workload, get_team_member, get_leaderboard, get_skills
• You — stats, progression, gigs: get_my_stats, get_my_progression, list_achievements, get_my_gigs, get_referral_info
• Contributions & time: list_contributions, get_time_report, get_comments
• Resources: list_resources, get_resource
• Finance & royalties (read-only): get_revenue_summary, list_distributions, get_distribution_details, preview_distribution, get_royalty_breakdown, get_royalty_config, get_my_payouts, get_agreement_status, list_expenses
• Marketplace: search_marketplace
• Comms & governance: list_notifications, list_calendar_events, list_conversations, get_conversation_messages, list_friends, list_proposals, list_polls, list_feature_requests

Write (33)

• Tasks: create_task, bulk_create_tasks, create_subtask, update_task, bulk_update_tasks, log_time, add_comment, delete_task
• Labels & board: manage_labels, update_board_column
• Milestones: create_milestone, update_milestone, assign_task_to_milestone, delete_milestone
• Resources: create_resource
• Projects, studios & team: create_project, update_project, create_studio, invite_teammate, update_team_member
• Meetings: create_meeting, rsvp_meeting, log_meeting_attendance
• Expenses: add_expense
• Governance & social: create_proposal, vote_on_proposal, vote_on_poll, mark_notifications_read, send_message, add_skill, endorse_skill, send_friend_request, create_feature_request

No-account tools (public MCP)

RoyalTea also runs a small unauthenticated MCP surface so an AI can help someone who doesn’t have an account yet — then hand them a link to continue for real. No RoyalTea data is read or written.

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

• calculate_revenue_split — model a fair revenue split across contributors, with real storefront cuts (Steam, Epic, console, mobile) applied first.
• get_platform_cuts — look up current platform economics: Steam tiers, Epic 12% / First Run, Apple/Google, Unreal royalty, itch.io, and more.
• draft_revenue_agreement — generate a plain revenue-share agreement draft (a template, not legal advice).
• prepare_studio_setup — turn a plan (studio, collaborators, split) into a one-click setup link the person completes after a quick signup.
• explain_royaltea — what RoyalTea is and whether it fits a given team.

Protocol & endpoints

RoyalTea implements MCP over Streamable HTTP (stateless JSON-RPC 2.0) and acts as its own OAuth 2.1 authorization server with PKCE (S256), Dynamic Client Registration (RFC 7591), and resource indicators (RFC 8707).

• Authenticated MCP: https://api.royalty.technology/api/mcp
• Public MCP (no auth): https://api.royalty.technology/api/public-mcp
• Protected resource metadata (RFC 9728): https://api.royalty.technology/.well-known/oauth-protected-resource
• Authorization server metadata (RFC 8414): https://api.royalty.technology/.well-known/oauth-authorization-server
• Authorize / Token / Register: https://api.royalty.technology/oauth/{authorize,token,register}
• Methods: initialize, tools/list, tools/call, ping. Protocol versions 2025-06-18, 2025-03-26, 2024-11-05.

Security & privacy

• Tokens are shown once and stored only as a SHA-256 hash; OAuth secrets are hashed or encrypted at rest.
• Every tool call re-checks your studio membership and role on the server — a connection can never exceed your own access.
• Money and legal actions (distributions, royalty weights, payouts, signing agreements) are never exposed to AI clients.
• Revoke a connector or token anytime from Preferences → AI & API Access.
• See the Privacy Policy for how data is handled, including AI processing subprocessors.