ClaudePost
Enables email functionality with Gmail accounts, supporting email search, reading email content with threading, viewing statistics, and composing/sending emails securely with TLS.
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., "@ClaudePost show me emails from yesterday"
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.
ClaudePost
A Model Context Protocol (MCP) server that provides a seamless email management interface through Claude. This integration allows you to handle emails directly through natural language conversations with Claude, supporting features like searching, reading, and sending emails securely.
Features & Demo
Email Search and Reading
📧 Search emails by date range and keywords
📅 View daily email statistics
📝 Read full email content with threading support
Email Composition and Sending
✉️ Send emails with CC recipients support
🔒 Secure email handling with TLS
Related MCP server: IMAP MCP Server
Prerequisites
Python 3.12 or higher
A Gmail account (or other email provider)
If using Gmail:
Two-factor authentication enabled
App-specific password generated
Claude Desktop application
Setup
Install uv:
# MacOS/Linux curl -LsSf https://astral.sh/uv/install.sh | sh # Remember to restart your terminal after installationClone and set up the project:
# Clone the repository git clone https://github.com/ZilongXue/claude-post.git cd claude-post # Create and activate virtual environment uv venv source .venv/bin/activate # On Windows: .venv\Scripts\activate # Install dependencies uv pip install -e .Create a
.envfile in the project root:EMAIL_ADDRESS=your.email@gmail.com EMAIL_PASSWORD=your-app-specific-password IMAP_SERVER=imap.gmail.com SMTP_SERVER=smtp.gmail.com SMTP_PORT=587Configure Claude Desktop:
First, make sure you have Claude for Desktop installed. You can install the latest version here. If you already have Claude for Desktop, make sure it's updated to the latest version.
Open your Claude Desktop configuration file:
# MacOS ~/Library/Application Support/Claude/claude_desktop_config.json # Create the file if it doesn't exist mkdir -p ~/Library/Application\ Support/Claude touch ~/Library/Application\ Support/Claude/claude_desktop_config.jsonAdd the following configuration:
{ "mcpServers": { "email": { "command": "/Users/username/.local/bin/uv", "args": [ "--directory", "/path/to/claude-post/src/email_client", "run", "email-client" ] } } }Replace
/Users/usernameand/path/to/claude-postwith your actual paths.After updating the configuration, restart Claude Desktop for the changes to take effect.
Running the Server
The server runs automatically through Claude Desktop:
The server will start when Claude launches if configured correctly
No manual server management needed
Server stops when Claude is closed
Usage Through Claude
You can interact with your emails using natural language commands. Here are some examples:
Search Emails
"Show me emails from last week"
"Find emails with subject containing 'meeting'"
"Search for emails from recruiting@linkedin.com between 2024-01-01 and 2024-01-07"
"Search sent emails from last month"
Read Email Content
"Show me the content of email #12345"
"What's the full message of the last email from HR?"
Email Statistics
"How many emails did I receive today?"
"Show me daily email counts for the past week"
Send Emails
"I want to send an email to john@example.com"
"Send a meeting confirmation to team@company.com"
Note: For security reasons, Claude will always show you the email details for confirmation before actually sending.
Project Structure
claude-post/
├── pyproject.toml
├── README.md
├── LICENSE
├── .env # Not included in repo
├── .python-version # Python version specification
└── src/
└── email_client/
├── __init__.py
├── __main__.py
└── server.py # Main implementationSecurity Notes
Use app-specific passwords instead of your main account password
For Gmail users:
Enable 2-Step Verification in your Google Account
Generate an App Password for this application
Use the App Password in your
.envfile
Logging
The application logs detailed information to email_client.log. Check this file for debugging information and error messages.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Available Tools
4 toolscount-daily-emailsB
Count emails received for each day in a date range
Inputs: end_date (required), start_date (required).
get-email-contentB
Get the full content of a specific email by its ID
Inputs: email_id (required).
search-emailsC
Search emails within a date range and/or with specific keywords
Inputs: end_date, folder, keyword, start_date.
send-emailA
CONFIRMATION STEP: Actually send the email after user confirms the details. Before calling this, first show the email details to the user for confirmation. Required fields: recipients (to), subject, and content. Optional: CC recipients.
Inputs: content (required), subject (required), to (required), cc.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: count-daily-emails aggregates email statistics, get-email-content retrieves a specific email's full content, search-emails finds emails based on criteria, and send-email handles email composition and sending. The descriptions clearly differentiate their functions, making misselection unlikely.
The tool names follow a consistent verb-noun pattern with hyphens (e.g., count-daily-emails, get-email-content), which is readable and predictable. The minor deviation is that send-email uses a simpler noun form (email instead of email-content or similar), but this does not break the overall consistency significantly.
With 4 tools, this server is well-scoped for email management, covering key operations: counting, retrieving, searching, and sending emails. Each tool earns its place by addressing a distinct aspect of the domain without being overly sparse or bloated.
The tool set provides good coverage for core email workflows, including read (count, get, search) and write (send) operations. A minor gap is the lack of update or delete tools for managing existing emails, but agents can work around this, and the surface is largely complete for the stated purpose.
Related MCP Connectors
Email infrastructure for AI agents — send, receive, search, and reply to email over MCP.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Email inboxes for AI agents: send, receive, reply, search, and manage threaded email over MCP.
Connect any IMAP/SMTP mailbox to Claude & ChatGPT: search, read, sort, draft. Sends only with OK.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that enables AI assistants like Claude to interact with Gmail through natural language, providing comprehensive email management capabilities including sending, reading, organizing, searching, and managing drafts and labels.23GPL 3.0
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to access and manage email through IMAP, supporting browsing, searching, reading, and organizing emails while learning user preferences over time.58MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables Claude AI to interact with Gmail, supporting email sending, reading, searching, labeling, draft management, and batch operations through natural language commands.2MIT
- -licenseNot gradedqualityNot gradedmaintenanceA Model Context Protocol server that enables Claude to interact with Gmail through a secure OAuth2 connection, providing email management capabilities like listing, sending, deleting, and organizing emails.-