Is this an official Wise MCP server?

No. It is Memtro's MCP server with Memtro's Wise connector behind it: the connector reads Wise through its API with the credentials you connect on Dashboard → Connections, and Wise publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Wise?

Not yet. Today every Wise tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Finance and commerce

Wise MCP server

Wise in any MCP client, through Memtro: Wise does not publish this server. Memtro's Wise connector reads Wise through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Your Wise business account, read-only: multi-currency balances and total funds, the activity feed of transfers, card payments, deposits and conversions, transfer details, recipients, exchange rates and balance statements.

Reads

wise_balancesBalances per currency (standard accounts and savings jars) with reserved amounts…
wise_activitiesThe account's activity feed newest first: transfers sent and received, card payments, deposits, conversions, fees and rewards…
wise_transferOne transfer by id: status, amounts and currencies, rate, reference, when it was created, and the recipient it went to.
wise_recipientsSaved recipients (payees): name, currency, country, type and Wise's masked account summary.
wise_statementBalance statement for one currency over a window (default the last 30 days, at most 469 days): each transaction with direction, amount, fees…
wise_ratesWise's exchange rate for a currency pair: current, at a past time, or a history with daily/hourly points over a window.
wise_profilesThe Wise profiles this token can see (business and personal) and which one the connection uses.

Connect it

First connect Wise on Dashboard → Connections, then add Memtro to your client once. The Wise tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Wise connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› What are our Wise balances right now, and the total in GBP?
› Which transfers went out this week and to whom?
› Did the EUR payment to Hotel Riga complete?
› What is the GBP to EUR rate today compared with a month ago?
› Show the GBP statement for September with running balances

Questions

Is this an official Wise MCP server?: No. It is Memtro's MCP server with Memtro's Wise connector behind it: the connector reads Wise through its API with the credentials you connect on Dashboard → Connections, and Wise publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Wise?: Not yet. Today every Wise tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.