Client catalog

Register an OAuth application

Use this path for n8n, corporate or server-side clients, custom connectors, and clients where WebMoney does not provide a pre-registered client_id.

  1. What to register

    Register a separate OAuth application for the MCP client at id.web.money.

  2. Which client type to choose

    Public/native clients cannot keep a secret and should use PKCE. Confidential/hosted clients run on a server that can protect its own client_secret.

    Authorization Code with PKCE protects public clients that cannot keep a client_secret.

  3. Which callback URLs and scopes to use

    The redirect URI must match the application callback. Native clients commonly use localhost callbacks.

    The resource parameter identifies the MCP resource audience, for example https://mcp.webmoney.com/.

    Start with openid and only the wm.* scopes your task needs. The example below reads balances; offline_access requests supported refresh. Add other capabilities explicitly. wm.invoices.manage permits changes to invoices as well as reads.

    Exact technical values

    Example: public/native client

    A local application cannot keep a shared secret: use none, PKCE S256 and the exact registered loopback callback. Do not create or embed a secret.

    authorization_code, refresh_token, PKCE S256

    Example: confidential/server client

    A server application uses client_secret_basic, keeps its secret server-side, and uses PKCE S256 with its exact HTTPS callback. Never put the secret in a browser, chat or public configuration.

    authorization_code, refresh_token, PKCE S256

  4. How to verify the connection

    First verify sign-in and available read operations, then confirm that the agent sees only selected wallets and access grants.

    Use separate production and development clients so test callbacks and permissions do not leak into production configuration.

  5. How to store the secret

    A client_secret belongs only to a confidential application and must be stored server-side.

    Keep secrets out of AI chat

    Save the client_secret securely. Do not paste it into an AI message, support ticket, or form on this site.

Client examples

n8n

Experimental guide

Registered application

n8n uses an OAuth application registered by you, rather than a ready catalog integration.

resource=https://mcp.webmoney.com/

Open guide

Other / Generic client

Experimental guide

Registered application

Use this template for corporate clients, server-side clients, custom connectors, and clients where WebMoney does not provide a pre-registered client_id.

Open guide

Connection help

Reauthorization

Reauthorize after changing requested capabilities or wallet access grants.

Troubleshooting

Check the MCP address, callback URL, application identifier, and MCP support in the selected platform.

Never paste secrets into chat

Do not enter access tokens, refresh tokens, WebMoney JWTs, or client secret values in any AI message.

Known limitations

Some client guides may require manual client configuration.