Gmail Mcp Client Server

Created By
karimdabbouza year ago
MCP client and server to hook up Claude to Gmail.
Overview

what is Gmail Mcp Client Server?

Gmail Mcp Client Server is a project designed to connect the Claude AI model to Gmail, allowing for enhanced email interactions and automation.

how to use Gmail Mcp Client Server?

To use the project, you need to authenticate with Gmail using OAuth. Run the server.py script with the credentials.json file, authenticate via your browser, and save the session as token.pickle. Then, you can start the client and server using the client.py file.

key features of Gmail Mcp Client Server?

  • Integration of Claude AI with Gmail for automated email handling.
  • OAuth authentication for secure access to Gmail.
  • Ability to run client and server scripts for email processing.

use cases of Gmail Mcp Client Server?

  1. Automating responses to emails using AI.
  2. Enhancing email management with AI-driven insights.
  3. Streamlining communication workflows through automation.

FAQ from Gmail Mcp Client Server?

  • How do I authenticate with Gmail?

You need to run server.py and follow the OAuth authentication process in your browser.

  • Is there a specific Python version required?

The project is developed in Python, and it is recommended to use Python 3.x.

  • Can I modify the client and server scripts?

Yes! The scripts are open for modification to suit your needs.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
karimdabbouz
Star
0
Language
Python
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago