AVA
Allows creating Gmail drafts via the Gmail API, enabling AI agents to generate email content without sending.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@AVA draft an email to carllos@example.com about the project update"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
AVA MCP Server – Gmail Draft Tool
This project implements a minimal Model Context Protocol (MCP) server named AVA, exposing a single tool: write_email_draft.
The tool creates Gmail drafts from structured input, allowing AI agents like Claude to generate email content safely — without sending anything. This enables reviewable automation for follow-ups, summaries, or outreach.
It integrates with the Gmail API using OAuth2 authentication, ensuring secure access and user control. The server responds with metadata including the draft ID, making it ideal for real-world AI workflows.
Architecture Overview
Claude AI → MCP Tool Call → AVA Server → Gmail API → Draft Created
┌────────────────────────────┐
│ Claude AI │
│ (MCP client) │
└────────────┬───────────────┘
│ Tool Call: write_email_draft
▼
┌────────────────────────────┐
│ MCP Server (AVA) │
│ mcp-server-draft.py │
│ └── gmail.py │
│ └── .env config │
└────────────┬───────────────┘
│ Uses credentials from .env
▼
┌────────────────────────────┐
│ Gmail API (OAuth2 Auth) │
│ via Google Cloud Console │
│ Project: ava-mcp-475222 │
└────────────┬───────────────┘
│ Creates draft
▼
┌────────────────────────────┐
│ Gmail Draft Created │
│ │
└────────────────────────────┘Claude AI: Sends structured tool calls via MCP
AVA Server: Receives calls, loads credentials from
.env, and handles logic viagmail.pyGoogle Cloud Console: Hosts OAuth2 credentials (
credentials.json)Gmail API: Creates draft and returns metadata
Related MCP server: Gmail MCP Server
Features
MCP-compliant server using
FastMCPGmail API integration via OAuth2
Secure credential handling via
.envCompatible with Claude and MCP Inspector
Project Structure
mcp-email-draft/
├── .env # Gmail credentials and sender email
├── mcp-server-draft.py # MCP server exposing the tool
├── gmail.py # Gmail API logic
├── pyproject.toml # Project metadata and dependencies
├── credentials.json # OAuth2 client credentials
├── token.json # Gmail API token
├── README.md # DocumentationSetup Instructions
1. Create project folder
cd C:/Users/carll/Desktop
mkdir mcp-email-draft
cd mcp-email-draft2. Install uv
curl -Ls https://astral.sh/uv/install.sh | sh3. Install dependencies
uv pip install -r pyproject.tomlOr manually:
uv pip install google-api-python-client google-auth-oauthlib python-dotenv mcp[cli]Gmail API Setup
Go to Google Cloud Console
Create OAuth credentials for a desktop app
Download
credentials.jsonand place it in the project rootRun the server once to trigger OAuth flow and generate
token.json
.env File
USER_EMAIL=carlloswattsnogueira@gmail.com
GOOGLE_CREDENTIALS_PATH=C:/Users/carll/Desktop/mcp-email-draft/credentials.json
GOOGLE_TOKEN_PATH=C:/Users/carll/Desktop/mcp-email-draft/token.jsonClaude Integration
Go to Claude Connectors and use:
{
"mcpServers": {
"AVA": {
"command": "C:/Users/carll/.local/bin/uv.exe",
"args": [
"--directory",
"C:/Users/carll/Desktop/mcp-email-draft",
"run",
"mcp-server-draft.py"
]
}
}
}Usage Example
{
"recipient_email": "carllos@example.com",
"subject": "Follow-up on our meeting",
"body": "Hi Carllos, thank you again for your time today. Looking forward to the next steps!"
}Claude will return the Gmail draft ID and metadata. Next: Using Discord
License
This project is for demonstration and evaluation purposes only.
No affiliation with Google or Anthropic.
Available Tools
1 toolwrite_email_draftC
Create a Gmail draft using recipient, subject, and body.
Inputs: recipient_email (required), subject (required), body (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap. The purpose is uniquely defined.
The single tool name 'write_email_draft' follows a clear verb_noun pattern, demonstrating internal consistency.
A single tool is borderline; while it performs a concrete task, the server feels overly thin for anything beyond a very narrow use case.
The tool only creates a draft with no support for listing, updating, deleting, or sending, leaving significant gaps in email management.
Maintenance
Related MCP Connectors
Manage Gmail end-to-end: search, read, send, draft, label, and organize threads. Automate workflow…
Let AI agents send email from your own Gmail, Microsoft 365 or SMTP inbox, with guardrails.
Manage Gmail messages, threads, labels, drafts, and settings from your workflows. Send and organiz…
Email inboxes and calendars for AI agents: send, receive, search, draft and schedule.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Gmail by reading unread emails with automatic classification, creating AI-generated draft replies, and saving drafts directly to Gmail through the Gmail API.298 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Gmail through OAuth2 authentication, allowing users to list, search, read emails, and create drafts with a safety-first design that prevents accidental sends by default.298 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to create Gmail drafts and append content to Google Docs, supporting automated review analysis and notification workflows.537 npmMIT
- AlicenseAqualityBmaintenanceEnables creating Gmail drafts through a single tool, returning draft URLs for the owner to review and send manually.112 npmMIT