4,000+ servers built on vurb.ts
Vinkius

OpenFEC (Federal Election Commission) MCP Server for CrewAIGive CrewAI instant access to 21 tools to Get Candidate, Get Candidate History, Get Candidate Totals, and more

MCP Inspector GDPR Free for Subscribers

Connect your CrewAI agents to OpenFEC (Federal Election Commission) through Vinkius, pass the Edge URL in the `mcps` parameter and every OpenFEC (Federal Election Commission) tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Ask AI about this MCP Server for CrewAI

The OpenFEC (Federal Election Commission) MCP Server for CrewAI is a standout in the Data Analytics category — giving your AI agent 21 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
python
from crewai import Agent, Task, Crew

agent = Agent(
    role="OpenFEC (Federal Election Commission) Specialist",
    goal="Help users interact with OpenFEC (Federal Election Commission) effectively",
    backstory=(
        "You are an expert at leveraging OpenFEC (Federal Election Commission) tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in OpenFEC (Federal Election Commission) "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 21 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
OpenFEC (Federal Election Commission)
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About 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.

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.

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.

The OpenFEC (Federal Election Commission) MCP Server exposes 21 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 21 OpenFEC (Federal Election Commission) tools available for CrewAI

When CrewAI connects to OpenFEC (Federal Election Commission) through Vinkius, your AI agent gets direct access to every tool listed below — spanning campaign-finance, election-data, political-transparency, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

get

Get candidate on OpenFEC (Federal Election Commission)

Get detailed information for a specific candidate by ID

get

Get candidate history on OpenFEC (Federal Election Commission)

Get the history of a candidate filings and designations

get

Get candidate totals on OpenFEC (Federal Election Commission)

Get aggregated financial totals for a specific candidate

get

Get committee on OpenFEC (Federal Election Commission)

Get detailed information for a specific committee by ID

get

Get committee history on OpenFEC (Federal Election Commission)

Get the history of a committee characteristics over time

get

Get totals by committee type on OpenFEC (Federal Election Commission)

Get financial totals for a specific committee type

get

Get totals by entity on OpenFEC (Federal Election Commission)

Get financial totals aggregated by candidate or committee entity

get

Get totals officer summary on OpenFEC (Federal Election Commission)

Summarize financial data by committee officer

list

List candidates on OpenFEC (Federal Election Commission)

Fetch a list of candidates with various filters

list

List committees on OpenFEC (Federal Election Commission)

Fetch a list of committees with filters

list

List filings on OpenFEC (Federal Election Commission)

List all filings (electronic and paper) with filters

list

List reports on OpenFEC (Federal Election Commission)

Fetch financial reports filed by specific types of committees

list

List schedule a on OpenFEC (Federal Election Commission)

Itemized Receipts: Contributions from individuals and committees

list

List schedule b on OpenFEC (Federal Election Commission)

Itemized Disbursements: Operating expenditures, transfers, refunds

list

List schedule c on OpenFEC (Federal Election Commission)

Loans: Information on loans received or made by committees

list

List schedule d on OpenFEC (Federal Election Commission)

Debts: Debts and obligations owed by or to committees

list

List schedule e on OpenFEC (Federal Election Commission)

Independent Expenditures: Spending to support/oppose candidates

list

List schedule f on OpenFEC (Federal Election Commission)

Coordinated Party Expenditures: Spending in coordination with candidates

list

List state election offices on OpenFEC (Federal Election Commission)

Get contact information for state election offices

search

Search candidates on OpenFEC (Federal Election Commission)

Search for candidates by name or other attributes

search

Search committees on OpenFEC (Federal Election Commission)

Search for committees by name or ID

Connect OpenFEC (Federal Election Commission) to CrewAI via MCP

Follow these steps to wire OpenFEC (Federal Election Commission) into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Install CrewAI

Run pip install crewai
02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
03

Customize the agent

Adjust the role, goal, and backstory to fit your use case
04

Run the crew

Run python crew.py. CrewAI auto-discovers 21 tools from OpenFEC (Federal Election Commission)

Why Use CrewAI with the OpenFEC (Federal Election Commission) MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with OpenFEC (Federal Election Commission) through the Model Context Protocol.

01

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

02

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

03

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

04

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) + CrewAI Use Cases

Practical scenarios where CrewAI combined with the OpenFEC (Federal Election Commission) MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries OpenFEC (Federal Election Commission) for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries OpenFEC (Federal Election Commission), analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain OpenFEC (Federal Election Commission) tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries OpenFEC (Federal Election Commission) against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for OpenFEC (Federal Election Commission) in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with OpenFEC (Federal Election Commission) immediately.

01

"List all presidential candidates for the 2024 election cycle."

02

"Show me the financial totals for candidate ID P00000001 in the 2024 cycle."

03

"Search for political committees with 'Action' in their name."

Troubleshooting OpenFEC (Federal Election Commission) MCP Server with CrewAI

Common issues when connecting OpenFEC (Federal Election Commission) to CrewAI through Vinkius, and how to resolve them.

01

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
02

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
03

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
04

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.

OpenFEC (Federal Election Commission) + CrewAI FAQ

Common questions about integrating OpenFEC (Federal Election Commission) MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Explore More MCP Servers

View all →