Skip to main content
Glama
ClaudePost

ClaudePost

by ZilongXue

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:

  • Claude Desktop application

Setup

  1. Install uv:

    # MacOS/Linux
    curl -LsSf https://astral.sh/uv/install.sh | sh
    
    # Remember to restart your terminal after installation
  2. Clone 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 .
  3. Create a .env file 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=587
  4. Configure 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.json

    Add 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/username and /path/to/claude-post with 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

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 implementation

Security Notes

  • Use app-specific passwords instead of your main account password

  • For Gmail users:

    1. Enable 2-Step Verification in your Google Account

    2. Generate an App Password for this application

    3. Use the App Password in your .env file

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 tools
count-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

    A3.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      A 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.
      23
      GPL 3.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      A 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.
      58
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A 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.
      2
      MIT
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      A 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.
      -