Connection guide

Back to category: Local clients

Claude Code

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

Requirements

Status
Connection verification pending
Connection channel
Local public client
What you do
Copy the public client_id and local settings into your desktop client, then authorize through id.web.money.
Connection values

Notes

  • This is a public client with PKCE: its application identifier is published, and no client secret is created or entered.

Setup

Claude Code Local

Use the published WebMoney public OAuth client for local Claude Code. Its loopback callback is registered, so you do not need to register another application.

  1. Open the local Claude Code MCP configuration.
  2. Copy the MCP URL, resource, and public client_id from the connection values on this page.
  3. Use the registered callback, scopes, grant type, token authentication method, and PKCE mode from the exact OAuth settings on this page.
  4. Do not register another OAuth application or substitute a different callback.
  5. Start the authorization flow from Claude Code.
  6. Complete OAuth sign-in at id.web.money.
  7. Confirm only the credential capabilities needed by Claude Code.

End-to-end verification of the new public client is still pending. The exact registered callback appears in the OAuth settings on this page.

Exact OAuth registration settings

These are the public settings registered for this catalog client.

Client name
WebMoney MCP for Claude Code Local
Client ID
eJ7abyUTmCfEbSZ5s9XE
Registered audience
https://mcp.webmoney.com
MCP URL
https://mcp.webmoney.com/mcp
OAuth resource
https://mcp.webmoney.com/
Scopes
  • openid
  • email
  • phone
  • profile
  • offline_access
  • wm.balance.read
  • wm.transactions.read
  • wm.messages.read
  • wm.messages.send
  • wm.invoices.manage
  • wm.transfers.create
  • wm.recipients.resolve
Grant types
  • authorization_code
  • refresh_token
Response types
code
Redirect URLs
http://localhost:8766/callback
Token endpoint client authentication
none — no client secret
PKCE
S256
Client URL
https://mcp.webmoney.com/docs
Verification status
Connection verification pending

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.