Bring Campaign Finance
to CrewAI
Learn how to connect OpenFEC (Federal Election Commission) to CrewAI and start using 21 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the OpenFEC (Federal Election Commission) MCP Server?
Connect to the official OpenFEC API and bring transparency to federal election data through your AI agent. This server provides direct access to the Federal Election Commission's comprehensive database of campaign finance information.
What you can do
- Candidate Research — List and search for individuals running for President, Senate, or House with filters for state, party, and cycle.
- Financial Analytics — Retrieve aggregated financial totals and summaries for specific candidates to understand fundraising and spending.
- Committee Tracking — Explore political committees (PACs, party committees) and their detailed metadata and filings.
- Historical Context — Access the history of candidate filings and designations over multiple election cycles.
- Deep Metadata — Fetch detailed profiles for any candidate or committee using their unique FEC identifiers.
How it works
- Subscribe to this server
- Enter your OpenFEC API Key
- Start querying election data from Claude, Cursor, or any MCP client
Who is this for?
- Journalists & Researchers — quickly verify campaign finance figures and candidate statuses without manual database exports.
- Data Analysts — pull structured election data directly into your workflow for political trend analysis.
- Civic Tech Developers — integrate official government data into applications with ease.
Built-in capabilities (21)
Get detailed information for a specific candidate by ID
Get the history of a candidate filings and designations
Get aggregated financial totals for a specific candidate
Get detailed information for a specific committee by ID
Get the history of a committee characteristics over time
Get financial totals for a specific committee type
Get financial totals aggregated by candidate or committee entity
Summarize financial data by committee officer
Fetch a list of candidates with various filters
Fetch a list of committees with filters
List all filings (electronic and paper) with filters
Fetch financial reports filed by specific types of committees
Itemized Receipts: Contributions from individuals and committees
Itemized Disbursements: Operating expenditures, transfers, refunds
Loans: Information on loans received or made by committees
Debts: Debts and obligations owed by or to committees
Independent Expenditures: Spending to support/oppose candidates
Coordinated Party Expenditures: Spending in coordination with candidates
Get contact information for state election offices
Search for candidates by name or other attributes
Search for committees by name or ID
Why CrewAI?
When paired with CrewAI, OpenFEC (Federal Election Commission) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call OpenFEC (Federal Election Commission) 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
OpenFEC (Federal Election Commission) in CrewAI
OpenFEC (Federal Election Commission) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect OpenFEC (Federal Election Commission) 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 | 4,000+ 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 OpenFEC (Federal Election Commission) in CrewAI
The OpenFEC (Federal Election Commission) 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 21 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
OpenFEC (Federal Election Commission) for CrewAI
Every tool call from CrewAI to the OpenFEC (Federal Election Commission) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I find out how much a specific candidate has raised in total for an election cycle?
Yes! Use the get_candidate_totals tool with the candidate's ID and the desired cycle. It will return aggregated financial summaries including total receipts and disbursements.
How do I search for all candidates running for the Senate in a specific state?
You can use the list_candidates tool and provide 'S' for the office and the two-letter state abbreviation (e.g., 'CA' for California) to filter the results.
Is it possible to see the history of a candidate's previous filings?
Absolutely. The get_candidate_history tool allows you to retrieve historical data for a candidate, showing their filings and designations over time.
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.
Explore More MCP Servers
View all →
UK ONS Population — Deaths, Well-being & Demographics
5 toolsUK population and health statistics: weekly death registrations by age, sex, and region, personal well-being estimates (life satisfaction, happiness, anxiety), suicide data by local authority, and population projections from the ONS.
Rapid URL Indexer
5 toolsFast URL indexing and SEO tools.
Hudu
10 toolsManage IT documentation, assets, and passwords via Hudu API.
CloudCart
8 toolsManage e-commerce and store operations via CloudCart — track products, monitor orders, and manage customers directly from any AI agent.