Skip to main content
Glama
Wise MCP Server
by rkm7448

Wise MCP Server

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

Features

  • 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

Related MCP server: poke-bank

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)

Get an API token

https://wise.com/your-account/integrations-and-tools/api-tokens

Create a new token here.

Installation

Option 1: Direct Installation

  1. Clone this repository:

    git clone repo-url
    cd jc-wise-mcp
  2. Set up the environment:

    cp .env.example .env
    # Edit .env to add your Wise API token
  3. Install dependencies with uv:

    uv venv
    uv pip install -e .

Option 2: Using Docker

You can build a Docker image:

docker build -t mcp-wise .

And add to Claude Code by adding it to your .mcp.json

{
  "mcpServers": {
    "mcp-wise": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "--init",
        "-e", "WISE_API_TOKEN=your_api_token_here",
        "-e", "WISE_IS_SANDBOX=true",
        "mcp-wise:latest"
      ]
    }
  }
}

Make sure to replace your_api_token_here with your actual Wise API token.

Make sure to also update your .mcp.json file to match your selected mode. We provide template files that you can use:

  1. For stdio mode (default):

    cp .mcp.json.stdio .mcp.json
  2. For HTTP mode:

    cp .mcp.json.http .mcp.json

These template files contain the appropriate configuration for each mode.

Available MCP Resources

The server provides the following MCP resources:

list_recipients

Returns a list of all recipients from your Wise account.

Parameters:

  • profile_type: The type of profile to list recipients for. One of [personal, business]. Default: "personal"

  • currency: Optional. Filter recipients by currency code (e.g., 'EUR', 'USD')

get_recipient_requirements

Fetches recipient requirements for creating a new recipient. If account details are provided, validates the account details against the requirements.

Parameters:

  • source_currency: The source currency code (e.g., 'USD')

  • target_currency: The target currency code (e.g., 'EUR')

  • source_amount: The amount in the source currency

  • profile_type: The type of profile to use. One of [personal, business]. Default: "personal"

  • account: Optional. The recipient account details to validate against requirements. If not provided, returns the initial account requirements.

create_recipient

Creates a new recipient with the provided account details.

Parameters:

  • profile_type: The type of profile to use. One of [personal, business]. Default: "personal"

  • account: The recipient account details compliant with Wise API requirements. This should include:

    • accountHolderName: Name of the account holder

    • currency: Target currency code (e.g., 'EUR')

    • type: Account type (e.g., 'iban', 'sort_code', etc.)

    • details: Object containing account-specific details (varies by currency and country)

send_money

Sends money to a recipient using the Wise API.

Parameters:

  • profile_type: The type of profile to use (personal or business)

  • source_currency: Source currency code (e.g., 'USD')

  • source_amount: Amount in source currency to send

  • recipient_id: The ID of the recipient to send money to

  • payment_reference: Optional. Reference message for the transfer (defaults to "money")

  • source_of_funds: Optional. Source of the funds (e.g., "salary", "savings")

Configuration

Configuration is done via environment variables, which can be set in the .env file:

  • WISE_API_TOKEN: Your Wise API token (required)

  • WISE_IS_SANDBOX: Set to true to use the Wise Sandbox API (default: false)

  • MODE: MCP Server transport mode, either "http" or "stdio" (default: stdio)

Development

Project Structure

wise-mcp/
├── .env                # Environment variables (not in git)
├── .env.example        # Example environment variables
├── pyproject.toml      # Project dependencies and configuration
├── README.md           # This file
└── src/                # Source code
    ├── main.py         # Entry point
    └── wise_mcp/       # Main package
        ├── api/        # API clients
        │   └── wise_client.py # Wise API client
        ├── resources/  # MCP resources
        │   └── recipients.py  # Recipients resource
        └── app.py      # MCP application setup

Adding New Features

To add new features:

  1. Add new API client methods in src/wise_mcp/api/wise_client.py

  2. Create new resources in src/wise_mcp/resources/

  3. Import and register the new resources in src/wise_mcp/app.py

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

MIT

Available Tools

4 tools
create_recipientC

Creates a new recipient with the provided account details.

Inputs: recipient_fullname (required), currency (required), recipient_type (required), profile_type, +1 more. Returns: result

get_recipient_requirementsA

Fetches recipient requirements for creating a new recipient. If account details are provided, validates the account details against the requirements.

Inputs: source_currency, target_currency, source_amount, profile_type, +1 more. Returns: object

list_recipientsA

Returns all recipients from the Wise API for the given profile type of current user. If a user has multiple profiles of that type, it will return recipients from the first profile.

Inputs: profile_type, currency. Returns: result

send_moneyB

Send money to a recipient using the Wise API.

Inputs: profile_type (required), source_currency (required), source_amount (required), recipient_id (required), +2 more. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: creating recipients, fetching requirements, listing recipients, and sending money. No overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_recipient, list_recipients, get_recipient_requirements, send_money).

    Tool Count5/5

    With 4 tools, the server is well-scoped for a focused Wise integration covering recipient management and money transfer.

    Completeness4/5

    Covers key recipient and transfer operations, but lacks a direct get_recipient by ID or update/delete recipient, which are minor gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables access to Wise API functionality for managing recipients and sending money transfers. Supports listing recipients, creating new recipients, validating account details, and executing money transfers with authentication handling.
      10
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that exposes Enable Banking API tools for interacting with bank accounts through Open Banking. It enables users to authenticate sessions, list accounts, and fetch transaction history or balances via a secure self-hosted server.
      2
      -
    • A
      license
      A
      quality
      D
      maintenance
      A custom MCP server for the Mercury banking API that uses personal API tokens to avoid session expiry. It provides 15 tools for managing accounts, transactions, recipients, treasury, and more.
      15
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for ZEN.com Payment Gateway enabling payment links, transaction lookup, refunds, payouts, and reporting.
      14
      41 npm
      MIT