Skip to Content
Connect Claude to Google Workspace with MCP
Connect Claude to Google Workspace with MCP

Use Claude with Gmail, Calendar, Drive-adjacent workflows, and Google Tasks through MCP. Pick the right server, copy a starter config, and understand the OAuth and local-file risks before connecting.

First Tool Call Help
Connect Claude to Google Workspace with MCP

Connect Claude to Google Workspace with MCP

If your goal is “let Claude work with my Gmail, calendar, or task workflows without manually hopping across apps,” this is the shortest path.

ServerBest forNot ideal whenAuthPermission risk
MCP GSuite ServerGmail + Calendar in one setup, multi-account workflows, attachment savingYou only need a simple task list integrationOAuth2 client files + account metadataHigh
MCP Google Tasks ServerTask-list CRUD with explicit env-based OAuth configYou want one server for mail and calendar tooGoogle OAuth client ID / secretMedium
GTasks MCPLightweight Google Tasks setup with Desktop App configYou need Gmail, Calendar, or broader Workspace coverageOAuth Desktop App fileMedium

Quick selection (30 seconds)

  • Pick MCP GSuite if you need Gmail and Calendar in the same Claude workflow.
  • Pick MCP Google Tasks Server if task automation is the main job and you are comfortable with explicit env vars.
  • Pick GTasks MCP if you want the smallest Google Tasks-only integration path.

Copy-paste config (Claude Desktop)

This is the most practical starting point if your immediate need is Gmail plus Calendar.

{
  "mcpServers": {
    "mcp-gsuite": {
      "command": "uvx",
      "args": [
        "mcp-gsuite",
        "--accounts-file",
        "/absolute/path/to/.accounts.json",
        "--credentials-dir",
        "/absolute/path/to/credentials"
      ]
    }
  }
}

For mcp-gsuite, keep a .gauth.json file nearby with your OAuth client configuration and start with only the accounts you actually need in .accounts.json.

Authentication and file checklist

ItemRequiredSensitiveNotes
.gauth.json or Google OAuth client configYesYesNeeded for mcp-gsuite OAuth initialization
.accounts.jsonYes for mcp-gsuiteYesList only the accounts Claude should know about
Credentials directoryYesYesStores refresh-token material after first login
Gmail / Calendar scopesYes for mcp-gsuiteYesAvoid adding broader scopes than needed
Tasks API OAuth credentialsYes for task-only serversYesUsed by mcp-googletasks and gtasks-mcp

First tool-call prompts

  • “Retrieve my latest unread messages and summarize only the ones that need a reply.”
  • “Check my agenda tomorrow and flag conflicts longer than 30 minutes.”
  • “List all open tasks in my default Google Tasks list and group them by due date.”

Risk and permission notes

  • OAuth scopes are the real permission boundary here. Start narrow and expand only if a real workflow needs it.
  • Auth files and credential caches should stay outside your repo and sync folders.
  • Gmail and Calendar access can expose sensitive personal or company data, so test with a low-risk account first.
  • If you only need tasks, do not grant full mail and calendar scopes just because one server supports them.

FAQ

Which server should I use for Gmail and Google Calendar together?

Start with MCP GSuite Server because it covers both in a single setup and already supports multiple Google accounts.

What about Google Drive?

This site’s current Workspace coverage is strongest for Gmail, Calendar, and Tasks. If Drive is your primary requirement, keep the page title/user intent clear and verify the exact Drive capability before granting broader Google scopes.

How do I reduce Google Workspace risk fastest?

Use a test account first, limit scopes to the workflow you need, and store OAuth files outside the project directory.

Sources and freshness

  • Sources: official server pages linked above.
  • Updated: March 15, 2026.
Last updated on