Email Management

You can run an Email Management MCP Server that connects to your IMAP mailbox, retrieves messages based on filters, and generates summarized content. It supports local stdio execution, a Docker-based flow, and an HTTP API for programmatic interaction so you can integrate email summaries into your apps.

How to use

You interact with the Email Management MCP Server through an MCP client or by using the HTTP API. Choose your deployment method and provide your email credentials and prompt. You can run in stdio mode for a local process, use Docker to containerize the service, or call the HTTP endpoint to fetch summaries programmatically. The server fetches emails from your inbox, applies filters such as subject, date range, sender, and mailbox, and returns the summarized results based on your prompt.

Usage patterns you can follow include:

How to install

Prerequisites: have Node.js and npm (or pnpm) installed on your machine. You may also use Docker if you prefer containerized execution.

Install dependencies and prepare the MCP client configuration for the stdio mode, which runs a local command. Use the following approach to enable the stdio flow and set up necessary environment variables.

1. Install dependencies globally:

pnpm install -g @cardor/email-summarizer

2. Add the configuration to your app client for stdio mode:

"email-summarizer": {
  "type": "stdio", // Your client MCP may require this type
  "command": "cardor-email-summarizer",
  "env": {
    "EMAIL_USERNAME": "<your-email>", 
    "EMAIL_PASSWORD": "<your-app-password>",
    "EMAIL_PORT": "993",  
    "EMAIL_CLIENT_TYPE": "gmail", 
    "EMAIL_PROMPT": "Summarize the following emails: {{emails}}"
  }
}

3. If you prefer Docker, use the Docker workflow described in the Docker configuration.

## Additional sections

Configuration notes: You can customize the prompt used for summarization. The prompt must include {{emails}} to insert the retrieved email content. You can also load the prompt content from a file or a URL by providing an absolute path or a URL that returns text.

Security: Store your email credentials securely. Use environment variables to avoid hard-coding passwords in configuration files. Rotate credentials regularly and limit access to the MCP server.

Examples of usage are available through the HTTP API. You can fetch summaries by sending the required headers to the endpoint at http://localhost:5555/mcp.

Notes: The system supports filtering by subject, date range, sender email address, and mailbox (default INBOX). Stream logs can be directed to a file via DEBUG\_LOG\_FILE or printed to the console in stream mode.

## Config references

{ "email-summarizer": { "type": "stdio", "command": "cardor-email-summarizer", "env": { "EMAIL_USERNAME": "<your-email>", "EMAIL_PASSWORD": "<your-app-password>", "EMAIL_PORT": "993", "EMAIL_CLIENT_TYPE": "gmail", "EMAIL_PROMPT": "Summarize the following emails: {{emails}}" } } }

```json
{
  "email-dock": {
    "command": "docker",
    "args": [
      "run",
      "-i",
      "--rm",
      "-e",
      "EMAIL_USERNAME=<your-email>",
      "-e",
      "EMAIL_PASSWORD=<your-app-password>",
      "-e",
      "EMAIL_PORT=993",
      "-e",
      "EMAIL_CLIENT_TYPE=gmail",
      "-e",
      "EMAIL_PROMPT=Summarize the following emails: {{emails}}",
      "email-summarizer"
    ]
  }
}

{
  "email_http": {
    "type": "http",
    "name": "email_http",
    "url": "http://localhost:5555/mcp",
    "args": []
  }
}

Available tools

search-emails

Fetch emails from the inbox applying subject, date range, sender, and mailbox filters.

mark-emails-as-read

Mark the specified emails as read in the inbox.