Skip to content

Submit MCP server: funraise-mcp #4521

Description

@sanjibani

Server name

sanjibani/funraise-mcp

Repository

https://github.com/sanjibani/funraise-mcp

Description

First MCP server for the Funraise nonprofit fundraising API - 32 tools across supporters, transactions (one-time donations), subscriptions (recurring gifts), campaign sites, forms, households, addresses, and interactions. Public REST API at https://api.funraise.io (v1 + v2) has had no first-party MCP server, no Zapier wrapper, no Composio toolkit, no viaSocket integration. Auth is a single X-Api-Key header (no OAuth dance, no token rotation). 71 tests via respx + hypothesis, ruff + mypy --strict clean, isError-compliance per the Blackwell MCP security audit pattern, JSONL audit logging per tool call with secret redaction (FUNRAISE_API_KEY + X-Api-Key header auto-redacted in the audit trail), typed exception hierarchy, application-level retry with exponential backoff honoring Retry-After, dispatch table for HTTP status -> exception. Used by mid-size to large nonprofits (4.46 stars on Capterra, 114 reviews). Real workflows this unlocks: 'log this cash gift from the Patel family - $500, for the Year End campaign', 'who are the top 5 new donors this month', 'send Sarah her 2025 giving summary', 'cancel this monthly subscription and email the donor a card-update link instead', 'merge these two duplicate household records'. Part of the same vertical-MCP portfolio as hawksoft, open-dental, ezyvet, jobber, practicepanther, cox-automotive, qualia, campspot, cleancloud, playmetrics, foreup, storedge, courtreserve, procare, passare.

Tools exposed

32

Connection info

  • Installation: see repo README
  • Transport: stdio (default)
  • Auth: env vars (FUNRAISE_API_KEY (required, the API key from Funraise > Settings > API Keys) + FUNRAISE_BASE_URL (optional, defaults to https://api.funraise.io) + FUNRAISE_AUDIT_LOG (optional JSONL audit log file path, defaults to stderr))

Self-check

  • Repository is public
  • README has install + usage instructions
  • Server has at least one tool
  • MIT-licensed

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions