Gmail MCP server for Claude & ChatGPT

What it looks like

What does Gmail look like in Claude?

Connect Gmail once. Your agent reads the full thread history on the unified profile—and can send the next email—through one MCP server, identity-resolved with your CRM, support, and website events.

MCP

Gmail, exposed as MCP tools.

Claude · pathbound MCP connected

you

What did we last say to [email protected], and draft a follow-up I can send.

↳ get_contact_conversations { email: "[email protected]" } 6 threads · 420ms

gmail last reply: “send pricing” · 2d ago

hubspot deal_stage = presentation

tracker revisited /pricing today

↳ gmail_send_email { to: "[email protected]", draft: "…" } awaiting approval

status draft ready—not sent

claude

Your last exchange: she asked for pricing two days ago; the deal is at presentation and she revisited /pricing today. I’ve drafted the follow-up—want me to send it via Gmail?

review Sending is a write action—Pathbound surfaces the draft for approval before gmail_send_email fires.

claude_desktop_config.json

{
  "mcpServers": {
    "pathbound": {
      "url": "https://mcp.pathbound.ai/mcp"
    }
  }
}

Gmail tools out of the box · read & write

get_contact_conversations — full Gmail thread history on the unified profile

get_contact_timeline — emails alongside CRM, support, and web activity

list_contact_email_threads — browse threads for a contact

get_contact — unified profile across Gmail + your other sources

gmail_send_email — send the follow-up, drafted from full context

create_contact_note — log call recaps and research on the contact

…plus 20 more—26 MCP tools total, across contacts, companies, events, and conversations.

Setup

How do I connect Gmail to Claude?

OAuth with Google. Drop a snippet into your MCP client. Ask a question.

01

Sign up for Pathbound

Create an account at pathbound.ai. Free during public alpha.
02

Connect Gmail

In the dashboard, go to Integrations → Gmail → Connect. OAuth via Google’s official OAuth flow; Pathbound syncs threaded email history and matches each thread to the right contact. Reading is enabled by default; sending requires granting the send scope.
03
Add Pathbound to your MCP client

Drop the snippet below into your Claude Desktop config (or in Claude.ai web: Settings → Connected Apps → Add custom MCP → enter https://mcp.pathbound.ai/mcp). The same URL works for ChatGPT, Cursor, Cline, and any MCP client that supports OAuth.
claude_desktop_config.json
```
{
  "mcpServers": {
    "pathbound": {
      "url": "https://mcp.pathbound.ai/mcp"
    }
  }
}
```
04

Run a test prompt

Ask the agent: “Summarize my last email exchange with [email protected].” The agent calls get_contact_conversations via MCP and returns the thread.

Why Pathbound

The email thread is half the story. Pathbound has the other half.

A direct Gmail connector shows your agent an inbox. Pathbound shows your agent the customer—Gmail threads stitched together with your CRM, support, website events, and the rest of your stack—through one unified profile served over the Model Context Protocol.

Beyond the inbox

Email threads land on the same timeline as CRM deal stage, support tickets, and pricing-page visits. Your agent reads one profile, not five tabs.

Identity-resolved

The same person across Gmail ([email protected]), your CRM ([email protected]), and support resolves to one entity. A raw inbox connector only knows email addresses.

Send from full context

Agents don’t just read the thread—they can send the follow-up with gmail_send_email, drafted from the customer’s entire history and logged back on the timeline.

Built for LLMs

Token-efficient thread summaries instead of raw MIME. Agents get the gist and the latest message, not a 40-email dump that blows the context window.

FAQ

Common questions.

Is this an official Gmail MCP server?

Pathbound is an independent platform. We connect to Gmail via Google’s official OAuth flow and expose your data through one Model Context Protocol server alongside your other sources. Not affiliated with Google.

Can the agent send email, or just read?

Both. It reads threaded history onto the unified profile, and gmail_send_email lets an agent send a message drafted from the full customer context. Sends are a write action—connect with read-only scope if you only want the agent to read.

How is this different from the Gmail API?

The Gmail API is for backends and scheduled jobs. MCP is for AI agents—it’s the protocol Claude, ChatGPT, and Cursor speak. Pathbound’s MCP also unifies Gmail with your CRM, support tools, and website events into one profile per contact, so the agent doesn’t glue several APIs together itself.

Which MCP clients does this work with?

Claude.ai, Claude Desktop, Claude Code, ChatGPT (with custom connectors), Cursor, Cline, Continue—any client that supports the Model Context Protocol with OAuth.

How are emails matched to a contact?

By identity resolution. Each thread is matched to a unified contact by email address, so a person’s Gmail history lands on the same profile as their CRM record, support conversations, and web activity—even when the addresses differ.

How does authentication work?

Google OAuth 2.0. You authorize from the Pathbound dashboard; tokens are encrypted at rest, and you can disconnect anytime from Integrations → Gmail or revoke access from your Google Account’s security settings.

Is my customer data secure?

Tenant-isolated and OAuth-scoped per user, with encryption at rest via our infrastructure provider’s default configuration. GDPR-aligned; SOC 2 readiness in progress. Pathbound does not sell customer data, and we don’t call AI providers on your behalf—your MCP client does, under your account and the AI provider’s terms.

What about HubSpot, Pipedrive, Apollo, Intercom?

Same MCP server, same tools—just connect a different source. See the integrations directory.

Gmail with Claude & ChatGPT—Gmail MCP server