Google Calendar
Connect AI agents and workflows to Google Calendar: create and update events, check availability, manage calendars and who can see them.
Book a demo
Google Calendar for AI agents and workflows.
engini lets your AI agents and workflows work in Google Calendar: create events in full or from a quick sentence, update and delete them, check people's availability, create and manage calendars, and control who can see a calendar. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.
Cursor, your code
audit log

in engini
What your agent can do in Google Calendar. Every tool is one you allow or leave out.
The Google Calendar tools in engini, grouped by what they change. Read tools are safe to hand out widely. Write and delete tools go only to the agents that need them.
Read
Read what is booked.
See when people are free.
Read calendars and who can see them.
Write
Book and change meetings.
Manage calendars.
Share a calendar.
Delete
Remove events, calendars or access.
Any endpoint
Call the Google Calendar API, with the sign-in added for you.
Triggers
There are no Google Calendar triggers. Start the workflow from another system or on a schedule.
Connect your AI agent to Google Calendar. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your Google Calendar connection and only the tools you choose. Add its address to your client and sign in through engini. There is no key to copy.
MCP client setup →Python and TypeScript
Hand your agent a toolset of Google Calendar tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.
SDK guide →For coding agents
The engini CLI connects Google Calendar and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.
CLI guide →Any language
Every Google Calendar tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.
API reference →.cursor/mcp.json. Claude Code: claude mcp add.// .cursor/mcp.json: Cursor, connected to Google Calendar through engini
{
"mcpServers": {
"engini-google-calendar": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your Google Calendar connection and the tools this agent may use, then paste its address. The client signs in through engini on first use. Claude, VS Code and other clients take the same address: see the MCP client setup guide.
Each request runs through the Google Calendar tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on Google Calendar. Agents and workflows, across systems.
Meetings booked from the CRM
When a deal reaches demo stage, find a slot and book it with the account's contacts.
Onboarding calls on close
A closed deal books the kickoff call with the customer and the CSM.
First-week schedule
A new hire's first-week meetings are booked from the HR record.
Scheduling in chat
An agent in Claude finds a time and books it. Its toolset holds the calendar tools it needs.
Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between Google Calendar and another system engini connects is available.
You decide what each agent may do in Google Calendar. engini enforces it on every call.
Only the tools you allow
A toolset lists the Google Calendar tools an agent may call and the connection each one uses. Give one agent read tools only and another the write it needs. engini refuses any call outside the toolset.
Scoped when you set them up
An MCP server exposes only the connections and tools chosen when it is created, and engini shows who uses each server.
Whose permissions apply
Connect a person's own Google Calendar account and engini acts as that person, with their Google Calendar permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.
Kept out of prompts
Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.
Every call on record
Every call lands in History and the audit log, which you can export or stream to your SIEM.
Test before production
Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.
Connect Google Calendar in three steps. Then decide what each agent may do.
Sign in to Google Calendar
Add a Google Calendar connection and sign in with your Google account, or use your own Google OAuth client.
Choose the tools
Add the connection to an MCP server or a toolset with only the tools each agent needs.
Build or ask
Use the connection as a step in a workflow, or ask your agent to work in Google Calendar from Claude, ChatGPT, Cursor or your own code.
Google Calendar and engini. Straight answers.
Can an AI agent write to Google Calendar, or only read?
Both. engini has tools to create, update and delete events and calendars and to manage who can see a calendar. Whether a given agent may use them is up to you: give it a toolset or an MCP server with read tools only, and it cannot call the rest.
Does the agent act as me in Google Calendar?
It acts as the Google account behind the connection, with that account's calendars. Every run is recorded under the person who started it.
What if the tool I need is not listed?
Use Send API Request to call any Google Calendar API endpoint through the same connection, and give it only to the agents that need it.