Overview
The Google Calendar integration lets users connect their Google Calendar so Alysio can read and manage their calendar on their behalf. Users can ask Alysio to list upcoming events, see the next meeting, create or update events, and view calendar details—all in natural language. The integration uses the user’s connected Google account so all actions apply to their own calendars (e.g. primary or other calendars they have access to).
Supported capabilities / objects
- Calendars — Get calendar details (e.g. primary calendar).
- Events — List events in a date range, get a single event, get the next upcoming event, create events, update events (title, time, location, description, attendees, etc.).
- User settings — Timezone, week start day, locale, and other calendar preferences (used to show times and dates in the user’s timezone).
Authentication
Method: OAuth 2.0 (Google). The MCP sends requests using a Bearer token and a credential ID that identifies the user’s connected Google account.
Redirect URI: Configured when the Google Calendar integration is set up in Alysio.
Token handling
- OAuth tokens for the connected Google account are stored securely and refreshed automatically.
- Each user/tenant has their own credential; the MCP sends the appropriate credential ID with each request so calls are isolated per connection.
- On disconnect, that credential is no longer used and calendar tools will not be available for that user until they reconnect Google Calendar.
Required scopes
https://www.googleapis.com/auth/calendar
https://www.googleapis.com/auth/calendar.events
https://www.googleapis.com/auth/calendar.settings.readonly
| Scope | Purpose |
|---|
| calendar | Query and display calendars, list/create/update events, get next event. |
| calendar.settings.readonly | Query and display user settings (timezone, week start day) so date/time answers match the user’s preferences. |
Connection required: Users must connect Google Calendar in Alysio before calendar tools work. If the connection is missing or expired, they may need to re-authorize in Settings → Integrations.
The Google Calendar MCP exposes the following tools. Users can invoke these capabilities through natural language in Alysio.
| Tool | Description | Example user prompts |
|---|
get_google_calendar | Returns details for a specific calendar (e.g. primary). | ”What’s my primary calendar?”, “Show my Google calendar details.” |
google_calendar_get_user_settings | Returns the user’s calendar settings (timezone, week start day, locale, etc.). | ”What’s my calendar timezone?”, “When does my week start?” |
google_calendar_list_events | Lists events from a calendar in a given time range, with optional ordering and limit. | ”What’s on my calendar this week?”, “List my meetings between Monday and Friday.” |
google_calendar_get_event | Returns full details for a single event by calendar and event ID. | ”Get details for event abc123”, “Show me that meeting.” |
google_calendar_create_event | Creates a new event on the specified calendar (summary, start/end, optional description, location, attendees). | ”Schedule a call tomorrow at 2pm for an hour”, “Create a meeting with Jane next Tuesday 10–11am.” |
google_calendar_update_event | Updates an existing event (e.g. title, time, location, description). | ”Move my 2pm meeting to 3pm”, “Change the title of event abc123 to ‘QBR’.” |
google_calendar_get_next_event | Returns the single next upcoming event from a calendar after the current time. | ”What’s my next meeting?”, “What’s coming up next on my calendar?” |
App Behavior
- API calls are made on-demand only when the user asks something that requires calendar data or an action (e.g. list events, create/update event). There is no background sync; each request triggers the relevant Google Calendar API call using the user’s OAuth credential.
Example flow
- User asks: “What’s on my calendar this week?”
- Alysio routes the request to the Google Calendar MCP.
- The MCP may call
google_calendar_get_user_settings to get timezone/week start, then google_calendar_list_events with the appropriate time_min/time_max for “this week.”
- The request is sent to the Google Calendar API using the user’s stored OAuth credential.
- The MCP returns the event list; Alysio presents the answer in chat (e.g. in the user’s timezone).
Troubleshooting
Common issues
- Missing or expired connection — User sees errors or no calendar data. Fix: Reconnect Google Calendar in Settings → Integrations (re-authorize with Google).
- 401 Unauthorized — Token invalid or revoked. Fix: Re-authorize the integration in Settings → Integrations.
- 403 Forbidden — Often due to insufficient OAuth scopes. Fix: Ensure the Google Calendar integration is configured with the required scopes (e.g.
calendar, calendar.settings.readonly).
- Wrong timezone or week range — Fix: Alysio uses
google_calendar_get_user_settings for timezone and week start; if settings are wrong, the user should correct them in their Google Calendar settings.
Support
