Connect supported AI assistants and agentic tools to your Wise account with our Model Context Protocol server. The Wise MCP lets an assistant securely read selected Wise account information on your behalf, using your existing Wise login and permissions.
This MCP server allows you to connect your AI client to your Wise account. If you are looking for the MCP for Wise documentation, see our Wise Docs MCP guide
You can use Wise MCP to help an AI assistant:
- View the Wise profiles you have connected.
- Check balances and balance account details.
- Look up current exchange rates.
- Find out the cost of sending money with Wise.
- View recipients.
- Retrieve and filter transfer history.
Wise MCP currently has read-only access. You cannot use it to create or change recipients, move money, create/fund/cancel transfers, or make any other changes to a Wise account at this time. If an assistant asks to perform one of these actions, the MCP server will not offer a tool that can complete it. Use the Wise app or website for actions that change your account or move money.
At the moment, Wise MCP supports the following AI clients:
- Claude Code
- ChatGPT
- Codex CLI
We’re continuously working to expand this list, so do check back if your preferred provider is not included yet.
When you connect an AI assistant, it can request information from the Wise profiles and within the permissions you approve. This may include balances, transaction history and recipient information, including information about other people or businesses.
Wise controls access to your account through MCP and the information it makes available. The AI assistant is operated by a separate provider, which handles information it receives under its own terms and privacy policy. This includes how the information may be stored or used.
Only grant the permissions you need and review your AI provider's privacy practices before connecting. AI-generated answers may also be inaccurate, so consider reviewing important financial information directly in your Wise account.
Never share Wise passwords, one-time passcodes, or recovery codes with an AI assistant. A legitimate Wise Accounts MCP connection redirects you to a Wise-hosted page to sign in.
- A Wise account.
- Access to a supported MCP client that allows remote HTTP servers and OAuth.
- An eligible Wise profile with the information you want to access.
Your organisation or network administrator may restrict connections to external MCP servers. If the connection fails in a managed environment, ask your administrator whether the Wise MCP domain is allowed.
Use the following server URL in your MCP client: https://mcp.wise.com/mcp
Run this command in your terminal:
claude mcp add --transport http wise-mcp https://mcp.wise.com/mcpAfter adding the server, start your client's MCP authentication flow. The exact command or menu varies by client.
Wise MCP uses OAuth. You do not need to create or paste a personal API token into your AI client.
When you connect, your client opens a Wise-hosted sign-in and consent page.
- Sign in to Wise and complete any required authentication checks.
- Review the client requesting access.
- Select the eligible Wise profile(s) you want to connect.
- Choose the read permissions you want to grant.
- Confirm the connection.
The client receives access only to the profiles and read permissions you approve. Wise checks the client's access on every request.
The consent screen may offer permissions for:
| Permission | What the client can read | Scopes | Supported tools |
|---|---|---|---|
| Discovery and profiles | View your profiles and see which tools and permissions are available. | profiles:get, authorization:getPrivileges | wise_get_profile, wise_list_available_tools, wise_list_permissions |
| Balances | View your balances and multi-currency accounts. | borderlessAccounts:view | wise_list_multi_currency_accounts |
| Availability | View available currencies for balances and bank details. | borderlessAccounts:getAvailableCurrencies, borderlessAccounts:getPayinCurrencies | wise_list_available_balance_currencies, wise_list_topup_currencies |
| Recipients | View and list your recipients. | recipients:view | wise_get_recipient, wise_list_recipients |
| Transfers | View your transfer delivery estimates and payment details. | deliveryEstimates:get, transfers:view | wise_get_transfer_delivery_estimate, wise_list_transfer_payments |
| Transactions | View your account transactions and activity. | activities:list | wise_list_activities |
| Exchange rates and fees | View exchange rates, fees and quotes. | quotes:create, quotes:get | wise_create_quote, wise_get_existing_quote |
Read-only access can still expose sensitive financial and personal information in the assistant's conversation or logs. Review your AI provider's data-handling and retention terms before connecting it to Wise.
You can stop a client from accessing Wise by revoking its OAuth session.
To log out:
$ claude mcp logout wise-mcpTo revoke tokens:
Use /mcp inside Claude Code interactively and choose Clear authentication.
To remove Wise MCP server completely:
$ claude mcp remove wise-mcpThis will delete the local server entry and stored tokens. Note that Wise MCP uses OAuth, which means you should run claude mcp logout first.
To manage tool permissions:
Run /permissions inside Claude Code to view, adjust, or block Wise MCP tool rules.
After access is revoked, the client can no longer use the associated Wise permissions. To reconnect it, repeat the OAuth consent flow.
If you need to change the profiles or permissions granted to a client, revoke the existing connection and connect it again with the new selection.
- Wise-hosted authentication: You sign in and grant access on a Wise-controlled page, not inside the AI client.
- OAuth with PKCE: The connection uses the OAuth authorization-code flow with Proof Key for Code Exchange, designed for public clients that cannot safely store a secret.
- Profile-level consent: You choose which eligible Wise profiles to connect.
- Permission-level consent: You choose which categories of information the client can read.
- Per-request authorization: Wise validates access for the user, profile, and client on every request.
- Revocation: Revoking the OAuth session removes the client's associated access grants.
- Read-only enforcement: The launch server exposes only tools backed by read-only API operations.
Never share Wise passwords, one-time passcodes, or recovery codes with an AI assistant. A legitimate Wise MCP connection redirects you to a Wise-hosted page to sign in.
Wise MCP exposes the following read-only tools at launch. The tools visible in a client and the results they can return depend on the permissions granted for the selected profile.
Discovery and profiles:
| Tool | Description | Required permission |
|---|---|---|
wise_list_profiles | List the personal and business profiles the signed-in user can access, including profiles shared with them. | None |
wise_get_profile | Retrieve one Wise profile by ID. | profiles:get |
wise_list_available_tools | List the tools available for a profile with the current connection, and the missing permission for each unavailable tool. | authorization:getPrivileges |
wise_list_permissions | Return the permissions granted for a profile. | authorization:getPrivileges |
Exchange rates and quotes:
| Tool | Description | Required permission |
|---|---|---|
wise_get_exchange_rate | Get the current mid-market exchange rate for a currency pair. | None |
wise_create_quote | Get the current rate, fees, and delivery estimate for each payment option when sending money between two currencies. | quotes:create |
wise_get_existing_quote | Retrieve an existing quote by ID. | quotes:get |
Balances:
| Tool | Description | Required permission |
|---|---|---|
wise_list_multi_currency_accounts | List balance accounts and their balances for a profile, optionally filtered by account type. | borderlessAccounts:view |
wise_list_available_balance_currencies | List the currencies a profile can hold a balance in. | borderlessAccounts:getAvailableCurrencies |
wise_list_topup_currencies | List the currencies a profile can add money in. | borderlessAccounts:getPayinCurrencies |
Recipients:
| Tool | Description | Required permission |
|---|---|---|
wise_get_recipient | Retrieve one recipient account by ID. | recipients:view |
wise_list_recipients | List active recipient accounts for a profile, optionally filtered by currency. | recipients:view |
Activities and transfers:
| Tool | Description | Required permission |
|---|---|---|
wise_list_activities | List account activity for a profile, such as transfers, card payments, deposits, and conversions, with optional status, type, and date filters. | activities:list |
wise_get_transfer_delivery_estimate | Get the estimated delivery date for a transfer. | deliveryEstimates:get |
wise_list_transfer_payments | List the completed payments used to pay for a transfer. | transfers:view |
| Problem | Cause & solution |
|---|---|
| The client asks to authenticate again. | Your access token may have expired, the session may have been revoked, or the client's permissions may have changed. Start the client's Wise authentication flow again. |
| A tool is listed but access is denied. | The connection may not have the required permission for that profile. Use wise_list_permissions or wise_list_available_tools to check the current access. If necessary, revoke the connection and reconnect with the required read permission. |
| A profile is missing. | Only eligible profiles available to the signed-in user can be connected. Confirm that you signed in to the correct Wise account and that you have the required relationship to the profile. |
| The MCP server does not connect. | Check that:
|
| The assistant returns more data than expected. | Stop using the MCP. Revoke its Wise OAuth session within the client based on the steps included in the Managing access section of this guide. |