draft_revenue_agreement — royaltea public MCP Tool
draft_revenue_agreement
(draft revenue agreement) is one of 5 tools on the
royaltea public
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call draft_revenue_agreement from your client
- Claude Code royaltea public draft_revenue_agreement run in your project directory
- Claude Desktop royaltea public draft_revenue_agreement ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor royaltea public draft_revenue_agreement ~/.cursor/mcp.json
- VS Code royaltea public draft_revenue_agreement .vscode/mcp.json
- Zed royaltea public draft_revenue_agreement ~/.config/zed/settings.json
- Windsurf royaltea public draft_revenue_agreement ~/.codeium/windsurf/mcp_config.json
- Cline royaltea public draft_revenue_agreement ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI royaltea public draft_revenue_agreement ~/.gemini/settings.json
- Grok royaltea public draft_revenue_agreement .mcp.json (in your project root)
- ChatGPT royaltea public draft_revenue_agreement Settings → Connectors → Advanced → Developer mode
- Claude.ai royaltea public draft_revenue_agreement Settings → Connectors → Add custom connector
- LangChain royaltea public draft_revenue_agreement pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http royaltea-public https://api.royalty.technology/api/public-mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.