Gmail Server for Model Context Protocol (MCP)

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Gmail Server for Model Context Protocol (MCP)?

This project is a server that integrates with Gmail to enable functionalities such as sending, removing, reading, drafting, and responding to emails through the Model Context Protocol (MCP).

how to use Gmail Server for MCP?

To use this server, set up the Gmail API, authenticate your application, and configure it to work with an MCP client. Follow the setup instructions provided in the documentation to integrate it with your application.

key features of Gmail Server for MCP?

  • Send emails to specified recipients.
  • Remove emails by moving them to trash.
  • Mark emails as read.
  • Retrieve unread emails.
  • Read specific email content.
  • Open emails in a browser.

use cases of Gmail Server for MCP?

  1. Automating email responses in applications.
  2. Managing email workflows in desktop applications.
  3. Integrating email functionalities into custom software solutions.

FAQ from Gmail Server for MCP?

  • What is the purpose of this server?

It allows MCP clients to interact with Gmail for various email operations.

  • Is there a specific setup required?

Yes, you need to set up a Google Cloud project and enable the Gmail API.

  • Can this server be used with any MCP client?

Yes, as long as the client is configured correctly to communicate with this server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
Python
License
GPL-3.0 license

Recommend Servers

View All
Voyei

3 hours ago
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.

13 hours ago