How do I get an Eventmaker API Key?

Log in to your Eventmaker account, navigate to **Account Settings > API**, and you can generate or retrieve your unique API Key from there. Ensure you have an active plan that supports API access.

Can the agent perform onsite check-ins?

This integration currently focuses on listing and auditing events, participants, and check-in logs. Performing live check-ins or scanning badges should be managed via the Eventmaker mobile app or onsite hardware.

Does the integration show real-time attendance rates?

Yes, you can use the get_event_performance_stats tool to retrieve real-time data on check-in rates and total registrations compared to onsite attendance.

Eventmaker MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Eventmaker
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Eventmaker through Vinkius, pass the Edge URL in the `mcps` parameter and every Eventmaker 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="Eventmaker Specialist",
    goal="Help users interact with Eventmaker effectively",
    backstory=(
        "You are an expert at leveraging Eventmaker 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 Eventmaker "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 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 Eventmaker MCP Server

Integrate Eventmaker, the comprehensive event management software, directly into your AI workflow. Manage your corporate events and trade shows, track registered participants and exhibitors, monitor session schedules and real-time check-ins, and oversee your event performance using natural language.

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

Event Oversight — List and retrieve detailed information, start dates, and status for all your Eventmaker projects.
Participant Intelligence — Monitor registered participants and exhibitors, resolving names, emails, and professional categories.
Operational Management — Access and monitor event sessions and real-time check-in logs to stay ahead of attendee flow.
Performance Auditing — Retrieve high-level summaries of registration volume, check-in rates, and organizational event health instantly.

The Eventmaker MCP Server exposes 10 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 Eventmaker to CrewAI via MCP

Follow these steps to integrate the Eventmaker 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 10 tools from Eventmaker

Why Use CrewAI with the Eventmaker MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Eventmaker 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

Eventmaker + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries Eventmaker 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 Eventmaker, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Eventmaker 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 Eventmaker against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Eventmaker MCP Tools for CrewAI (10)

These 10 tools become available when you connect Eventmaker to CrewAI via MCP:

get_event_detailed_data

Get detailed settings and information for a specific event

get_event_performance_stats

Get high-level performance metrics for a specific event

get_eventmaker_account_metadata

Retrieve metadata and limits for your Eventmaker account

list_all_events

List all events managed in your Eventmaker account

list_currently_ongoing_events

Identify events that are currently active or ongoing

list_event_checkins_log

List all check-in events and logs for a specific event

list_event_exhibitors

List all exhibitors and partners for a specific event

list_event_participants

List all registered participants for a specific event

list_event_sessions

List all sessions and schedule items for a specific event

quick_event_engagement_audit

Retrieve a high-level summary of participants and check-ins

Example Prompts for Eventmaker in CrewAI

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

"List all participants for event ID '12345'."

"Show me the check-in log for today."

"Get performance stats for 'Autumn Trade Show'."

Troubleshooting Eventmaker MCP Server with CrewAI

Common issues when connecting Eventmaker 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.

Eventmaker + CrewAI FAQ

Common questions about integrating Eventmaker 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.