Potencia tu agente
El comando propio del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
npx -y @blanketbyte/[email protected]Claude Code no tiene enlace de instalación para un comando local. Copia el comando de abajo y ejecútalo en una terminal.
claude mcp add blanketbyte-wise-mcp -- npx -y @blanketbyte/wise-mcp@1.1.1Ejecútalo en una terminal.
{ "mcpServers": { "blanketbyte-wise-mcp": { "command": "npx", "args": [ "-y", "@blanketbyte/[email protected]" ] } }}claude_desktop_config.json
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDel publicador
Ask Claude or ChatGPT about your Wise money.
The simplest, most complete MCP server for your Wise balances, card payments, transfers and recipients that can also prepare transfers you approve twice.
Run it locally with one npx command (Claude Desktop, Claude Code, Codex, Cursor…), or host it as a custom connector for Claude and ChatGPT.
MCP server for Wise: read balances, card payments, transfers and recipients, and prepare transfers you approve twice. Runs locally (npx, for Claude, Codex, Cursor…) or as a remote connector for Claude and ChatGPT.
"How much did I spend on groceries in September?" "What's left in my jars, in EUR?" "Show the transfers I sent to Mario this year and the rate I got." "Send Mario 120 EUR for dinner."
Give it a Wise API token once and your assistant can answer questions like these across all your Wise profiles, personal and business. It can also prepare transfers, new recipients and cancellations. Every change needs your explicit approval in chat, and a transfer only moves money once you pay it in the Wise app.
The simplest way to connect Wise to an AI assistant, and the most feature-rich Wise MCP server we know of (October 2026):
npx for Claude Desktop, Claude Code, Codex and Cursor, a one-click Claude Desktop extension, or a self-hosted connector for Claude and ChatGPT on web and mobile.Profiles are discovered from the token at runtime. Every tool takes an optional profile: an id, personal, business, or part of the profile name.
Locally, the server runs on your machine as a child process of your MCP client and reads the token from WISE_API_TOKEN. Nothing is hosted and there's no login.
Remotely, Wise doesn't offer OAuth to individuals, so the server is its own OAuth 2.1 authorization server for Claude and ChatGPT, and the "login" is a Wise personal API token you paste once.
sequenceDiagram
autonumber
participant C as Claude / ChatGPT
participant S as Wise MCP
participant W as Wise API
C->>S: Dynamic client registration (trusted redirect hosts only)
C->>S: /authorize (PKCE)
S-->>C: Login page: token + "stay connected for"
Note over C,S: You paste a Wise API token, pick 5 / 15 / 30 / 90 days or until revoked
S->>W: GET /v1/me
W-->>S: Wise user id
S->>S: Allowlist check, token sealed with AES-256-GCM
S-->>C: Authorization code → access + refresh tokens
C->>S: MCP tool calls (Bearer, 1 h tokens, rotating refresh)
S->>W: Reads, and writes only after confirm_action
/sessions lists every connected session for your Wise account and lets you revoke one or all. You sign in by pasting a Wise token again; it's only used to check who you are and is never stored. Access lasts 15 minutes in an HTTP-only cookie.prepare_* ──▶ summary + code (TX-…, RCP-…, CXL-…) ──▶ you approve in chat ──▶ confirm_action
nothing written to Wise yet ① created in Wise
│
transfers only: you pay it in the Wise app ◀──────────┘
② money moves only now
incoming_payment_waiting). Wise doesn't let personal tokens fund transfers for EU/UK accounts anyway, so the final "Pay" is always yours. Until then you can cancel the transfer with prepare_cancel_transfer or in the app.audit.log (~/.wise-mcp/ locally, the data volume when hosted).[!WARNING] Keep
TOKEN_ENCRYPTION_KEYout of backups of the data volume. Changing it makes stored tokens unreadable: just reconnect.
Needs Node.js 20 or newer. Create a token first: Wise → Settings → API tokens → Add new token (Full access to prepare transfers and recipients, Read only for answers only).
Download wise-mcp-<version>.mcpb from the latest release and open it. Claude Desktop asks for your token (stored securely, never in a plain config file) and whether to allow preparing transfers.
claude mcp add wise -e WISE_API_TOKEN=your-token -- npx -y @blanketbyte/wise-mcp
Add this to ~/.codex/config.toml:
[mcp_servers.wise]
command = "npx"
args = ["-y", "@blanketbyte/wise-mcp"]
env = { WISE_API_TOKEN = "your-token" }
Add this to the client's MCP config (for Claude Desktop: Settings → Developer → Edit config):
{
"mcpServers": {
"wise": {
"command": "npx",
"args": ["-y", "@blanketbyte/wise-mcp"],
"env": { "WISE_API_TOKEN": "your-token" }
}
}
}
The repo is also an Agent Plugin (plugin.json + mcp.json), so clients and directories that support the standard can install it directly. Set WISE_API_TOKEN in your client.
Optional env: WRITES_ENABLED=false for read-only, MAX_TRANSFER_AMOUNT for a per-transfer limit. Run npx @blanketbyte/wise-mcp --help for all options.
[!NOTE] ChatGPT only connects to remote servers, so for ChatGPT use the self-hosted setup.
The container serves plain HTTP on port 3000; put it behind anything that terminates HTTPS. State (sealed tokens, sessions) lives in /data.
A prebuilt image is published with every release: ghcr.io/blanketbyte/wise-mcp:<version> (or :latest), for linux/amd64 and linux/arm64. Use it instead of building from source wherever your platform accepts an image.
wise.example.com) at your Dokploy server.main, build type Dockerfile, context ../data (the container runs as uid 1000).PUBLIC_URL=https://wise.example.com
ALLOWED_WISE_USERS= # empty on the first deploy, see step 7
TOKEN_ENCRYPTION_KEY= # openssl rand -base64 32
https://wise.example.com/health.ALLOWED_WISE_USERS=<id>, redeploy and connect again.wise.example.com) at your Easypanel server.wise-mcp.main, build path /. (Or Git with the repository URL.)Dockerfile.PUBLIC_URL=https://wise.example.com
ALLOWED_WISE_USERS= # empty on the first deploy, see step 9
TOKEN_ENCRYPTION_KEY= # openssl rand -base64 32
wise.example.com, HTTPS on, port 3000. Easypanel issues the Let's Encrypt certificate.data with mount path /data. Without it, sessions and tokens are lost on every redeploy.https://wise.example.com/health.ALLOWED_WISE_USERS=<id>, deploy again and reconnect.To redeploy automatically on every push, enable Auto Deploy on the service (it adds a GitHub webhook).
cp .env.example .env # fill it in
mkdir -p data && sudo chown 1000:1000 data
docker compose up -d --build # listens on 127.0.0.1:3000
https://wise.example.com/mcp
ChatGPT: Settings → Apps & Connectors, turn on Developer mode (under Advanced), then Create a connector with the same /mcp address and OAuth authentication. The same login page opens.
Once deployed, your server has three pages you can open in a browser. Replace wise.example.com with your own address.
Common situations
ALLOWED_WISE_USERS and redeploy.For monitoring there's also https://wise.example.com/health, which returns {"ok":true} when the server is running.
At startup the server logs the allowed users and a short SHA-256 fingerprint of the encryption key, so you can tell which key is deployed without revealing it.
npm install
npm run dev # remote server with tsx watch (needs the remote env vars)
npm test # typecheck + both end-to-end suites
npm run e2e # remote server against a local mock of the Wise API
npm run e2e:stdio # local mode: spawns the CLI like an MCP client would
npm run mcpb # builds release/wise-mcp-<version>.mcpb
The remote end-to-end test boots the server next to a mock Wise API and drives everything Claude does: client registration, PKCE login, allowlist, session lengths, refresh rotation, encryption at rest, every tool (amount parsing, pagination, filters), the two-step writes (single-use codes, cross-session isolation, route requirements, cancellation, audit log, read-only tokens), /sessions, and revocation in Wise. The stdio suite covers the CLI, token errors, every tool over stdio, two-step writes, the audit log and read-only mode.
Push a tag matching package.json (e.g. v1.1.0). The release workflow runs the tests, publishes @blanketbyte/wise-mcp to npm with provenance (trusted publishing over GitHub OIDC, no npm token stored anywhere), lists it in the official MCP Registry from server.json, attaches the .mcpb to a GitHub release, and pushes the Docker image to ghcr.io/blanketbyte/wise-mcp. Before the first release, remove "private": true from package.json.
src/
cli.ts Entry point: `wise-mcp` (stdio) or `wise-mcp serve` (remote)
stdio.ts Local mode over stdin/stdout
index.ts Remote server: icons, OAuth routes, /login, /sessions, /mcp
config.ts Environment validation (shared and remote-only settings)
meta.ts Version, paths, links
crypto.ts AES-256-GCM sealing, cookie signing
tools.ts MCP tools (read + two-step write)
pending.ts Prepared actions and one-time confirmation codes
wise/client.ts Wise API client (retries, idempotent transfers, revocation detection)
wise/service.ts Profiles, balances, activities, transfers, recipients, rates
wise/connections.ts Encrypted per-token connections
auth/provider.ts OAuth 2.1 provider for Claude, token-paste login
auth/store.ts Clients, sessions, hashed tokens
auth/pages.ts Login, /sessions and message pages
public/ Logo, icons, favicon
mcpb/manifest.json Claude Desktop extension manifest
scripts/e2e.ts Remote end-to-end test with a mock Wise API
scripts/e2e-stdio.ts Local (stdio) end-to-end test
scripts/build-mcpb.sh Builds the .mcpb bundle
.github/workflows/ CI, and release to npm + GitHub
Personal API tokens can't use every Wise endpoint. In particular, for EU/UK accounts PSD2 rules block balance statements (so there's no running balance per transaction) and the card list. The activity feed covers card payments, so day-to-day spending questions work fine.
On the write side, personal tokens can't fund transfers for EU/UK accounts (you pay them in the Wise app, which this server relies on anyway), and Wise rejects API transfers on business accounts that have payment approval rules.
Issues and pull requests are welcome; see CONTRIBUTING.md. Please report security problems privately as described in SECURITY.md.
MCP server for Wise: read balances, card payments, transfers and recipients, and prepare transfers you approve twice. Runs locally (npx, for Claude, Codex, Cursor…) or as a remote connector for Claude
{ "mcpServers": { "blanketbyte-wise-mcp": { "command": "npx", "args": [ "-y", "@blanketbyte/[email protected]" ] } }}Resumen general
MCP server for Wise: read balances, card payments, transfers and recipients, and prepare transfers you approve twice. Runs locally (npx, for Claude, Codex, Cursor…) or as a remote connector for Claude and ChatGPT.
Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
Este registro no indica ninguna variable de entorno obligatoria.
@blanketbyte/wise se ejecuta localmente por stdio.
Última comprobación: 2026-11-15. MCP server for Wise: read balances, card payments, transfers and recipients, and prepare transfers you approve twice. Runs locally (npx, for Claude, Codex, Cursor…) or as a remote connector for Claude and ChatGPT.