Can my agent create events on my synced Google or Outlook calendars?

Yes. When you use the 'create_event' tool, the agent commands the Notion Calendar backend to generate the meeting overlay, which is then synchronized directly to your connected upstream provider logic.

How do I check if my team members are free for a meeting on a specific date?

Use the 'get_free_busy' tool. Provide a JSON array of email addresses and the target date. Your agent will analyze the cross-references and identify available hourly slots, predicting any potential collision limits.

Can I retrieve my scheduling links via chat to share with clients?

Absolutely. The 'get_scheduling_links' tool extracts the precise active booking forms tied directly to your Notion Calendar profile, allowing your agent to provide you with ready-to-share links instantly.

Notion Calendar (formerly Cron) MCP Server for Cursor 10 tools — connect in under 2 minutes

Name: Notion Calendar (formerly Cron)
Availability: InStock
Author: Vinkius

docs.cursor.com/context/model-context-protocol

Built by Vinkius GDPR 10 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

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.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Notion Calendar (formerly Cron) and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "notion-calendar-formerly-cron": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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 Notion Calendar (formerly Cron) MCP Server

Connect your Notion Calendar (formerly Cron) account to any AI agent and take full control of your beautifully designed scheduling workflows through natural conversation.

Cursor's Agent mode turns Notion Calendar (formerly Cron) into an in-editor superpower. Ask Cursor to generate code using live data from Notion Calendar (formerly Cron) 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.

What you can do

Event Orchestration — List and retrieve exact CRM records extracting events tied strictly to specific date constraints and Notion sync states
Live Scheduling — Provision highly-available Event payloads generating hard schedule binds synchronized directly to upstream Google or Microsoft logic
Availability Auditing — Dispatch automated validation checks to process cross-calendar math and isolate available bookable limits explicitly
Team Coordination — Enumerate explicitly attached structural rules to analyze freeBusy cross-references and predict collision limits across multiple emails
Booking Links — Retrieve precise active scheduling forms and booking links tied directly to your profile settings for instant sharing
Profile Management — Inspect deep internal arrays of your Cron profile, including localized preferences and unified calendar provider connections

The Notion Calendar (formerly Cron) MCP Server exposes 10 tools through the Vinkius. Connect it to Cursor 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 Notion Calendar (formerly Cron) to Cursor via MCP

Follow these steps to integrate the Notion Calendar (formerly Cron) MCP Server with Cursor.

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

Save the file

Cursor will automatically detect the new MCP server

Start using Notion Calendar (formerly Cron)

Open Agent mode in chat and ask: "Using Notion Calendar (formerly Cron), help me...". 10 tools available

Why Use Cursor with the Notion Calendar (formerly Cron) MCP Server

Cursor AI Code Editor provides unique advantages when paired with Notion Calendar (formerly Cron) through the Model Context Protocol.

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

Notion Calendar (formerly Cron) + Cursor Use Cases

Practical scenarios where Cursor combined with the Notion Calendar (formerly Cron) MCP Server delivers measurable value.

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

Notion Calendar (formerly Cron) MCP Tools for Cursor (10)

These 10 tools become available when you connect Notion Calendar (formerly Cron) to Cursor via MCP:

create_event

Provision a highly-available Event Payload generating hard Schedule binds

delete_event

Irreversibly vaporize explicit validations extracting rich Schedule drops

get_availability

Dispatch an automated validation check routing explicit Availability

get_event

Perform structural extraction of properties driving active Event targets

get_free_busy

Enumerate explicitly attached structured rules exporting active Graph overlaps

get_profile

Inspect deep internal arrays mitigating specific Math Logic limits

get_scheduling_links

Identify precise active arrays spanning native Gateway limits

list_calendars

Retrieve explicit Cloud logging tracing explicit Payload IDs limitlessly

list_events

Identify bounded CRM records inside the Headless Cron Engine

update_event

Dissect precise variables checking active state matching payload targets

Example Prompts for Notion Calendar (formerly Cron) in Cursor

Ready-to-use prompts you can give your Cursor agent to start working with Notion Calendar (formerly Cron) immediately.

"List my calendar events for today"

"Check if john@acme.com and sarah@acme.com are free tomorrow"

"Give me my booking link for '15 Minute Coffee Chat'"

Troubleshooting Notion Calendar (formerly Cron) MCP Server with Cursor

Common issues when connecting Notion Calendar (formerly Cron) to Cursor through the Vinkius, and how to resolve them.

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.

Notion Calendar (formerly Cron) + Cursor FAQ

Common questions about integrating Notion Calendar (formerly Cron) MCP Server with Cursor.

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.