How and where do I collect my universal Truto API Token?

Navigate accurately toward your primary Truto management dashboard portal. Search intentionally along your workspace or developer settings focusing clearly on the `API Keys` section. Dictate the explicit creation of a new bearer credential. Lock the generated long string into your clipboard and transport it perfectly to the waiting field array below.

What is the Truto Integrated Account ID and where is it?

Because Truto is unified, one single environment connects entirely to many different client calendars (e.g., your Google, a client's Outlook). The `Integrated Account ID` designates explicitly WHICH underlying calendar provider the agent should orchestrate right now. You fetch this prefix ID commonly starting with `ia_` precisely from the Integrations tab listed inside your Truto dashboard.

Should I save the Truto API Token immediately?

Yes. Once you click 'Create API Token' and it gets generated, you must copy it immediately. Truto will only show the API Token once. If you close the window without securely saving it, you will have to create a new one.

Truto Unified Calendar MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Truto Unified Calendar
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

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

Deploy the ultimate scheduling machine by linking your AI agent to Truto. Instead of building fragmented code for individual calendar APIs, Truto provides a normalized schema that controls Google Calendar, Outlook, and countless others underneath. Command your agent to list daily events, find free timeslots accurately, or write absolute meetings directly to the chosen provider without swapping logic loops.

When paired with CrewAI, Truto Unified Calendar becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Truto Unified Calendar tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

Unified Calendar Tracking — Check all connected calendars regardless of provider natively and list their available events continuously
Meeting Generation — Instruct your AI to generate or directly cancel/update specific events passing ISO-compliant timings directly to the root provider
Free/Busy Analysis — Demand explicit gaps inside your schedule bypassing complex metadata just extracting readable unavailable/available blocks
Integration Audit — Check the absolute status of all connected root provider connections (Integrations) to ensure nothing is decoupled abruptly
Event Forensics — Interrogate and extract any granular metadata embedded inside an event_id, including conferencing details and attendee lists

The Truto Unified Calendar 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 Truto Unified Calendar to CrewAI via MCP

Follow these steps to integrate the Truto Unified Calendar 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 Truto Unified Calendar

Why Use CrewAI with the Truto Unified Calendar MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Truto Unified Calendar 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 the 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

Truto Unified Calendar + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Truto Unified Calendar MCP Server delivers measurable value.

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

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

Truto Unified Calendar MCP Tools for CrewAI (10)

These 10 tools become available when you connect Truto Unified Calendar to CrewAI via MCP:

create_event

Provide calendar_id, title, and start/end times in ISO format. Create a new event in a calendar via Truto. The event is written through to the underlying provider (Google/Outlook) in real-time. Provide calendar ID, title, and ISO 8601 start/end times

delete_event

This action is irreversible. Delete an event via Truto. The event is removed from both Truto and the underlying provider in real-time

get_calendar

Get details of a specific calendar via Truto by ID. Returns calendar name, provider, timezone, and metadata normalized to the Truto unified schema

get_event

Get full details of a specific event via Truto. Returns title, description, start/end times, attendees, location, organizer, recurrence, and provider-specific metadata

get_free_busy

Provide calendar_id and time range. Get free/busy data for a calendar via Truto within a date range. Returns time blocks as free or busy in the unified Truto format

list_calendars

List all calendars via Truto unified API. Truto provides a real-time, pass-through API that normalizes calendar data across Google Calendar, Outlook Calendar, and other providers into a consistent schema

list_connections

List all integrated accounts (connections) in Truto. Shows connected calendar providers, auth status, and account metadata

list_events

Provide the calendar_id. List all events from a calendar via Truto. Returns events in a unified format regardless of the underlying provider. Shows titles, times, attendees, locations, and conferencing info

update_event

Provide the event_id and a JSON updates object. Update an existing event via Truto. Provide a JSON object with fields to change. Changes pass through to the real provider in real-time

validate_connection

Validate a Truto integrated account connection. Checks credentials, permissions, and API accessibility. Returns validation status and any errors

Example Prompts for Truto Unified Calendar in CrewAI

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

"List all interconnected calendars belonging to this unified account."

"Search my events and get the specific details for event ID evt_7xkP."

Troubleshooting Truto Unified Calendar MCP Server with CrewAI

Common issues when connecting Truto Unified Calendar 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

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Truto Unified Calendar + CrewAI FAQ

Common questions about integrating Truto Unified Calendar 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.