Can my agent check availability across different calendar providers like Google and iCloud?

Yes. Use the 'query_availability' tool. Your agent will traverse multi-user JSON payloads and calculate strict intersections across all connected accounts, regardless of the underlying calendar provider.

How do I create a new calendar event via the agent?

Provide the 'calendar_id', 'summary', and 'start/end' times to the 'create_event' tool. The agent commands Cronofy to update your upstream provider synchronously, ensuring the event appears on your calendar immediately.

Can I generate a public scheduling link through chat?

Absolutely. Use the 'create_scheduling_request' tool. The agent will generate a shared UI link mapped to your live availability, which you can then share externally to let others book time with you.

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

Name: Cronofy
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Cronofy through Vinkius, pass the Edge URL in the `mcps` parameter and every Cronofy 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="Cronofy Specialist",
    goal="Help users interact with Cronofy effectively",
    backstory=(
        "You are an expert at leveraging Cronofy 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 Cronofy "
        "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 Cronofy MCP Server

Connect your Cronofy account to any AI agent and take full control of your unified calendar and scheduling workflows through natural conversation.

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

Unified Event Management — List, retrieve, and create events across aggregated Google, iCloud, and Exchange overlays limitlessly
Multi-User Availability — Query availability for up to 10 participants simultaneously, calculating strict intersections to find the perfect meeting time
Free/Busy Auditing — Execute bulk iterations to map time matrices and return exact available boundaries without exposing event payloads
Automated Scheduling — Generate live-availability links and shared scheduling requests to simplify meeting coordination with external members
Identity & Profile Mapping — Inspect unified account canonical IDs and list distinct identity providers connected natively to your Cronofy profile
Sync Control — Irreversibly vaporize explicit validations and delete events to maintain absolute consistency across all connected upstream providers

The Cronofy 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 Cronofy to CrewAI via MCP

Follow these steps to integrate the Cronofy 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 Cronofy

Why Use CrewAI with the Cronofy MCP Server

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

Cronofy + CrewAI Use Cases

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

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

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

Cronofy MCP Tools for CrewAI (10)

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

create_event

Provision a highly-available JSON Payload generating explicit Sync links

create_scheduling_request

Fetch elaborate explicit mapped limits via native forms dispatch

delete_event

Irreversibly vaporize explicit validations extracting rich Provider syncs

get_account

Inspect deep internal arrays mitigating specific Sub Provider lists

get_free_busy

Enumerate explicitly attached structured rules exporting active Overlaps

get_user_info

Identify precise active arrays spanning native Gateway auth bounds

list_calendars

Retrieve explicit Cloud logging tracing explicit Payload IDs limitlessly

list_profiles

Retrieve the exact structural matching verifying Blueprint directories

query_availability

Dispatch an automated validation check routing explicit Cross-Provider checks

read_events

cronofy.com/v1/events` pulling unified aggregated Google, iCloud, and Exchange overlays limitlessly. Identify bounded CRM records inside the Headless Cronofy Engine

Example Prompts for Cronofy in CrewAI

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

"List my calendar events from tomorrow to next week"

"Find a 30-minute slot for a meeting with john@example.com tomorrow"

"Create a scheduling link for a 'Project Review' meeting"

Troubleshooting Cronofy MCP Server with CrewAI

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

Cronofy + CrewAI FAQ

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