Your calendars, managed your way in chat with Claude.

This page covers the practical side: what setup looks like, where Cocal works, and what it can and cannot see.

Sign up

Setup, start to finish.

Four steps, a few minutes. Here is what each one actually looks like.

  1. 1

    Sign in with Google

    Your Cocal account is your Google sign-in. There is no separate password, and signing in is also how you connect your first calendar account.

    Sign in with Google
  2. 2

    Choose your calendars

    Connect work, personal, or extra Google accounts and turn individual calendars on or off. Claude only sees the calendars you enable, and you can change the list any time.

    • Workyou@company.com
    • Personalyou@gmail.com
    • Familyyou@gmail.com
    • Team standup (shared)you@company.com
  3. 3

    Add your preferences

    Preferences are a freeform note Claude reads at the start of every conversation. Write rules however you like, in chat or on the web. Changes apply to new conversations.

    Calendar preferences

    • Default new events to my work calendar on weekdays.
    • Keep Fridays meeting-light.
    • Lunch is 12:30 to 1:15. Don’t book over it.
  4. 4

    Connect Claude

    In Claude, add Cocal as a connector and paste the server URL below. In Claude Code, it's one terminal command. The connect guide walks through each client click by click.

    Server URL

    https://mcp.cocal.io/mcp

Where it works.

Claude on the web and desktop

Chat plus the visual calendar. Your day appears as an actual schedule in the conversation, so you can compare events and spot conflicts instead of reading a list.

Claude on your phone

The same visual calendar in the Claude mobile app. Check your day, move events, and catch conflicts from wherever you are. There is nothing extra to set up: connect once and Cocal is there wherever you sign in to Claude.

Claude Code

The same calendar control in text. List your day, find open time, and create events from the terminal.

Cocal is built for Claude. The visual calendar appears where Claude supports embedded interfaces; everywhere else, answers arrive as plain chat.

What Cocal can see, and what it keeps.

The permissions you grant
Reading and writing events, plus reading your calendar list and free/busy times. Cocal does not ask for control over calendar sharing.
What Cocal stores
Not your events. Event titles, descriptions, and attendees pass through to Claude without being saved. The activity log records when something happened, never what your events contain.
Walking away
Disconnect a calendar account from your dashboard any time, or revoke access from your Google account settings. If Google reports a security event on your account, Cocal revokes its own access automatically.

The privacy policy spells all of this out in full.

Set up once, the same everywhere.

Your calendar choices and preferences live on your Cocal account, not inside any one app. Claude on your laptop, your phone, and Claude Code all read the same setup. Update a rule once and every new conversation follows it.

Under the hood, Cocal builds on one of the most widely used open-source Google Calendar integrations for AI assistants, with account-based setup, preferences, and the visual calendar layer on top.

Ready when your calendars are.

Start by creating your Cocal account. After that, the calendar dashboard walks you through the exact setup for the AI apps you use.

Start with Google