MCP Wise MCP Server

If you want an AI assistant working directly with MCP Wise, the mcp wise mcp server is the bridge. A MCP (Machine Communication Protocol) server that serves as a gateway for the Wise API, providing simplified access to Wise's recipient functionality.

What MCP Wise does

A MCP (Machine Communication Protocol) server that serves as a gateway for the Wise API, providing simplified access to Wise's recipient functionality.

Key capabilities

• List all recipients from your Wise account via a simple MCP resource
• Automatically handles authentication and profile selection
• Uses the Wise Sandbox API for development and testing
• Available as a Docker image for easy integration

Tools it exposes

Once connected, the assistant can call these 4 tools directly:

• list_recipients — The list_recipients tool exposed by this server
• get_recipient_requirements — Fetches recipient requirements for creating a new recipient. If account details are provided, validates the account details against the requirements
• create_recipient — The create_recipient tool exposed by this server
• send_money — The send_money tool exposed by this server

Installing the mcp wise mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply one environment variable: WISE_API_TOKEN. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

• Python 3.12 or higher (only if installing directly) - uv package manager (only if installing directly) - Wise API token - Docker (if using Docker image)

Where it fits

Cloud and DevOps servers put infrastructure on speaking terms with your assistant, so "why is this broken?" is answered from real state rather than a generic checklist. MCP Wise sits in that group, and the shape of its toolset — list_recipients, get_recipient_requirements, create_recipient among others — tells you what it is really for. Worth comparing against the other cloud devops servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• Maintained by sergeiledvanov, written in Python.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the mcp wise mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.