RouteMyAgent

Connect MCP with OAuth

OAuth is not enabled on this deployment yet. Use the existing private-token connection until setup is completed.

OAuth lets a compatible client request access to your RouteMyAgent account without manually copying a router token. It is an alternative to private token setup; accountless wallet MCP remains available separately.

  1. In RouteMyAgent, choose Sign in to an existing account and use the account you want the client to access. A guest workspace and a signed-in account are separate; OAuth does not transfer a guest workspace or its credentials.
  2. In that account's workspace, select free gateway access and attach your own authorized NVIDIA key privately. Never give a client your NVIDIA password, or paste a key into chat.
  3. Add https://routemyagent.dev/mcp as a remote Streamable HTTP MCP server in your client. Choose its OAuth connection option, if offered. Current availability and authorization metadata are published in service discovery.
  4. Sign in on the Clerk authorization page and review the app and requested permissions. mcp:read permits MCP connection and model discovery. mcp:delegate additionally permits model-help requests. Approve only the client you intended to connect.
  5. Allow the client to complete its PKCE code exchange and keep its access and refresh tokens in private credential storage. Call router_models to inspect available exact model IDs.
  6. Before paid delegation, review and explicitly enable MCP billing in the RouteMyAgent workspace and add prepaid credit if needed. OAuth approval does not enable billing, create credit, include NVIDIA quota or expose your saved provider key. Direct gateway routing remains free; MCP model help currently costs $0.001 per successful completed call.

Revoke a connection

Use your Clerk account's connected-application controls to revoke the OAuth app. Compatible clients can also use the issuer's published revocation endpoint. Our configured OAuth path uses opaque tokens and verifies them with Clerk for each authorized operation, including resource audience, expiry, revocation and scope. Revocation blocks subsequent operations; it does not undo a tool effect or a model request already accepted. Disconnect a provider key separately in RouteMyAgent if desired.

If the client cannot connect

Use the private token setup instructions when your client does not support this OAuth flow. Invalid, expired, revoked, wrong-resource or insufficient-scope tokens are rejected. Provider errors and unavailable Clerk verification remain real errors; neither grants permission to retry paid calls blindly. Inspect the original receipt after an uncertain result.

OAuth applies only to workspace MCP. It does not grant access to account management, provider-key controls, Stripe or the direct gateway endpoints. Accountless wallet help uses its separate documented payment flow.

Key protection · Terms · Support