Bring Donation Tracking
to CrewAI
Learn how to connect FundraisingBox to CrewAI 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 CrewAI?
When paired with CrewAI, FundraisingBox becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call FundraisingBox tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
FundraisingBox in CrewAI
FundraisingBox and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect FundraisingBox to CrewAI 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 CrewAI
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 CrewAI 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 CrewAI
Every tool call from CrewAI 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 CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.