OpenClaw setup guide

Add live revenue context to OpenClaw.

Register VerifiedMRR as a Streamable HTTP server in OpenClaw, authenticate through OAuth, and prove the connection with a live MCP probe before an agent depends on it.

Open free dashboard See pricing

Add the remote server

Use OpenClaw's managed outbound MCP registry. The transport flag matters: VerifiedMRR uses Streamable HTTP, not legacy SSE.

openclaw mcp add verifiedmrr \
  --url https://verifiedmrr.com/mcp \
  --transport streamable-http \
  --auth oauth \
  --oauth-scope revenue:read

Log in and probe it

The login command opens the VerifiedMRR authorization flow. After approval, doctor --probe makes a real connection and confirms the tools are discoverable rather than only checking saved configuration.

openclaw mcp login verifiedmrr
openclaw mcp doctor verifiedmrr --probe
openclaw mcp show verifiedmrr --json

Operate it safely

VerifiedMRR exposes only read-only tools, so it is suitable for unattended reporting and monitoring. Still instruct the agent to check get_sync_status before drawing conclusions from a period that may not have finished syncing.

If an already-running Gateway or agent does not see the new server, run openclaw mcp reload and restart the owning process when required. Use openclaw mcp logout verifiedmrr to clear stored OAuth credentials without removing the server definition.

Paste this after setup

Run this as the first OpenClaw task after the live probe succeeds.

Verify my VerifiedMRR MCP connection in OpenClaw. List the available VerifiedMRR tools, call get_sync_status, then call list_projects. Report whether authentication works, whether any source is stale or degraded, and which read-only analyses are now available. Do not combine currencies or expose credentials.

Keep exploring

Finish the agent setup.

MCP overviewTools, authentication, and data boundaries.Revenue analysis promptsA repeatable daily and monthly agent loop.OpenClaw MCP docsOfficial registry, OAuth, probe, and transport reference.

FAQ

Before you connect a provider.

Should I use streamable-http or SSE?

Use streamable-http. VerifiedMRR implements the current remote MCP transport; OpenClaw's SSE option is for legacy servers.

What proves the server is actually working?

Run openclaw mcp doctor verifiedmrr --probe. Unlike a configuration-only status check, the probe opens a live connection and lists capabilities.

Can I use a personal token instead of OAuth?

Yes. Save an Authorization bearer header in the server definition, but avoid committing a literal token. OAuth is the recommended interactive path.

Give OpenClaw verified numbers.

Open free dashboard