MCP Headless Gmail Server

Created By
baryhuanga year ago
A MCP (Model Context Protocol) server that provides get, send Gmails without local credential or token setup.
Overview

What is MCP Headless Gmail Server?

MCP Headless Gmail Server is a server that allows users to send and receive Gmail messages without the need for local credentials or token setup, utilizing the Model Context Protocol (MCP).

How to use MCP Headless Gmail Server?

To use the server, clone the repository, install dependencies, and run the server. You can also configure it to work with Docker or other MCP clients like Claude.

Key features of MCP Headless Gmail Server?

  • Headless operation without local file access.
  • Decoupled architecture for credential management.
  • Focused functionality for Gmail access only.
  • Docker-ready for easy deployment.
  • Automatic token refresh handling.

Use cases of MCP Headless Gmail Server?

  1. Sending automated marketing emails.
  2. Retrieving recent emails for analysis.
  3. Integrating Gmail functionality into other applications without local setup.

FAQ from MCP Headless Gmail Server?

  • Can I use this server without local credentials?

Yes! The server is designed to operate without local credential setup.

  • Is it necessary to use Docker?

No, Docker is optional; you can run the server directly in your environment.

  • How does token refreshing work?

The server automatically refreshes tokens when they expire, simplifying the authentication process.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
baryhuang
Star
23
Language
Python
License
MIT 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