Advertise
MCP.so
Sign In

Gmail MCP Client Server

@karimdabbouz

Repository

Basic information

Category

Communication

Transports

stdio

Author

karimdabbouz

About Gmail MCP Client Server

MCP client and server to hook up Claude to Gmail.

#gmail#mcp#client-server

Gmail MCP Client Server config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Gmail MCP Client Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Gmail Mcp Client Server?

The Gmail Mcp Client Server is an MCP server that integrates with Gmail using OAuth authentication. It requires manual browser-based authentication to access a Gmail account. Designed for developers who need to connect MCP clients to Gmail.

How to use Gmail Mcp Client Server?

Run server.py once as a standalone script with a credentials.json file next to it. Authenticate via your browser; after success, the session is saved as token.pickle. Then use client.py to start the client and server with that pickle file. Obtain credentials.json from the Google Cloud Console using the linked guide.

Key features of Gmail Mcp Client Server

  • Manual OAuth authentication via browser
  • Session persists as a token.pickle file
  • Separate authentication and runtime scripts

Use cases of Gmail Mcp Client Server

  • —

Frequently asked questions

1

How do I obtain the required credentials file?

Follow the Google Gmail API guide at https://developers.google.com/gmail/api/quickstart/python to generate a `credentials.json` file.

2

Where is the authentication session saved?

After browser authentication, the session is saved as `token.pickle` in the root directory of the project.

3

Do I need to authenticate every time I start the server?

No, the `token.pickle` file stores the session; reuse it to skip re-authentication on subsequent runs.

4

Which files are required to run the server?

You need `credentials.json` (obtained once) and `token.pickle` (generated after first auth). The server provides `server.py` and `client.py`.

Comments

More Communication MCP servers

Mektup-mcp

WeeCi

Mektup gives AI agents and their humans a real email mailbox, not just a one-way sending API. Through 41 MCP tools, an agent can register a domain, create a mailbox, send and receive mail, and manage threads, drafts, fol

B2B Creators

Social Tree Global

Agencies and GTM teams use HeyReach and Instantly to run LinkedIn outbound from personal sender profiles — but those profiles sit empty and prospects don't accept. B2B Creators is the content layer that keeps every sende

R

RelayLink

RelayLink lets your AI assistant send briefings to other people's AI assistants. Draft a package from your current conversation, attach files, approve the note, and the recipient's AI gets the full context: decisions, op

gtm-api

gtm-api

MCP server and API for AI agents that work LinkedIn on accounts you own: search, connect, message and enrich, with limits enforced on our server.

SocialFaktory

SocialFaktory

Run a brand's social media from your agent: write posts in the brand's voice, generate short videos, schedule and publish to TikTok, Instagram, YouTube, X, LinkedIn, Facebook and Pinterest, and read the metrics back. 21

Advertise