How do I find my vote.direct API Key?

Log in to your [**vote.direct dashboard**](https://vote.direct/), register for an API Key, and you will find it in your account settings. Copy and paste it below.

Does it show the specific items on the ballot?

Yes. The `get_ballot_information` tool retrieves the specific measures and candidates that will appear on the ballot for a given address.

Can the agent check registration deadlines?

Yes. Use the `get_registration_details` tool providing the state code. Your agent will return the official deadlines and registration links instantly.

vote.direct MCP Server for CrewAI 5 tools — connect in under 2 minutes

Name: vote.direct
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 5 Tools Framework

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

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="vote.direct Specialist",
    goal="Help users interact with vote.direct effectively",
    backstory=(
        "You are an expert at leveraging vote.direct 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 vote.direct "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 5 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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 vote.direct MCP Server

Empower your AI agent to orchestrate your entire civic participation and voter auditing workflow with vote.direct, the comprehensive source for localized election data. By connecting vote.direct to your agent, you transform complex voter searches into a natural conversation. Your agent can instantly search for polling locations, audit upcoming elections, and retrieve registration deadlines without you ever touching a government portal. Whether you are preparing for a local vote or conducting regional civic research, your agent acts as a real-time civic consultant, ensuring your data is always verified and localized.

When paired with CrewAI, vote.direct becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call vote.direct 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

Polling Auditing — Search for polling locations near any street address and retrieve detailed metadata, including hours and names.
Election Oversight — Audit upcoming elections for specific ZIP codes to maintain a clear view of local civic timelines and scale.
Ballot Discovery — Retrieve detailed ballot information for specific elections to understand the legislative items and candidates instantly.
Registration Intelligence — Query voter registration deadlines and links for any state to assist in civic compliance and planning.
Civic Monitoring — Check API status to ensure your civic research workflow is always operational.

The vote.direct MCP Server exposes 5 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect vote.direct to CrewAI via MCP

Follow these steps to integrate the vote.direct MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

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

Customize the agent

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

Run the crew

Run python crew.py. CrewAI auto-discovers 5 tools from vote.direct

Why Use CrewAI with the vote.direct MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with vote.direct through the Model Context Protocol.

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 `mcps` parameter 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

vote.direct + CrewAI Use Cases

Practical scenarios where CrewAI combined with the vote.direct MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries vote.direct for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries vote.direct, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain vote.direct tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries vote.direct against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

vote.direct MCP Tools for CrewAI (5)

These 5 tools become available when you connect vote.direct to CrewAI via MCP:

check_api_status

direct election data service. Check if the vote.direct service is operational

get_ballot_information

Get ballot information for a specific election and address

get_polling_locations

Find polling locations near a specific address

get_registration_details

Get voter registration deadlines and links for a specific state

get_upcoming_elections

Find upcoming elections for a specific ZIP code

Example Prompts for vote.direct in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with vote.direct immediately.

"Find polling locations near '1600 Pennsylvania Avenue NW, Washington, DC' using vote.direct."

"What elections are upcoming for ZIP code '90210'?"

"Get registration deadline for 'New York'."

Troubleshooting vote.direct MCP Server with CrewAI

Common issues when connecting vote.direct to CrewAI through the Vinkius, and how to resolve them.

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.

vote.direct + CrewAI FAQ

Common questions about integrating vote.direct MCP Server with CrewAI.

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.