Bring Every Org
to CrewAI
Learn how to connect Every.org 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 Every.org MCP Server?
Connect your Every.org account to any AI agent and take full control of your philanthropic discovery and fundraising workflows through natural conversation.
What you can do
- Nonprofit Orchestration — Search across over 1.5 million registered 501(c)(3) nonprofits programmatically using keywords and location filters
- Cause Intelligence — Browse and filter nonprofits by specific causes such as climate, education, or animal welfare to maintain high-fidelity social impact
- Fundraising Automation — Programmatically create and manage fundraisers for your favorite nonprofits directly through your agent (Requires Private Key)
- Deep Metadata Retrieval — Access detailed information for specific nonprofits, including descriptions, EINs, and direct donation links
- Philanthropic Visibility — Monitor your active fundraisers and retrieve engagement metadata programmatically using natural language commands
How it works
1. Subscribe to this server
2. Retrieve your Public API Key (and optional Private Key) from the Every.org API Dashboard
3. Start discovering nonprofits and managing fundraisers from Claude, Cursor, or any MCP client
No more manual searching through fragmented charity databases. Your AI acts as your dedicated philanthropic coordinator and social impact analyst.
Who is this for?
- Social Impact Teams — instantly identify relevant nonprofits for corporate social responsibility (CSR) initiatives using natural language
- Fundraisers & Philanthropists — automate the creation of fundraising campaigns and monitor engagement without leaving your workspace
- Developers — integrate high-quality nonprofit data and donation links into custom internal tools and social platforms
Built-in capabilities (12)
Browse by cause
Browse causes
Verify connectivity
Create a donation
Create a fundraiser
Get featured nonprofits
Get fundraiser details
Get nonprofit details
Get nonprofit by EIN
List donations
List fundraisers
Search nonprofits
Why CrewAI?
When paired with CrewAI, Every.org becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Every.org 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
Every.org in CrewAI
Every.org and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Every.org 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 Every.org in CrewAI
The Every.org 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
Every.org for CrewAI
Every tool call from CrewAI to the Every.org 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 get an API Key for Every.org?
Visit the Every.org API Dashboard to request your free Public Key. For fundraising features, you will also need a Partner account and Private Key.
Can I search for nonprofits in a specific location?
Yes! The search_nonprofits tool accepts keywords that can include cities or regions to narrow your search for local organizations.
How do I create a new fundraiser programmatically?
Use the create_fundraiser tool by providing the nonprofit_id (EIN or slug) and a title. Note that this requires a Private Key configured in your credentials.
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.