Givebutter logoMCP server · CRM and sales

Givebutter MCP server

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

Givebutter fundraising: campaigns with goal, raised and donor counts, gifts with amount, date, campaign and status, contacts by name or email, and a campaign's fundraising members; can create, edit and delete contacts, add or remove their tags and notes, record and edit offline gifts, create, edit, publish and delete campaigns, add event tickets, remove a fundraiser, and create funds and households.

Reads

  • givebutter_campaignsGivebutter campaigns (fundraising pages, events, forms): title, type, status, goal, amount raised, donor count, currency, link and end date.
  • givebutter_transactionsGivebutter gifts, newest first by default: amount, currency, date, campaign and status, with the contact id.
  • givebutter_contactsGivebutter contacts (donors and supporters) by email, first or last name, or tag: id, type, name and email only.
  • givebutter_membersThe fundraising members of one Givebutter campaign (peer-to-peer fundraisers): name, amount raised, goal, donor count and page link.

Acts, when you ask

These change something in Givebutter. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

  • givebutter_add_contact_noteAdds a note to a Givebutter contact's activity timeline.
  • givebutter_add_contact_tagsAdds tags to a Givebutter contact, keeping the tags it already has; a tag that does not exist yet is created.
  • givebutter_remove_contact_tagsRemoves the named tags from one Givebutter contact; its other tags stay.
  • givebutter_create_contactCreates a contact (a donor or supporter) in Givebutter, visible to everyone on the account.
  • givebutter_update_contactEdits one Givebutter contact: names, title, employer, the contact's note, external id, email/SMS/mail opt-ins…
  • givebutter_delete_contactDeletes one Givebutter contact.
  • givebutter_delete_contact_activityPermanently deletes one note or activity from a Givebutter contact's timeline.
  • givebutter_record_transactionRecords an offline gift (cheque, cash, stock, in-kind and the like) in Givebutter against a contact and campaign.
  • givebutter_update_transactionEdits one Givebutter gift: internal note, cheque number and deposit date, fund, campaign, appeal, payment method or date.
  • givebutter_create_campaignCreates a Givebutter campaign: a general donation page, collect form, peer-to-peer fundraiser or event.
  • givebutter_update_campaignEdits a Givebutter campaign, or publishes or unpublishes it.
  • givebutter_delete_campaignPermanently deletes a Givebutter campaign and its page.
  • givebutter_remove_campaign_memberRemoves one fundraiser (member) from a Givebutter campaign; their fundraising page comes down.
  • givebutter_create_campaign_ticketAdds a ticket type to a Givebutter event campaign.
  • givebutter_create_fundCreates a fund (a designation donors can give to) in Givebutter.
  • givebutter_create_householdCreates a household in Givebutter to group related contacts, optionally with a head contact.

Connect it

First connect Givebutter on Dashboard → Connections, then add Memtro to your client once. The Givebutter 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 Givebutter 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 against its goal?
  • › Who are the top fundraisers on the gala page?
  • › What did we raise last month, by currency?
  • › Tag Dan Fletcher as a gala volunteer.
  • › Record a £100 cash gift from Sarah Chen to the Winter Appeal, dated yesterday.

Questions

Is this an official Givebutter MCP server?
No. It is Memtro's MCP server with Memtro's Givebutter connector behind it: the connector reads Givebutter through its API with the credentials you connect on Dashboard → Connections, and Givebutter 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 Givebutter?
Only when you ask, and only what it has been granted: add a note to a contact's activity; add tags to a contact; remove tags from a contact; create a contact (matches an existing one by email or phone unless forced); edit a contact's name, details, notes or opt-ins; delete a contact (restorable in Givebutter); delete a note or activity from a contact (permanent); record an offline gift (cheque, cash and the like) against a campaign and contact; edit an offline gift's note, cheque number, fund, campaign, method or date; create a campaign; edit, publish or unpublish a campaign; delete a campaign that has raised nothing (permanent); remove a fundraiser from a campaign (permanent); add a ticket type to an event campaign; create a fund; create a household. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
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.

Other MCP servers · CRM and sales

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time