This exists for a specific worry: once an agent can create events it can normally also delete them, because Google's scopes do not separate the two. Removing the tools is the blunt fix, and it means an agent using this can add to a calendar but never quietly clear it. Mail is not restricted the same way, and it can send.
A Gmail and Google Calendar server on OAuth. It is a variant of the Google Workspace server with the calendar update and delete tools removed, because Google's Calendar API has no scope that permits creating events without also permitting deleting and updating them.
- Recent inbox mail listed with optional filtering (list_emails)
- Advanced search using Gmail query syntax (search_emails)
- New mail sent, with CC and BCC support (send_email)
- Labels changed: archive, trash, mark read or unread (modify_email)
- Upcoming calendar events listed, with date-range filtering
- Calendar events created, with attendees
- No calendar update and no calendar delete: both were removed on purpose
Node.js, and a Google Cloud project with the Gmail API and Google Calendar API enabled. Create OAuth credentials of type Web application, list the server's local callback address among the authorised redirect URIs, and save them as credentials.json in the project root. Smithery can install it for Claude Desktop in one command.
One command plus a key — npx -y @smithery/cli install @erickva/google-workspace-mcp-server-no-calendar-deletetion --client claude, then supply credentials