Gmail MCP Server

Created By
christo707a year ago
Gmail MCP Server using Java and Spring Boot
Overview

what is Gmail MCP Server?

Gmail MCP Server is a Spring Boot application that implements the Model Context Protocol (MCP) for Gmail, allowing users to interact with their Gmail accounts programmatically.

how to use Gmail MCP Server?

To use the Gmail MCP Server, clone the repository, configure your Gmail API credentials, build the project using Maven, and run the server. You can also test the server functionality using the provided ClientStdio client.

key features of Gmail MCP Server?

  • GMailer Tools: Functions to manage emails such as sending, reading, marking as read, and moving to trash.
  • ClientStdio: A client for testing the MCP server functionality via standard input and output.

use cases of Gmail MCP Server?

  1. Automating email management tasks like sending and organizing emails.
  2. Building applications that require email notifications or interactions.
  3. Testing and developing features that integrate with Gmail.

FAQ from Gmail MCP Server?

  • What are the prerequisites for running the server?

You need Java 17 or higher, Maven, and Gmail API credentials.

  • Is there a client provided for testing?

Yes, the ClientStdio class is included for testing the MCP server functionality.

  • What license is the project under?

The project is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
christo707
Star
0
Language
Java
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