Skip to main content
Glama
Google Calendar - No deletion

Google Calendar - No deletion

by erickva

Google Workspace MCP Server

A Model Context Protocol (MCP) server that provides tools for interacting with Gmail and Calendar APIs. This server enables you to manage your emails and calendar events programmatically through the MCP interface.

Features

Gmail Tools

  • list_emails: List recent emails from your inbox with optional filtering

  • search_emails: Advanced email search with Gmail query syntax

  • send_email: Send new emails with support for CC and BCC

  • modify_email: Modify email labels (archive, trash, mark read/unread)

Calendar Tools

  • list_events: List upcoming calendar events with date range filtering

  • create_event: Create new calendar events with attendees

  • The events below were removed from this server for security measures since Google Cloud Calendar API does not have a scope that allows creation but prevents deletion or updates.

  • update_event: Update existing calendar events

  • delete_event: Delete calendar events

Related MCP server: google-workspace-mcp-server

Prerequisites

  1. Node.js: Install Node.js version 14 or higher

  2. Google Cloud Console Setup:

    • Go to Google Cloud Console

    • Create a new project or select an existing one

    • Enable the Gmail API and Google Calendar API:

      1. Go to "APIs & Services" > "Library"

      2. Search for and enable "Gmail API"

      3. Search for and enable "Google Calendar API"

    • Set up OAuth 2.0 credentials:

      1. Go to "APIs & Services" > "Credentials"

      2. Click "Create Credentials" > "OAuth client ID"

      3. Choose "Web application"

      4. Set "Authorized redirect URIs" to include: http://localhost:4100/code

      5. Note down the Client ID and Client Secret

Setup Instructions

Installing via Smithery

To install Google Workspace Server - No Calendar Deletion for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @erickva/google-workspace-mcp-server-no-calendar-deletetion --client claude

Installing Manually

  1. Clone and Install:

    git clone https://github.com/epaproditus/google-workspace-mcp-server.git
    cd google-workspace-mcp-server
    npm install
  2. Create OAuth Credentials: Create a credentials.json file in the root directory:

    {
        "web": {
            "client_id": "YOUR_CLIENT_ID",
            "client_secret": "YOUR_CLIENT_SECRET",
            "redirect_uris": ["http://localhost:4100/code"],
            "auth_uri": "https://accounts.google.com/o/oauth2/auth",
            "token_uri": "https://oauth2.googleapis.com/token"
        }
    }
  3. Get Refresh Token:

    node get-refresh-token.js

    This will:

    • Open your browser for Google OAuth authentication

    • Request the following permissions:

      • https://www.googleapis.com/auth/gmail.modify

      • https://www.googleapis.com/auth/calendar

      • https://www.googleapis.com/auth/gmail.send

    • Save the credentials to token.json

    • Display the refresh token in the console

  4. Configure MCP Settings: Add the server configuration to your MCP settings file:

    • For VSCode Claude extension: ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

    • For Claude desktop app: ~/Library/Application Support/Claude/claude_desktop_config.json

    Add this to the mcpServers object:

    {
      "mcpServers": {
        "google-workspace": {
          "command": "node",
          "args": ["/path/to/google-workspace-server/build/index.js"],
          "env": {
            "GOOGLE_CLIENT_ID": "your_client_id",
            "GOOGLE_CLIENT_SECRET": "your_client_secret",
            "GOOGLE_REFRESH_TOKEN": "your_refresh_token"
          }
        }
      }
    }
  5. Build and Run:

    npm run build

Usage Examples

Gmail Operations

  1. List Recent Emails:

    {
      "maxResults": 5,
      "query": "is:unread"
    }
  2. Search Emails:

    {
      "query": "from:example@gmail.com has:attachment",
      "maxResults": 10
    }
  3. Send Email:

    {
      "to": "recipient@example.com",
      "subject": "Hello",
      "body": "Message content",
      "cc": "cc@example.com",
      "bcc": "bcc@example.com"
    }
  4. Modify Email:

    {
      "id": "message_id",
      "addLabels": ["UNREAD"],
      "removeLabels": ["INBOX"]
    }

Calendar Operations

  1. List Events:

    {
      "maxResults": 10,
      "timeMin": "2024-01-01T00:00:00Z",
      "timeMax": "2024-12-31T23:59:59Z"
    }
  2. Create Event:

    {
      "summary": "Team Meeting",
      "location": "Conference Room",
      "description": "Weekly sync-up",
      "start": "2024-01-24T10:00:00Z",
      "end": "2024-01-24T11:00:00Z",
      "attendees": ["colleague@example.com"]
    }

3. Update Event:

{
  "eventId": "event_id",
  "summary": "Updated Meeting Title",
  "location": "Virtual",
  "start": "2024-01-24T11:00:00Z",
  "end": "2024-01-24T12:00:00Z"
}

4. Delete Event:

{
  "eventId": "event_id"
}

Troubleshooting

  1. Authentication Issues:

    • Ensure all required OAuth scopes are granted

    • Verify client ID and secret are correct

    • Check if refresh token is valid

  2. API Errors:

    • Check Google Cloud Console for API quotas and limits

    • Ensure APIs are enabled for your project

    • Verify request parameters match the required format

License

This project is licensed under the MIT License.

Available Tools

7 tools
create_eventC

Create a new calendar event

Inputs: end (required), start (required), summary (required), attendees, +2 more.

list_emailsB

List recent emails from Gmail inbox

Inputs: maxResults, query.

list_eventsC

List upcoming calendar events

Inputs: maxResults, timeMax, timeMin.

meeting_suggestionC

Suggest available meeting slots within the next 30 days

Inputs: bankHolidays, calendarIds, daysToSearch, meetingLengthMinutes, +4 more.

modify_emailA

Modify email labels (archive, trash, mark read/unread)

Inputs: id (required), addLabels, removeLabels.

search_emailsC

Search emails with advanced query

Inputs: query (required), maxResults.

send_emailC

Send a new email

Inputs: body (required), subject (required), to (required), bcc, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.6/5.0

    Scored across 7 tools

    Disambiguation2/5

    The tool set mixes calendar and email operations without clear boundaries, causing potential misselection. For example, 'list_emails' and 'search_emails' overlap in purpose for email retrieval, while calendar tools like 'create_event' and 'list_events' are distinct but the server's dual-domain focus creates confusion.

    Naming Consistency3/5

    Naming conventions are mixed, with some tools using verb_noun patterns like 'create_event' and others using noun_verb like 'meeting_suggestion'. While readable, the inconsistency in structure (e.g., 'modify_email' vs. 'send_email') deviates from a predictable pattern.

    Tool Count3/5

    With 7 tools, the count is reasonable, but it feels borderline due to the server's split focus on both Google Calendar and Gmail. This scope might be too broad for the limited tool set, leading to a thin coverage in each domain.

    Completeness2/5

    For the implied dual-domain purpose, there are significant gaps. In calendar, tools lack update or delete event operations, and in email, there's no way to delete emails or manage drafts. The server name suggests calendar focus, but email tools are included without full lifecycle coverage.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers