MCP Gmail Server

Created By
jeremyjordana year ago
A Model Context Protocol (MCP) server that provides Gmail access for LLMs, powered by the MCP Python SDK.
Overview

What is MCP Gmail Server?

MCP Gmail Server is a Model Context Protocol (MCP) server that provides Gmail access for Large Language Models (LLMs), utilizing the MCP Python SDK.

How to use MCP Gmail Server?

To use the MCP Gmail Server, set up your Gmail API access, install the necessary dependencies, and run the server. You can then connect to the server using any MCP client or Claude Desktop.

Key features of MCP Gmail Server?

  • Exposes Gmail messages as MCP resources.
  • Provides tools for composing, sending, and managing emails.
  • Supports OAuth 2.0 authentication with Google's Gmail API.

Use cases of MCP Gmail Server?

  1. Integrating Gmail functionalities into LLM applications.
  2. Automating email management tasks.
  3. Building custom email clients that leverage LLM capabilities.

FAQ from MCP Gmail Server?

  • What are the prerequisites for using MCP Gmail Server?

    You need Python 3.10+, a Gmail account with API access, and the uv package for Python package management.

  • Is there a detailed setup guide?

    Yes, the setup guide includes steps for creating a Google Cloud project, enabling the Gmail API, and configuring OAuth credentials.

  • Can I use this server for personal projects?

    Yes, MCP Gmail Server can be used for personal projects as long as you comply with Gmail API usage policies.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jeremyjordan
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.

8 hours ago