@mindstone/mcp-server-wise

Wise (formerly TransferWise) MCP server for Model Context Protocol hosts. Check multi-currency balances and exchange rates, review transactions and activity, manage recipients, price transfers with quotes โ and create, fund, and cancel transfers, with your host app's tool approval deciding when to ask you first โ all through a standardised MCP interface.
Status
- Version: 0.1.1 ยท npm
- Auth: API token (env var, or on disk via
WISE_CONFIG_PATH)
- Tools: 17 (accounts, balances, recipients, quotes, transfers, discovery)
- Surface: cloud-api
- Machine-readable:
STATUS.json
Requirements
- Node.js 20+
- npm
- A Wise API token: wise.com โ Settings โ API tokens
One-click install

After clicking the button, your host will prompt you to fill: WISE_API_TOKEN.
Manual config for Claude Desktop / Claude Code / Goose / Continue.dev (Wise)
{
"mcpServers": {
"Wise": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-wise"
],
"env": {
"WISE_API_TOKEN": ""
}
}
}
}
Quick Start
Install & build
cd <path-to-repo>/connectors/wise
npm install
npm run build
npx (once published)
npx -y @mindstone/mcp-server-wise
Local
Configuration
Environment variables
WISE_API_TOKEN โ Wise API token. Optional if you connect via the configure_wise tool instead; when set, it takes precedence over any stored token.
WISE_ENVIRONMENT โ production (default) or sandbox. Sandbox is Wise's test environment, with no real money, and requires a token created in the Wise sandbox.
WISE_CONFIG_PATH โ path to the config directory that stores the token written by configure_wise (defaults to ~/.mcp/wise).
WISE_REQUEST_TIMEOUT_MS โ outbound request timeout in milliseconds (default 30000).
MCP_HOST_BRIDGE_STATE โ optional path to a host bridge state file. The host bridge is a local connection to the host app on this computer; when it is set, configure_wise hands the token to the host app to save, instead of writing credentials.json itself.
MINDSTONE_REBEL_BRIDGE_STATE โ backwards-compatible alias for MCP_HOST_BRIDGE_STATE.
Host configuration examples
Claude Desktop / Cursor
{
"mcpServers": {
"Wise": {
"command": "npx",
"args": ["-y", "@mindstone/mcp-server-wise"],
"env": {
"WISE_API_TOKEN": "your-wise-api-token"
}
}
}
}
Local development (no npm publish needed)
{
"mcpServers": {
"Wise": {
"command": "node",
"args": ["<path-to-repo>/connectors/wise/dist/index.js"],
"env": {
"WISE_API_TOKEN": "your-wise-api-token"
}
}
}
}
Account management
configure_wise โ Connect a Wise account with an API token (verified against the Wise API before storing)
remove_wise_account โ Disconnect the Wise account
Profiles & balances
list_wise_profiles โ List personal and business profiles accessible with the token; use the ids as profile_id
list_wise_balances โ List balances (multi-currency accounts and savings jars) with amounts per currency
get_wise_balance_statement โ Transaction statement for one balance over a time window (max 469 days)
list_wise_activities โ Chronological activity feed (transfers, card payments, deposits) with status
Exchange rates & quotes
get_wise_exchange_rate โ Current or historic mid-market rate between two currencies
create_wise_quote โ Lock a rate and get exact fees per funding method (does not move money)
Recipients
list_wise_recipients โ List saved recipients (bank accounts), filterable by currency or type
get_wise_recipient โ Full details of one recipient, including bank details
get_wise_recipient_requirements โ Discover the bank detail fields Wise requires for a route, given a quote
create_wise_recipient โ Create a saved recipient (does not move money)
Transfers
list_wise_transfers โ List transfers with filters (status, currencies, created-date window)
get_wise_transfer โ Current state of one transfer
create_wise_transfer โ Create a transfer from a quote to a recipient (not funded yet)
fund_wise_transfer โ Fund a created transfer from a Wise balance (moves money)
cancel_wise_transfer โ Cancel a transfer before the funds_converted stage
Typical payout flow
list_wise_profiles โ pick a profile_id
create_wise_quote โ price the transfer and lock a rate
- (New recipient)
get_wise_recipient_requirements โ create_wise_recipient
create_wise_transfer โ creates the transfer (not funded yet)
fund_wise_transfer โ pays from a Wise balance; this is the step that moves money
Security
- Money-moving tools are on by default.
create_wise_transfer, fund_wise_transfer, and cancel_wise_transfer are always available and declare destructiveHint: true โ gating of individual invocations is the host's tool-approval layer's job, not the connector's. A host with no approval step runs them whenever the model calls them. Quote and recipient creation never move money; only fund_wise_transfer debits a balance.
- Untrusted-content envelopes. Strings authored by external parties (recipient names and bank details, transfer references, statement descriptions and merchant names, activity titles, quote notices and their links) are wrapped in
<untrusted-content source="โฆ"> envelopes so the host LLM treats them as data, not instructions. Exchange-rate strings and the funding reply (type, status, errorCode) are enveloped too.
- What is not enveloped. Records are passed through with their other fields raw, and that includes any field the connector does not know about, because the record is copied as a whole and only the named fields are enveloped. The funding reply is the exception: only its three checked fields are returned, each enveloped, and the rest is dropped. In exchange rates only the values are enveloped; the object keys are kept as Wise sent them. Recipient-list pagination returns
seekPositionForNext raw. The connector's own message text quotes a Wise value only after a type check: an id only when it is a number, a count only from a checked list, and never a status string. The activities cursor is returned raw so it can be passed back; it is accepted only if it uses an opaque-token alphabet (letters, digits and _-=.:%+, at most 512 characters), and otherwise pagination stops. That check limits which characters a cursor can contain; it does not prove the cursor came from Wise.
- Response checks. Replies the connector acts on are checked before use: the profile list used for auto-selection (the chosen id must be a positive integer before it goes into a URL), the token check's profile list, the recipient requirements list (whose length becomes
count), and the funding reply. A reply of the wrong shape gives a fixed error instead of a guess. A funding reply that cannot be read says the transfer may or may not be funded, so check it with get_wise_transfer or in your Wise account before retrying. A funding rejection suggests topping up only when Wise says the balance is short; any other rejection says to check the transfer before trying again. When a write (any request other than a read) gets a success status but a reply that cannot be read, the error says Wise may have acted on it, so check before trying again.
- Credential storage. Tokens written by
configure_wise are stored in credentials.json under WISE_CONFIG_PATH with 0600 permissions (config directory 0700). The file is written to a temporary file and renamed into place. If a save fails before the new file replaces the old one, the old credentials are kept; if it fails after that (while setting permissions or flushing the folder), the new credentials may already be in place. Either way configure_wise reports SAVE_FAILED. A symbolic link at the credentials path is refused for both reading and writing. Each token is sent only to the Wise host of the environment it was saved for, and only the two fixed Wise hosts (api.wise.com, api.wise-sandbox.com) are ever contacted โ there is no arbitrary base-URL override, and a Wise reply that redirects is refused rather than followed.
- Host bridge. The bridge state file is checked before it is trusted (a regular file, not a symbolic link or pipe, of bounded size, with a valid port; the bridge is only ever reached on
127.0.0.1), and a bridge reply that redirects is refused, so the bridge token (the secret the host app writes into the state file) and a Wise token sent to the bridge stay on loopback.
- Error hygiene. Vendor error bodies, raw
Retry-After header text, and query-bearing URLs are never written to logs or surfaced in tool errors; tokens never appear in error messages. Unexpected failures return fixed text, and the log records only an error code.
- Idempotent transfer creation.
create_wise_transfer uses customer_transaction_id as the Wise idempotency key, so a retry never creates a duplicate transfer.
- Input validation. Currency codes, numeric ids, UUIDs, and date-time windows are validated before any request is made.
Licence
FSL-1.1-MIT โ Functional Source License, Version 1.1, with MIT future licence. The software converts to MIT licence on 2030-04-08.