Provides read-only tools for Wise (TransferWise) including profiles, balances, exchange rates, transfers, and recipients.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Wise MCP Server list my Wise profiles and balances"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Wise (TransferWise) Personal API MCP server. Read-only: profiles, balances, rates, transfers, recipients.
wise_list_profiles, wise_get_profile
wise_list_balances, wise_get_balance
wise_get_exchange_rate, wise_get_exchange_rate_history
wise_list_transfers, wise_get_transfer
wise_list_recipients, wise_get_recipient, wise_get_account_requirements
Write tools (create/fund/cancel transfer, create/delete recipient, create quote) are intentionally not in v0.1.x — they require idempotency + SCA state-machine handling, planned for v0.2.0.
Related MCP server: t212-mcp-server
Env var | Required | Default | Purpose |
| yes | — | Personal API token from https://wise.com/settings/api-tokens |
| no |
| Sandbox override: |
| no |
| Per-request timeout |
| no | — | Dangerous override — see below |
WISE_API_BASE_URL is locked down by default:
Must use https://
Host must be on the allowlist: api.wise.com or api.sandbox.transferwise.tech
Violation throws WiseConfigError before any Bearer token leaves the machine. This prevents token exfiltration via a misconfigured env, a bad CI value, or a malicious override.
Dangerous override: set
WISE_API_ALLOW_UNSAFE_BASE_URL=1to bypass both checks (allowhttp://and arbitrary hosts). Only use for local testing against a mock server. Never enable this in production or with a real Wise token. The token will be sent to whatever host you configure.
Two ways to run this server — pick the one that fits.
No local runtime, no env vars on your machine — your Wise token is AES-256-GCM encrypted server-side via HashiCorp Vault.
Sign up at aiwerkmcp.com.
Install Wise from the catalog and paste your WISE_API_TOKEN.
Point your MCP client (Claude.ai, Cursor, Hermes, …) at your hosted endpoint:
https://bridge.aiwerk.ch/u/<your-user-id>/mcpwith your Bearer token.
All 11 read-only tools appear. Install other AIWerk recipes from the same bridge.
Run directly — you manage the token:
WISE_API_TOKEN=xxx npx @aiwerk/mcp-server-wiseOr install globally:
npm install -g @aiwerk/mcp-server-wise
WISE_API_TOKEN=xxx mcp-server-wiseErrors surface as MCP isError: true responses with distinct prefixes:
Timeout: … — request exceeded WISE_API_TIMEOUT_MS (wraps AbortController)
Network error: … — fetch rejected (DNS, connection reset, etc.)
Configuration error: … — missing token or invalid base URL
Wise API error <status> … — HTTP 4xx/5xx response from Wise
wise_list_profiles → pick profileId
wise_list_balances({profileId}) → see available currencies / amounts
wise_get_exchange_rate({source, target}) → check rate
wise_list_transfers({profileId, status}) → history / status lookup
src/version.ts is generated from package.json by scripts/gen-version.mjs (runs as prebuild / predev / pretest). The file IS committed so a fresh clone compiles immediately.
The generator is idempotent: it only writes when the version actually changes. So npm run build on an in-sync tree leaves the working copy clean.
Bumping package.json's version and running any of build / dev / test is enough to propagate — no separate manual step on src/version.ts.
Part of the AIWerk MCP platform — curated, signed MCP recipes served either as npm packages for self-hosting or through our multi-tenant hosted bridge (bridge.aiwerk.ch).
Other AIWerk MCP servers:
@aiwerk/mcp-server-cal — Cal.com scheduling
@aiwerk/mcp-server-imap — IMAP/SMTP email, provider-agnostic
@aiwerk/mcp-server-clawhub — ClawHub skill catalog
Browse the full catalog (20+ recipes including GitHub, Linear, Notion, Stripe, …) at aiwerkmcp.com.
MIT © 2026 AIWerk
Get the required bank-account fields for creating a recipient in a given source→target currency + amount. Fields differ by country: USD routing number, EUR IBAN, GBP sort code, etc.
Inputs: source (required), target (required), sourceAmount (required).
Get a specific balance by ID (available amount, reserved amount, last updated).
Inputs: balanceId (required), profileId (required).
Get the current mid-market exchange rate between two currencies.
Inputs: source (required), target (required).
Get historical mid-market exchange rates between two currencies. group: day/hour/minute granularity.
Inputs: to (required), from (required), source (required), target (required), +1 more.
Get a profile by ID (name, type, address, KYC status).
Inputs: profileId (required).
Get a recipient account by ID (bank details, account holder, currency).
Inputs: accountId (required).
Get a specific transfer by ID (status, amounts, recipient, quote, timestamps).
Inputs: transferId (required).
List balance accounts for a profile. STANDARD = one per currency (the multi-currency account). SAVINGS = jars (user-named buckets). Default returns only STANDARD.
Inputs: profileId (required), types.
List all profiles (PERSONAL and BUSINESS) accessible with the token. ALWAYS call this first — most other tools need a profileId.
Inputs: no named parameters.
List recipient accounts for a profile. Filter by currency if you only want e.g. EUR beneficiaries.
Inputs: profileId (required), currency.
List transfers for a profile with optional filters. Use status to narrow: incoming_payment_waiting, processing, funds_converted, outgoing_payment_sent, bounced_back, cancelled, funds_refunded.
Inputs: profileId (required), limit, offset, status, +4 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 11 tools
Each tool targets a distinct resource and action (e.g., get vs list for balances, profiles, recipients, transfers), with clear separation between exchange rate and exchange rate history. No overlap in purpose.
All tools follow a consistent 'wise_' prefix and 'verb_noun' pattern in snake_case. Verbs are uniformly 'get' for single resources and 'list' for collections, providing predictable structure.
11 tools is within the typical 3-15 range and covers the core read operations for balances, rates, profiles, recipients, and transfers. However, the set feels slightly lean given the complexity of the Wise API.
The tool set is entirely read-only; there are no create, update, delete, or action operations (e.g., creating transfers, recipients, or initiating payments). This leaves significant gaps for any workflow involving writing data.
Wise (https://wise.com) MCP, multi-currency account access via Personal Token + SCA key. Reads profi
Read-only access to your bank, investment, and crypto accounts: balances, transactions, holdings.
Read-only access to your Finch finances: accounts, transactions, spending, net worth, goals.
Read-only: transactions, budgets, forecasts and insights from the PocketSmith personal finance tool.
