MCP server to interact with Google products.

Example prompts

Right now, this MCP server supports Gmail and Calendar integration with the following capabilities:

1. General

   • Multiple Google accounts

2. Gmail

   • Get your Gmail user information
   • Query emails with flexible search (e.g., unread, from specific senders, date ranges, with attachments)
   • Retrieve complete email content by ID
   • Create new draft emails with recipients, subject, body and CC options
   • Delete draft emails
   • Reply to existing emails (can either send immediately or save as draft)
   • Retrieve multiple emails at once by their IDs
   • Save multiple attachments from emails to your local system

3. Calendar

   • Manage multiple calendars
   • Get calendar events within specified time ranges
   • Create calendar events with:
     • Title, start/end times
     • Optional location and description
     • Optional attendees
     • Custom timezone support
     • Notification preferences
   • Delete calendar events

Example prompts you can try:

• Retrieve my latest unread messages
• Search my emails from the Scrum Master
• Retrieve all emails from accounting
• Take the email about ABC and summarize it
• Write a nice response to Alice's last email and upload a draft.
• Reply to Bob's email with a Thank you note. Store it as draft
• What do I have on my agenda tomorrow?
• Check my private account's Family agenda for next week
• I need to plan an event with Tim for 2hrs next week. Suggest some time slots.

Configuration Options

The MCP server can be configured with several command-line options to specify custom paths for authentication and account information:

• --gauth-file: Specifies the path to the .gauth.json file containing OAuth2 client configuration. Default is ./.gauth.json.
• --accounts-file: Specifies the path to the .accounts.json file containing information about the Google accounts. Default is ./.accounts.json.
• --credentials-dir: Specifies the directory where OAuth credentials are stored after successful authentication. Default is the current working directory with a subdirectory for each account as .oauth.\{email\}.json.

These options allow for flexibility in managing different environments or multiple sets of credentials and accounts, especially useful in development and testing scenarios.