Gmail MCP Server

Created By
aniket-raskar1a year ago
Overview

What is Gmail MCP Server?

The Gmail MCP Server is a Python-based package that integrates Gmail and Google Calendar with Claude Desktop, allowing users to manage their emails and calendar events through natural language commands.

How to use Gmail MCP Server?

To use the Gmail MCP Server, install the package via pip, ensure you have the necessary prerequisites, and run it as a background server to interact with your Gmail and Google Calendar.

Key features of Gmail MCP Server?

  • Email summarization for recent emails.
  • Sending emails directly from Claude Desktop.
  • Creating calendar events for important emails.
  • Automatic scheduling of calendar events based on email importance.
  • Secure authentication using OAuth 2.0.
  • Cross-platform support for Windows, macOS, and Linux.

Use cases of Gmail MCP Server?

  1. Automating email management tasks.
  2. Streamlining event scheduling based on email content.
  3. Enhancing productivity by using natural language commands to interact with Gmail and Google Calendar.

FAQ from Gmail MCP Server?

  • What are the prerequisites for using the Gmail MCP Server?

You need Python 3.8 or higher, Claude Desktop, a Google Cloud Project with the necessary APIs enabled, and a Gmail account.

  • Is the Gmail MCP Server free to use?

Yes, it is free to use as it is an open-source project.

  • How does the server ensure secure access to Gmail?

It uses OAuth 2.0 for secure authentication.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aniket-raskar1
Star
1
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.

16 hours ago