Skip to content

AI Agents with MCP

Calendaria can connect to AI agents through remote MCP at:

https://api.calendaria.co/mcp

Use this URL in Claude, Cursor, or another OAuth-capable MCP client when you want that client to use Calendaria calendar tools. MCP support runs inside the existing Calendaria API; there is no separate Calendaria app to install for remote MCP clients.

For ChatGPT, Calendaria is creating a dedicated Calendaria ChatGPT app. ChatGPT setup will use that app flow instead of asking users to paste the remote MCP URL into ChatGPT.

Safety model

Read-only tools can inspect calendars, events, free time, conflicts, booking links, and group invites. Calendar-changing tools create pending actions first and require explicit confirmation before Calendaria changes a calendar.

Connection flow

The normal flow is:

  1. Add the Calendaria MCP URL in your MCP client.
  2. The client opens Calendaria's authorization page.
  3. Sign in with your Calendaria magic link.
  4. Authorize the AI agent.
  5. Return to the client and use Calendaria tools from the agent.

MCP clients do not receive dashboard cookies, Google OAuth tokens, provider credentials, or encrypted token data. The client receives access to Calendaria's MCP tools through the authorization you approve.

Cursor setup

Add Calendaria to Cursor's mcp.json:

{
  "mcpServers": {
    "calendaria": {
      "type": "http",
      "url": "https://api.calendaria.co/mcp"
    }
  }
}

After saving the config, follow Cursor's sign-in or authorization prompt. Calendaria will open its authorization page, send your magic link, and ask you to authorize the agent.

Do not put a username, password, magic link, Google token, or Calendaria dashboard cookie in Cursor's mcp.json.

ChatGPT app

Calendaria is creating a dedicated ChatGPT app for ChatGPT users. Use the ChatGPT app flow when it is available; use the remote MCP URL on this page for Claude, Cursor, and other OAuth-capable MCP clients.

Claude and other clients

In Claude or another OAuth-capable MCP client, add Calendaria as a remote MCP server with this URL:

https://api.calendaria.co/mcp

The client should handle the OAuth redirect, Calendaria sign-in, and authorization screen. If your client asks whether to trust or enable the server, review the server URL and continue only when it is https://api.calendaria.co/mcp.

What agents can do

With authorization, an AI agent can use Calendaria tools to:

  • inspect calendars and event details
  • find free time, conflicts, booking links, and group invites
  • prepare event creation, move, delete, update, RSVP, booking-link, or group-invite actions

Read-only tools can run immediately. Calendar-changing actions are staged as pending actions and wait for your explicit confirmation in Calendaria before anything changes in a calendar.

Revoke access

You can revoke connected AI agents from the Calendaria dashboard. Revocation is useful when you stop using a client, lose access to a device, or want to reconnect with a fresh authorization.

Troubleshooting

Cursor still appears connected after removing the config

Remove the config, revoke the AI agent from the Calendaria dashboard, then reconnect from Cursor.

The client shows old or missing Calendaria tools

Disconnect and reconnect Calendaria after MCP tool or auth updates. This lets the client refresh tool descriptors and authorization tokens.

The client asks for credentials in config

Do not add credentials to mcp.json or any client config. Calendaria uses browser-based OAuth and magic-link sign-in during the authorization flow.