Claude web and desktop
Open Settings → Connectors, choose Add custom connector, enter VerifiedMRR and https://verifiedmrr.com/mcp, then complete the OAuth sign-in. Organization owners may need to enable or add the connector before members can use it.
In a new conversation, enable the connector and ask Claude to list projects before requesting analysis. Starting with a read verifies the connection and gives Claude the project IDs it needs for deeper queries.
Claude Code with OAuth
Add VerifiedMRR as a user-scoped remote HTTP server. In Claude Code, run /mcp and select the server to complete the browser login. User scope makes the connection available across projects on your machine.
claude mcp add --transport http --scope user verifiedmrr https://verifiedmrr.com/mcp
claude
# Inside Claude Code:
/mcp
Claude Code with a personal token
For a headless machine, create a token in VerifiedMRR Settings → Agent access and pass it as a bearer header. Avoid putting the literal token in a committed project-level .mcp.json file.
claude mcp add --transport http --scope user verifiedmrr https://verifiedmrr.com/mcp \
--header "Authorization: Bearer vmrr_mcp_REPLACE_ME"
claude mcp list
FAQ
Before you connect a provider.
Does VerifiedMRR support Claude OAuth?
Yes. Add the remote HTTP endpoint and use /mcp in Claude Code, or the custom connector flow in Claude, to authorize your workspace.
What scope should I use in Claude Code?
User scope is convenient across projects. Use local or project scope only when you intentionally want the server limited or shared through that project's configuration.
Can Claude modify revenue or payment data?
No. VerifiedMRR's MCP tools are read-only and do not expose refunds, payouts, subscriptions, customers, or credentials.