Connection guide

Back to category: Register an application

n8n

Sign in through id.web.money, then check your available wallets or balance. A successful sign-in alone does not verify every operation.

Never paste secrets into chat

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

Requirements

Status
Experimental guide
Connection channel
Registered application
What you do
Register an OAuth application, configure its callback, then authorize through id.web.money.
Connection values

Notes

  • Redirect URI is configured by your MCP client.
  • provided by your MCP client

Setup

n8n

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

n8n usually needs its own registered callback URL and a separate OAuth credentials configuration.

  1. Register an OAuth client_id at id.web.money for your n8n callback URL.
  2. Choose public/local or confidential/server-side client settings according to where n8n runs.
  3. Set Auth URI Query Parameters to include resource=https://mcp.webmoney.com/.
  4. Request the scopes needed by the workflow.
  5. Store client_secret only in n8n credentials or a secret store when you use a confidential client.
  6. Do not paste client_secret, access_token, refresh_token, or JWT values into AI chat.

The n8n settings screen varies by version and installation. This guide is experimental and field labels may need adaptation.

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

This guide may require manual client configuration.