Bring Donation Tracking
to Claude Desktop
Learn how to connect FundraisingBox to Claude Desktop and start using 14 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the FundraisingBox MCP Server?
Connect your FundraisingBox account to any AI agent and manage your nonprofit fundraising operations through natural conversation.
What you can do
- Donation Tracking — List all donations with amounts, donors, campaigns, and payment methods, and filter by campaign
- Recurring Donations — Monitor all active recurring donation subscriptions with frequency and status
- Donor Management — Browse all donors with contact info, total donated, and donation count; search by name or email
- Donor History — Retrieve complete giving history for any donor including amounts, dates, and campaign allocations
- Campaign Monitoring — List all fundraising campaigns with goals, progress, and donation statistics
- Donation Forms — View all configured donation form widgets
- Tax Receipts — Access all generated donation receipts for fiscal reporting
- Dashboard Analytics — Retrieve aggregate fundraising metrics: total raised, donor count, campaign performance, and trends
How it works
1. Subscribe to this server
2. Enter your FundraisingBox API Key from your organization settings
3. Start managing your fundraising from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Fundraising Managers — track donation trends, monitor campaign progress, and review donor engagement without opening the dashboard
- Donor Relations — search donors, review giving histories, and prepare personalized outreach
- Finance Teams — access donation receipts and reconcile fundraising data for annual reporting
Built-in capabilities (14)
Verify connectivity
Get campaign details
Get fundraising dashboard
Get donation details
Get donor profile
Get donor history
List campaigns
List donations
List donations by campaign
List donors
List donation forms
List donation receipts
List recurring donations
Search donors
Why Claude Desktop?
Claude Desktop is the definitive way to connect FundraisingBox to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 14 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
FundraisingBox in Claude Desktop
FundraisingBox and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect FundraisingBox to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for FundraisingBox in Claude Desktop
The FundraisingBox MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 14 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
FundraisingBox for Claude Desktop
Every tool call from Claude Desktop to the FundraisingBox MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see the full donation history for a specific donor?
Yes. Use search_donors to find a donor by name or email, then call get_donor_history with their Donor ID to retrieve every donation they've made — including amounts, dates, campaign allocations, and payment methods. Use get_donor for their full profile with contact details and total lifetime giving.
Can I monitor campaign progress toward fundraising goals?
Yes. The list_campaigns tool retrieves all fundraising campaigns with their goals and current progress. Use get_campaign with a Campaign ID for detailed statistics including donor count, average donation, and progress percentage. Combine with list_donations_by_project to see every donation linked to a specific campaign.
Can I access donation tax receipts for annual fiscal reporting?
Yes. The list_receipts tool retrieves all generated donation tax receipts across your organization. Each receipt includes the donor name, donation amount, date, and receipt number. Use get_dashboard for aggregate fundraising metrics to supplement your annual reporting.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.