Is this an official Mercury MCP server?

No. It is Memtro's MCP server with Memtro's Mercury connector behind it: the connector reads Mercury through its API with the credentials you connect on Dashboard → Connections, and Mercury 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 Mercury?

Not yet. Today every Mercury 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

Mercury MCP server

Mercury in any MCP client, through Memtro: Mercury does not publish this server. Memtro's Mercury connector reads Mercury 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

Read-only Mercury business banking: accounts and balances, transactions by date, account, counterparty or text, payment recipients, the organisation's users and receivable invoices.

Reads

mercury_get_organizationThe Mercury organisation this connection reads: legal business name, trading names, kind and plan.
mercury_list_accountsBank accounts in Mercury (checking, savings, treasury) with status and available and current balances.
mercury_list_transactionsTransactions, newest first: amount as Mercury reports it, status (pending, sent, failed and so on), counterparty, bank description, note…
mercury_list_recipientsPayment recipients (the people and firms the business pays): name, nickname, status, emails, default payment method and when they were last paid.
mercury_list_usersPeople with access to the Mercury organisation: name, email and role.
mercury_list_invoicesReceivable invoices raised in Mercury, newest first: number, customer id, status (Unpaid, Paid, Cancelled, Processing), amount and currency…

Connect it

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

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=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-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

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 Mercury 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 is our balance across all Mercury accounts?
› What did we pay Northwind last month?
› Which invoices are still unpaid, and when were they due?
› What came in last week?
› Who has access to the bank account?

Questions

Is this an official Mercury MCP server?: No. It is Memtro's MCP server with Memtro's Mercury connector behind it: the connector reads Mercury through its API with the credentials you connect on Dashboard → Connections, and Mercury 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 Mercury?: Not yet. Today every Mercury 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.