Skip to main content
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.

​
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

  1. Your MCP client discovers Royaltyport’s OAuth endpoints via the server metadata
  2. You are redirected to sign in and approve access on the consent screen
  3. The client receives an authorization code and exchanges it for access and refresh tokens
  4. 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. 
{
  "mcpServers": {
    "royaltyport": {
      "url": "https://mcp.royaltyport.com/agents/mcp"
    }
  }
}
MCP clients that support OAuth 2.1 (such as Claude Desktop) handle endpoint discovery and token management automatically. You just need to add the server URL and your client does the rest.

​
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 the headers of your MCP client configuration: 
{
  "mcpServers": {
    "royaltyport": {
      "url": "https://mcp.royaltyport.com/agents/mcp",
      "headers": {
        "Authorization": "Bearer rp_your_token_here"
      }
    }
  }
}

​
Creating Tokens

Tokens are managed from Organizations > Settings > Tokens. See API Authentication for full details on creating and managing tokens.