Connection guide

Back to category: Register an application

Other / Generic client

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

Other / Generic client

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

Register an OAuth client at id.web.money and copy the values into your client configuration. Public/local clients use PKCE and no client_secret. Confidential/server-side clients use client_secret_basic and must store the secret only in server-side configuration or a secret store.

Compatibility is not promised until the client is tested with its real callback, resource handling, and OAuth flow.

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.