Bring Calendar Integration
to Cursor
Learn how to connect Truto Unified Calendar to Cursor and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the 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.
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
How it works
- Anchor this multi-calendar instance to your local Vinkius conversational agent
- Provide the Master Token from Truto combined specifically with your
Integrated Account IDtargeting a specific linked provider - Engage scheduling queries organically conversing with your assistant
Who is this for?
- Executive Assistants — Book multi-provider meetings strictly through conversational commands checking calendar gaps dynamically
- Sales Coordinators — Force event creation securely across varied client infrastructures without logging into fragmented Google and Microsoft portals
- Platform Architects — Centralize routing logic manipulating the agent to alter calendar entries strictly using one unified schema rule
Built-in capabilities (10)
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
This action is irreversible. Delete an event via Truto. The event is removed from both Truto and the underlying provider in real-time
Get details of a specific calendar via Truto by ID. Returns calendar name, provider, timezone, and metadata normalized to the Truto unified schema
Get full details of a specific event via Truto. Returns title, description, start/end times, attendees, location, organizer, recurrence, and provider-specific metadata
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 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 all integrated accounts (connections) in Truto. Shows connected calendar providers, auth status, and account metadata
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
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 a Truto integrated account connection. Checks credentials, permissions, and API accessibility. Returns validation status and any errors
Why Cursor?
Cursor's Agent mode turns Truto Unified Calendar into an in-editor superpower. Ask Cursor to generate code using live data from Truto Unified Calendar and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Truto Unified Calendar in Cursor
Truto Unified Calendar and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Truto Unified Calendar to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Truto Unified Calendar in Cursor
The Truto Unified Calendar 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. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Truto Unified Calendar for Cursor
Every tool call from Cursor to the Truto Unified Calendar MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Docparser
10 toolsEquip your AI agent to extract data from documents, manage parsers, and track extraction results via the Docparser API.
Ellie Planner
8 toolsPlan projects visually with AI-assisted task breakdowns, timelines, and team coordination that adapts as your work evolves.
Drip
10 toolsAutomate e-commerce marketing via Drip — manage subscribers, trigger workflows, track custom events, and audit campaigns directly from any AI agent.
Moloni (Cloud Invoicing & Fiscal Management)
20 toolsManage certified invoicing via Moloni — track customers by VAT/NIF, audit invoices, and monitor stock levels.