Royaltyport MCP supports two authentication methods. OAuth 2.1 is the recommended approach — MCP clients handle the flow automatically and you sign in via your browser. API tokens are available for server-side or headless environments.Documentation Index
Fetch the complete documentation index at: https://docs.royaltyport.com/llms.txt
Use this file to discover all available pages before exploring further.
OAuth 2.1
MCP clients authenticate via OAuth 2.1 using the authorization code flow with PKCE. When you connect for the first time, your client will open a browser window where you sign in to Royaltyport and approve access. No tokens to copy or manage.How it works
- Your MCP client discovers Royaltyport’s OAuth endpoints via the server metadata
- You are redirected to sign in and approve access on the consent screen
- The client receives an authorization code and exchanges it for access and refresh tokens
- The access token is used as a Bearer token for all MCP requests
MCP Client Configuration
Add the server URL to your MCP client configuration. OAuth is handled automatically — your client will open a browser window for you to sign in on first use.API Tokens
For server-side integrations, CI/CD pipelines, or MCP clients that don’t support OAuth, use an API token as a Bearer token.MCP Client Configuration
Pass the token in theheaders of your MCP client configuration: