6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Google's own Calendar server: list calendars, read and search events, check availability, create, update, delete or…
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
Google's own remote MCP server puts a Google Calendar account behind an AI assistant. Its nine tools list calendars, read and search events, and find times that work across several people. Four of them act: they create, update, delete and RSVP to events. One is annotated destructive, and the consequential ones reach other people's calendars.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Returns events on the given calendar matching all specified constraints. Time constraints should not be specified unless requested by the user. For open-ended keyword or topic-based searches on the primary calendar, the search_events tool must be used instead.
Returns a single event on the given calendar.
Returns the calendars this user has access to (their calendar list). Use this tool to resolve calendar identifying data (for example, 'my family calendar') into its corresponding `calendar_id` (email identifier)
Suggests time periods across one or more calendars.
Creates an event on the given calendar.
Updates an event on the given calendar.
Deletes an event on the given calendar.
Responds to an event on a calendar.
Searches events on the user's primary calendar using semantic search.
Read from the server on 2026-08-18, including each tool's own safety annotations.
delete_event cancels a meeting you organised for every attendee, and with notificationLevel unset it emails them all. This is the one tool that should never sit behind blanket auto-approval, and the four documented read-only scopes are the cleanest way to make it unreachable.notificationLevel as ALL. Set it explicitly, or accept that every change an agent makes sends mail to attendees including external ones.update_event can uninvite people while annotated non-destructive. removedAttendeeEmails removes attendees; overrideReminders replaces all existing reminders rather than adding to them. Neither is covered by the destructive flag.create_event, update_event, delete_event and respond_to_event in the same page's Tool reference. Both the live descriptor and Google's per-tool pages require calendar.events for those four. We did not test the failure, because testing it would mean calling a writing tool.search_events is primary-calendar only. Its schema accepts no calendarId, so semantic search cannot reach a shared or secondary calendar; only list_events with fullText can, and that is literal AND matching rather than semantic.respond_to_event cannot counter-propose, reaching accepted, tentative and declined and nothing else. And responseStatus is an unconstrained string: unlike every other constrained field here, its valid values appear only in prose, with no JSON Schema enum a client can validate against.search_events. Its Tool reference lists eight tools; the live server returns nine, and Google's own MCP reference index publishes a page for all nine.calendar.acls and calendar.settings.readonly among its twelve scopes, so the token can carry more authority than today's tools exercise.schedule_meeting and analyze_availability among five prompt_names. A live prompts/list on 2026-08-18 returned an empty array, though the server does declare a prompts capability.tools/list, which returns tool definitions and no events, plus one unauthenticated tools/call of the zero-argument read-only list_calendars purely to observe the gate. It returned HTTP 401 and no data. No authenticated call was made and no event was ever read, created, changed, deleted or responded to.Exactly one of the nine: delete_event. Google annotates it destructiveHint true, idempotentHint true, readOnlyHint false. It removes an event from the calendar named in calendarId, defaulting to your primary calendar. No tool on this server restores a deleted event, and none reports what an event contained before deletion.
Yes, when you organised it. Google Calendar stores one event with copies on each attendee's calendar, so deleting an event you own removes it for every attendee. The schema makes this worse by default: notificationLevel is documented as defaulting to ALL, so deletion also emails a cancellation to everyone invited.
Yes. respond_to_event sets your response status to accepted, tentative or declined, and takes an optional responseComment that other attendees can read. It cannot propose a new time — Calendar's counter-proposal feature is absent from the tool surface. Google annotates it destructiveHint false, which is true of your data and silent about the social signal.
suggest_time requires an attendeeEmails array and finds free slots across those people's calendars. It reads whatever free/busy information each address already shares with your Google account, so it surfaces no more than Calendar's own scheduling view would. It is annotated read-only and requires no calendar-writing scope.
No. Google's setup page names three read-only scopes: calendar.calendarlist.readonly, calendar.events.freebusy and calendar.events.readonly. Google's own per-tool reference pages require calendar.events or calendar for create_event, update_event, delete_event and respond_to_event. Consenting to the documented three yields a read-only deployment where the four writing tools fail on authorization.
Indirectly, and by default. Four tools take a notificationLevel enum whose unspecified value Google documents as treated as ALL, meaning every attendee is emailed. Setting NONE suppresses it and EXTERNAL_ONLY narrows it. An agent that never sets the parameter mails everyone on every create, update, delete and RSVP.
Yes, plus a Google Cloud project. Google states you need a Claude Enterprise, Pro, Max or Team plan and must add the server as a custom connector with your own OAuth client ID and secret. You separately enable the Google Calendar API and the Google Calendar MCP API. It is a Developer Preview feature, not a one-click install.
search_events, which the setup page's Tool reference omits · retrieved 2026-08-18https://developers.google.com/workspace/calendar/api/v3/reference/mcp/tools_list/ (retrieved 2026-08-18; pages last updated 2026-07-17). All nine returned HTTP 200, each publishing that tool's Tool Annotations and Authorization Scopes. Every annotation matched the live handshake exactly, and every scope list matched the wire descriptor exactly. Source for the per-tool scope table above · retrieved 2026-08-18calendar, calendar.events, calendar.events.readonly and calendar.events.freebusy. The page does not classify scopes as sensitive or restricted, so neither does this page · retrieved 2026-08-18tools/list handshake against https://calendarmcp.googleapis.com/mcp/v1 — 9 tools with descriptions, JSON Schemas and safety annotations (2026-08-18, HTTP 200). Source for every tool name, annotation state, parameter default and enum quoted above. No tool was called against any calendar · retrieved 2026-08-18initialize against the same endpoint (2026-08-18, HTTP 200) — protocol 2025-06-18, serverInfo name StatelessServer version ESF. Neither field names Calendar; ESF is Google's shared API-serving frontend, also present in the server: header of unrelated 404s on this host, so it is not evidence about the product. A live prompts/list the same day returned an empty array against the directory's five advertised prompt names · retrieved 2026-08-18tools/call of list_calendars — the only zero-argument, read-only, idempotent tool on the server — against the same endpoint (2026-08-18). Returned HTTP 401 with a WWW-Authenticate: Bearer header naming a per-tool resource_metadata URL, and no data. The 401 arrived inside a JSON-RPC result with isError: true rather than as an error member, so only the HTTP status reports it correctly. This is what sets authVerified: the server demonstrated the gate rather than a document asserting it · retrieved 2026-08-18https://calendarmcp.googleapis.com/.well-known/oauth-protected-resource/mcp/v1 (HTTP 200 on 2026-08-18). Names https://accounts.google.com/ as authorization server, header bearer methods and twelve supported scopes. The root form and the path-prefixed form both returned HTTP 404 the same day, so only the path-suffixed form exists. Per-tool descriptors under the same prefix returned HTTP 200 for all nine real tool names and HTTP 404 for a fabricated one · retrieved 2026-08-18https://calendarmcp.googleapis.com/mcp/v1 endpoint, streamable-http transport, auth_required posture, Google as author, and nine tool names matching the live server exactly) · retrieved 2026-08-16https://developers.google.com/robots.txt (retrieved 2026-08-18, HTTP 200) — User-agent: * with a single Disallow: /youtube/partner/, and no Content-Signal line of any kind. Every documentation path cited above is permitted. https://developers.google.com/llms.txt returns HTTP 404 · retrieved 2026-08-18https://calendarmcp.googleapis.com/.well-known/mcp/server-card.json returned HTTP 404, so no server card corroborates the tool list · retrieved 2026-08-18Connect Google Calendar once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.