Royaltea
technology.royaltyPublished by royalty.technologyOfficial publisherv1.0.0Updated Oct 24, 2026
Manage your RoyalTea game studio: tasks, milestones, team, and royalty data. 77 tools, OAuth 2.1.
Overview
Lets an assistant manage a RoyalTea game studio's tasks, milestones, team, and royalty data through a hosted remote endpoint.
- What you can do
- Royaltea is a remote MCP server for running a RoyalTea game studio. According to its registry description, it exposes 77 tools covering tasks, milestones, team members, and royalty data, so an assistant can read and act on studio records. It connects over streamable HTTP to a hosted API rather than running locally.
- When to use it
- Worth adding if you already use RoyalTea for game studio management and want an assistant to work with your tasks, milestones, team, and royalty information in the same place. It is not useful without a RoyalTea account or studio data.
- Requirements
- A remote MCP client that supports streamable HTTP, pointed at the provider's hosted API endpoint. The description mentions OAuth 2.1, so an authorization flow and a RoyalTea account are likely needed; the manifest declares no environment variables or headers.
Installation
In SourceWeft
- Open Royaltea in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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/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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"royaltea": {
"type": "http",
"url": "https://api.royalty.technology/api/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
67% 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 listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- 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.