Bring Double The Donation
to CrewAI
Learn how to connect Double the Donation to CrewAI and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Double the Donation MCP Server?
Connect your Double the Donation (360MatchPro) account to any AI agent and take full control of your nonprofit matching gift automation and corporate giving workflows through natural conversation.
What you can do
- Employer Orchestration — Search an extensive database of over 24,000 employers programmatically to find specific matching gift opportunities and guidelines
- Donation Life-cycle — Programmatically register new donations and automatically identify matching gift eligibility to maximize your fundraising revenue
- Supporter Tracking — Access complete status reports for individual donations and monitor the matching gift journey from donor action to payment completion
- Account Management — Programmatically provision and manage 360MatchPro accounts for nonprofit clients to streamline your partnership operations
- Strategic Visibility — Access high-level dashboard statistics and account settings directly through your agent for instant performance reporting
How it works
1. Subscribe to this server
2. Retrieve your Public and Private API Keys from your 360MatchPro dashboard (Settings > API Keys)
3. Start capturing unclaimed matching gift revenue from Claude, Cursor, or any MCP client
No more manual employer lookups or missing out on corporate gift matches. Your AI acts as your dedicated matching gift coordinator and fundraising strategist.
Who is this for?
- Nonprofit Development Teams — instantly verify employer matching programs and register gifts using natural language commands
- Fundraising Operations — monitor donation status across your entire portfolio and track payment completion without leaving your workspace
- Software Providers — automate the provisioning of 360MatchPro accounts for your nonprofit clients through simple AI queries
Built-in capabilities (12)
Provision a new 360MatchPro account
Get account settings
Get company matching gift details
Get dashboard statistics
Get donation details
Get organization details
List campaigns
List donations
List company subsidiaries
Register a new donation
Search for a company by name
Update organization details
Why CrewAI?
When paired with CrewAI, Double the Donation becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Double the Donation 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
Double the Donation in CrewAI
Double the Donation and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Double the Donation 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 Double the Donation in CrewAI
The Double the Donation 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 12 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
Double the Donation for CrewAI
Every tool call from CrewAI to the Double the Donation MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Public and Private API Keys?
Log in to your 360MatchPro dashboard, navigate to Settings > API Keys, and copy both your Public and Private access tokens.
Can I search for any employer in the database?
Yes! The search_company tool allows you to query a database of over 24,000 employers to find matching gift opportunities programmatically.
Does it support real-time donation status updates?
The get_donation tool retrieves the most current status and history for any registered donation ID directly from the 360MatchPro platform.
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.