MCP
Primecal MCP
Model Context Protocol integration for AI agents. Connect with scoped permissions and generated configuration that covers the connection details from the start.
AI & DEVELOPERS
Prime Calendar for agents and technical workflows
Connect calendar data to the tools you build. Primecal MCP gives agents and developers scoped access, managed keys, and generated configuration so integrations start from a working baseline.
Integration architecture
How Prime Calendar connects to your stack
Primecal MCP exposes calendar workflows through a documented interface. Agents and tools connect with scoped permissions — no read-everything access, no manual configuration from scratch.
API
REST API
Open API documentation for direct integration. Build custom workflows on top of calendar events, booking, and automation endpoints.
HOOKS
Webhooks
Connect schedule changes to downstream systems. Webhook-ready automation for event-driven workflows and external tool triggers.
Primecal MCP
Designed for agentic calendar access
Primecal MCP implements the Model Context Protocol so AI agents can read and write calendar events through a controlled interface. Each connection scopes what the agent can see and do — no blanket access.
- Scoped permissions — agents only see what they need
- Managed keys for reviewable, rotatable access
- Generated MCP configuration — start from a working baseline
- Companion API documentation for deeper integration
CONNECT IN A MINUTE
Connect your AI client
Prime Calendar is a remote MCP server with OAuth sign-in, so there is nothing to install. MCP access needs the User plan or higher.
Claude (web and desktop)
Settings › Connectors › Add custom connector. Paste the URL, sign in and approve a permission level.
https://api.primecal.eu/api/mcpClaude Code
Run the command, then type /mcp and sign in.
claude mcp add --transport http primecal https://api.primecal.eu/api/mcpCursor
Add this to ~/.cursor/mcp.json and sign in when asked.
{
"mcpServers": {
"primecal": {
"url": "https://api.primecal.eu/api/mcp"
}
}
}Connecting MCP hosts step by step · Tools and resources the MCP server exposes
Two ways to connect
Pick the connection that matches your workflow
Both paths reach the same MCP tools. The difference is how the agent authenticates.
OAuth Connect
One click, sign in, pick a permission level, approve. Primecal runs its own OAuth 2.1 + PKCE + Dynamic Client Registration server — no API key ever changes hands.
Agent API key
A static ag_sk_... key for scripted or command-line integrations, scoped to the same permission levels as OAuth.
Permission levels
Nine preset access levels, or build your own
Pick a preset in one click, or switch to Custom mode and toggle any individual action yourself. Every call is scope-checked server-side, not just hidden in the UI.
Minimal
Identity and profile lookups only — no calendar, task, or automation access.
All read-only
Browse every calendar, task, and routine. Can never create, edit, or delete anything.
Calendar only
Read and write calendar events. No access to tasks, routines, or automation.
Tasks & routines
Manage tasks and start or track routines. Calendar stays read-only.
Reservations operator
Manage bookings and availability for an organisation's resources.
Automation manager
List, inspect, and trigger automation rules without touching calendar data directly.
Household manager
Full control over routines, tasks, and household inventory.
Operational read/write
Calendar, tasks, and routines are all writable. Automation and reservations stay read-only.
Full MCP admin
Every available action, including automation and reservation writes.
Connecting through OAuth grants the level you pick across all of your calendars and organisations. To scope access down to specific calendars or individual actions, fine-tune it afterward in Agent Settings inside the app.
Access governance
Built-in permission controls
Every integration starts with a scope you define. Managed keys keep connections reviewable and easy to rotate. Nothing connects with blanket access.
Scoped permissions
Choose the exact resources and actions an agent or connected tool can reach before issuing access.
Managed keys
Create and rotate managed keys so connected workflows stay reviewable without rebuilding credentials from scratch.
Generated configuration
Start from generated Primecal MCP configuration instead of rebuilding the connection details by hand.
Developer resources
Documentation built for builders
- Secure payment: Paddle (Merchant of Record)
- 14-day money-back guarantee
- Cancel anytime — Free stays
- Personal Logs: see when and who accessed your data
How it compares
Prices and trade-offs next to the tools people usually look at as well.