Gmail MCP: Connect Gmail to Claude, ChatGPT and Cursor fast

TL;DR:

• Connecting Gmail to Claude, ChatGPT, or Cursor via the Model Context Protocol (MCP) typically requires:

  • A six-step Google Cloud Console setup.

  • Configuring an OAuth consent screen.

  • Managing OAuth tokens manually.

• Manual token management can lead to broken connections when access tokens expire.

• Composio simplifies the process by:

  • Providing a managed MCP gateway.

  • Handling OAuth authentication directly within the chat.

  • Persisting your connection after a single authentication.

• Composio's generous free tier includes:

  • 20,000 tool calls per month.

  • No credit card required.

• You can complete setup and start sending email replies or summarizing Gmail threads in a single session, whether you're using Claude, ChatGPT, or Cursor.

If you have ever tried to configure a Google Cloud OAuth consent screen just to summarize your inbox, you know exactly where this setup falls apart:

• OAuth redirect URI mismatches

• Invalid or missing OAuth scopes

• "Access denied" or "Needs vault" errors

• Empty resource or tool lists

• OAuth flows that never complete

• Client-specific authentication quirks

• Access tokens expiring mid-session

This guide shows you the fast path to a Gmail MCP connection. Using our managed MCP gateway, you can connect Gmail to Claude Desktop, ChatGPT, or Cursor with a single authentication click.

Setting up Gmail MCP through Google Cloud vs Community MCP Servers vs Composio

Your inbox holds most of the context your AI assistant currently can't reach: client threads, follow-up chains, invoices, meeting notes, and decisions buried in year-old threads. Without a Gmail connection, your AI can draft text but can't actually read, search, or send emails on your behalf.

Think of MCP as the nervous system connecting your AI's brain to your real work tools. The Model Context Protocol is the open standard that makes this possible. It lets AI models access external tools and data sources in a structured, permissioned way. The Gmail MCP server is the specific component that exposes your inbox as a set of callable actions.

Your integration options break down into three paths:

Native connectors require a Google Cloud project and CLI configuration before you can access any Gmail actions. Community MCP servers give you more control, but you own the token management. Composio handles the third path: full capability with no infrastructure to maintain.

Composio vs manual Gmail integration

Here's what the manual path actually looks like, step by step:

1. Google Cloud Console: Create a new project and navigate to the API library.
   
   

2. Enable Gmail API: Search for and enable the Gmail API under your project.
   
   

3. OAuth consent screen: Configure the consent screen under Google Auth Platform, set the branding, and add Gmail scopes under Data Access.
   
   

4. Client credentials: Create an OAuth 2.0 client ID, select "Web application," add authorized redirect URIs, and download the JSON credential file.
   
   

5. Local server deployment: Place the credential file on your machine, configure your MCP server to reference it, and start the local process.
   
   

6. Client integration: Add the local server path to your Claude Desktop or Cursor config file and restart the client.

Many community MCP servers require a local gcp-oauth.keys.jsoncredential file on your machine, a Google Cloud project, and a local auth script run per user before the connection works. Composio supports all 63 Gmail API methods, so you're not discovering capability gaps after setup.

Composio eliminates every one of those steps. You get a remote MCP server URL, authenticate your Gmail account once through a browser popup, and the connection is live. No local server, no key files, no terminal commands.

What you need for your Gmail MCP installation

Before you start, gather these items. The entire setup process depends on three things being in place.

• Gmail account

• AI client

• Composio account

Configuring Gmail for MCP access

Gmail requires explicit OAuth permission grants before any external tool can read or send email. Composio requests only the scopes your workflows actually need: reading messages, sending mail, managing labels, and accessing thread data. You review and approve these during the OAuth flow in your browser.

Personal Gmail accounts can approve this immediately. Google Workspace accounts are subject to admin-level API access controls. Your IT administrator must approve our client ID using the Google Admin Console API controls before the connection succeeds.

AI tools ready for Gmail MCP

All three major AI clients support MCP:

• Claude Desktop: Native MCP support via the claude_desktop_config.json file or the Connectors UI.

• ChatGPT: Custom GPT actions support OAuth-authenticated external APIs.

• Cursor: MCP server configuration under Settings > Features > MCP.

Each client handles tool calls differently, so expect varying integration patterns and response formats depending on which platform you choose.

Activating your free Composio access

Go to composio.dev and create an account. The free tier includes 20,000 tool calls per month with no credit card required. Once your account is live, navigate to the MCP section of your dashboard to find your unique MCP server URL. You'll use this URL in each of the three client setup steps below.

Connect Gmail to Claude Code

To connect Gmail to Claude Code using Composio:

1. Add the Composio MCP by generating the MCP URL in your terminal.
   
   

2. Start Claude Code by running the claude command.
   
   

3. Once Claude Code is open, access your MCP list by entering /mcp in the terminal.

4. From the list, select Composio and click Authenticate.
   
   

5. This will redirect you to the Composio OAuth authorization page, where you can complete the authentication process by granting the required permissions.
   
   

6. After authorization is complete, Gmail will be successfully connected to Claude Code through Composio.

Connect Gmail to ChatGPT via Composio

To connect Gmail to ChatGPT:

1. Enable Developer Mode by navigating to Settings > Apps > Advanced settings and turning on Developer Mode.
   
   

2. Click Create app and paste the Composio MCP server URL: https://connect.composio.dev/mcp.
   
   

3. After adding the MCP server, a browser window will automatically open, prompting you to sign in and authorize ChatGPT to access your Composio account.
   
   

4. Once the authorization process is complete, Composio tools will be available in ChatGPT chats and Deep Research.

To use them in a new conversation, click the + icon at the bottom of the chat, select More, and then choose Composio to enable the tools for that session. After connecting Gmail, you can perform tasks such as summarizing unread emails from the morning, creating draft replies to urgent messages, retrieving contact details for recent senders, and adding a "Follow Up" label to flagged emails.

Configure the Gmail MCP server for Cursor

To connect Gmail to Cursor using Composio, you can either install it with a single click using the "Install in Cursor" option or add it manually by updating your Cursor MCP configuration. To install manually:

1. Open .cursor/mcp.json in your project root (or ~/.cursor/mcp.json for a global configuration) and add a Composio server entry that points to https://connect.composio.dev/mcp.
   
   

2. After saving the configuration, restart Cursor and navigate to the MCP Tools settings, where you will see a Connect button next to Composio.
   
   

3. Clicking Connect will open a browser window and redirect you to the Composio authorization flow.
   
   

4. Once authorized, return to Cursor and ask the agent to connect to Gmail or perform any Gmail-related task, such as summarizing unread emails from this morning, creating draft replies to urgent messages, or fetching contact details for recent senders.
   
   

5. Cursor will prompt you to authenticate and grant Gmail access if needed.
   
   

6. After completing the authorization process, Composio tools will be available in Cursor and your Gmail account will be ready to use.

Expand your assistant with Gmail data

Streamline outgoing email workflows

With all 63 Gmail methods available, you can ask Claude, ChatGPT, or Cursor to draft and send replies directly. Try: "Reply to the most recent email from [sender] thanking them for the proposal and asking for a 30-minute call next week." The agent drafts the reply and either sends it or creates a draft for your review, depending on how you phrase the instruction.

Instant summaries for Gmail threads

Long email chains are where LLM synthesis earns its keep: an agent reading a long thread to surface one action item takes seconds, not minutes. Ask Claude: "Summarize this thread and tell me what decision was reached and what I'm expected to do next." Claude reads the full thread context and returns a concise summary with clear action items.

Set up automated follow-up flows

Where Gmail triggers are available in your Composio plan, you can configure event-driven workflows. Check out the supported tools & triggers for current trigger coverage.

Parse and ingest email content

Your AI assistant can extract structured data from email content: invoice amounts, meeting links, and deadlines. Ask: "Find all emails with 'invoice' in the subject from this month and extract the sender, amount due, and due date into a table." This replaces the manual work of opening each email and copying data into a spreadsheet.

Get started with Composio and securely connect your AI agents and chatbots (Claude, ChatGPT, Cursor, etc.) with Gmail MCP.

FAQs

What does Gmail MCP integration with Composio cost?

The free tier includes 20,000 tool calls per month with no credit card required. Paid plans start at $29 per month for 200,000 tool calls, with overage billed at $0.299 per 1,000 calls.

How secure is my Gmail data?

Composio is SOC 2 and ISO 27001 certified, with all data encrypted at rest and in transit. You control which Gmail scopes you grant and can revoke access at any time through your Google Account security settings or directly from the Composio dashboard.

How do I disconnect my Gmail account?

You can revoke access directly from your Composio dashboard. You can also revoke access independently by visiting your Google Account's connected apps settings and removing Composio from the list.

Can I use Gmail MCP with Google Workspace accounts?

Yes, but your Google Workspace administrator must first approve the Composio application in the Google Admin Console under the API controls section. Once approved, Workspace users connect through the same in-chat OAuth flow as personal Gmail users.

What are Gmail API usage limits?

Google enforces quota limits on the Gmail API to manage usage across all applications. Your Composio plan's monthly tool call quota is a separate limit set by Composio, not Google.

Key terms glossary

Model Context Protocol (MCP): An open standard that lets AI models securely access data and callable tools from external applications in a structured, permissioned way.

MCP server: A lightweight application that exposes specific tools and data sources to an AI client using the Model Context Protocol.

MCP gateway: A centralized managed layer, like Composio, that handles authentication, routing, and security for multiple MCP-connected services from a single endpoint.

Tool Router: Our routing layer that inspects incoming agent requests and directs them to the correct toolkit based on which services the user has authenticated, eliminating conditional logic in agent code.

OAuth 2.0: The authorization framework Gmail uses to grant external tools permissioned access to your inbox without exposing your password.