LabscoMCP early access ↗
quinnjrMCP SERVER

Google MCP

Twelve Google products — Gmail, Calendar, Drive, Docs, Sheets, Slides, Forms, Chat, Meet, Contacts, Tasks, YouTube — behind one desktop OAuth login.

by quinnjr ↗Office Suites & Cloud File StorageCommunity

LABSCO SUMMARY

One authorisation, and the whole Google surface is in reach.

Most Google servers pick a lane — mail, or calendar, or drive. This one covers twelve products with the same desktop OAuth client, so an agent can read a thread, find the file it mentions, book the follow-up and write the notes without a second login. The breadth costs you a Google Cloud project of your own: you enable the APIs and create the OAuth client before anything works.

What it is

One MCP server for a personal Google account, spanning twelve products: Calendar, Docs, Sheets, Slides, Drive, Gmail, Contacts, YouTube, Tasks, Forms, Chat and Meet. You authorise once as a desktop OAuth client and every service is reachable from the same session.

What you get

  • Mail that can be worked, not just read — gmail_search, gmail_get_thread, gmail_send, gmail_reply, gmail_trash, plus label and read-state changes
  • Calendar in both directions: calendar_list_events, calendar_create_event, calendar_update_event, natural-language entry via calendar_quick_add, and availability from calendar_get_freebusy
  • Drive as a working filesystem — drive_search, drive_upload_file, drive_download_file, drive_move_file, drive_copy_file, drive_create_folder
  • Document editing rather than document listing: docs_insert_text, docs_replace_text, sheets_read, sheets_update, sheets_append, slides_add_slide, slides_replace_text
  • Meet after the meeting — meet_list_conference_records, meet_list_participants, meet_list_recordings, meet_get_transcript, meet_list_transcript_entries
  • Forms and Chat: build a form and read its answers with forms_add_question and forms_list_responses; post and manage rooms with chat_send_message, chat_list_spaces, chat_add_member
  • Note-taking through Google Tasks — notes_create, notes_list, notes_update sit on the Tasks API, because Google Keep has no official public API

Requirements

A Google account plus your own Google Cloud project with the twelve APIs switched on, and a Desktop-app OAuth client whose downloaded JSON you save as credentials.json in the per-platform config directory (~/Library/Application Support/google-mcp on macOS, ~/.config/google-mcp on Linux, the roaming app-data folder on Windows). It is published on npm as @pegasusheavy/google-mcp (version 1.0.2, binary google-mcp) and runs with npx; the client configurations the project documents instead point node at a clone built with pnpm install and pnpm build. On first use call the google_auth tool once; the refreshable token is cached beside the credentials as tokens.json.

Setup effort

One command, then sign in — npx -y @pegasusheavy/google-mcp, then approve the OAuth sign-in