Enhanced Gmail MCP Server

Created By
theposcha year ago
A Gmail MCP server
Overview

What is Enhanced Gmail MCP Server?

The Enhanced Gmail MCP Server is a powerful Model Context Protocol (MCP) server designed for Gmail integration, enabling AI assistants to manage emails through natural language.

How to use Enhanced Gmail MCP Server?

To use the server, clone the repository, set up a virtual environment, install the package, and configure it with your Google Cloud credentials.

Key features of Enhanced Gmail MCP Server?

  • Complete email management including sending, reading, and organizing emails.
  • Draft management for creating and editing email drafts.
  • Advanced label management for organizing emails with custom labels.
  • Powerful search and filtering capabilities for efficient email retrieval.
  • Archive management to keep your inbox organized without deleting emails.

Use cases of Enhanced Gmail MCP Server?

  1. Automating email responses using AI.
  2. Organizing emails by creating and applying labels.
  3. Searching for specific emails using advanced queries.
  4. Managing drafts for later review and sending.

FAQ from Enhanced Gmail MCP Server?

  • Can I use this server with any email account?

No, it is specifically designed for Gmail accounts with the Gmail API enabled.

  • Is there a cost associated with using the Enhanced Gmail MCP Server?

The server itself is free to use, but you may incur costs from Google Cloud services.

  • What programming language is used for this project?

The server is written in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
theposch
Star
0
Language
Python
License
GPL-3.0 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