Google Calendar MCP server for your AI

Yes. Create an OAuth client in a Google Cloud project that has the Google Calendar API enabled, then paste the OAuth Client ID and OAuth Client Secret into the connect form. From there you authorize once on Google's own consent screen, so PopMCP never sees your Google password.

That happens when your Google Cloud project's Audience is set to External and the app has not been published. Google expires the authorization after 7 days in that state, and the connection goes dead with it. Publish the app before you connect, or publish and then reconnect if it has already lapsed.

There is no calendar to pick during setup. The connection reaches every calendar the Google account you authorize with can reach, and defaults to that account's own calendar. To narrow it, authorize with an account that only has the access you want to give. One extra limit worth knowing: transfer_calendar_ownership only moves a secondary calendar between users inside the same Google Workspace organization.

Yes. list_event_instances expands a recurring series into its individual occurrences, so the agent can pin down the specific standup or check-in you meant. update_event then makes the change to the occurrence it found.

create_event_with_meet books the event and attaches the Meet link in a single call, and it is what the agent should reach for whenever you say video call, Meet, virtual, remote or online. For a meeting that is already on the calendar, add_google_meet_to_event attaches the link and leaves everything else about the event untouched.

Changes to a watched calendar, to the account's calendar list, to sharing, and to settings such as time zone or working hours arrive as webhooks. Event-level changes are polled instead: event created, updated, rescheduled or cancelled, attendee responded, guest list changed, meeting link added, event starting soon, and out-of-office or focus-time blocks.

No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.

Any client that supports a remote Streamable HTTP MCP server — Claude Desktop, Claude Web, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.

Loading 42 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 26-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. You can switch a connection to the full catalog at any time.

A tool is something your AI calls — there are 42 here. A trigger is something PopMCP watches for you: 16 Google Calendar events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into Google Calendar.