Wise MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MODE | No | MCP Server transport mode, either 'http' or 'stdio' | stdio |
| WISE_API_TOKEN | Yes | Your Wise API token (required) | |
| WISE_IS_SANDBOX | No | Set to true to use the Wise Sandbox API | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| get_recipient_requirementsA | Fetches recipient requirements for creating a new recipient. If account details are provided, validates the account details against the requirements. |
| create_recipientC | Creates a new recipient with the provided account details. |
| send_moneyB | Send money to a recipient using the Wise API. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: creating recipients, fetching requirements, listing recipients, and sending money. No overlap.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_recipient, list_recipients, get_recipient_requirements, send_money).
With 4 tools, the server is well-scoped for a focused Wise integration covering recipient management and money transfer.
Covers key recipient and transfer operations, but lacks a direct get_recipient by ID or update/delete recipient, which are minor gaps.