Is this an official Donorbox MCP server?

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

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

Donorbox MCP server

Donorbox in any MCP client, through Memtro: Donorbox does not publish this server. Memtro's Donorbox connector reads Donorbox 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 Donorbox fundraising: donations with amount, campaign, date, status and donor (anonymous donors unnamed), donors by name or email with their giving, and campaigns with goal and amount raised.

Reads

donorbox_list_donationsDonorbox donations, newest first by default: amount and currency, campaign, date, status, refunded amount, recurring or one-off…
donorbox_list_donorsDonorbox donors by name or email: each donor's name, email, number of donations, last donation date and total given per currency.
donorbox_list_campaignsDonorbox campaigns: name, currency, goal, amount raised and number of donations.

Connect it

First connect Donorbox on Dashboard → Connections, then add Memtro to your client once. The Donorbox 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 Donorbox 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

› How much has the winter appeal raised this month?
› Which donations were refunded last quarter?
› How much has Sarah Chen given in total, and when did she last donate?
› Which campaigns are furthest from their goal?
› Which recurring donations came in for the spring campaign last week?

Questions

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