Bring Donation Tracking
to Cursor
Learn how to connect FundraisingBox to Cursor 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 Cursor?
Cursor's Agent mode turns FundraisingBox into an in-editor superpower. Ask Cursor to generate code using live data from FundraisingBox and it fetches, processes, and writes. all in a single agentic loop. 14 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
FundraisingBox in Cursor
FundraisingBox and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect FundraisingBox to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.