WareBenchPropose a projectENIT

PRODUCTS / AI & MCP

Postmaster MCP

A self-hosted, MCP-oriented system that brings together email, tasks and project knowledge for AI-assisted workflows. Public repository documentation describes supported integrations and setup.

View public repository →All products →

Project overview

A self-hosted, MCP-oriented system that brings together email, tasks and project knowledge for AI-assisted workflows. Public repository documentation describes supported integrations and setup.

For shipped features, installation requirements, version and license, consult the latest documentation in the public repository.

Contact WareBench →
SECTION 01

Documented capabilities

Capabilities and tools described in the public project documentation.

What the software does

  • Connects MCP-capable clients to one or more IMAP/SMTP identities with credentials stored server-side.
  • Combines persistent tasks, project-scoped knowledge, memory and skills with lexical/semantic retrieval.
  • Supports drafts, replies, outbound follow-ups, attachments, recipient authorization and a web administration dashboard.

Source and latest documentation ↗

SECTION 02

Architecture and integrations

MCP client → authenticated access or trusted network → self-hosted Postmaster → mail, task, knowledge and account stores.

Architecture overview

MCP client
authenticated access or trusted network
self-hosted Postmaster
mail, task, knowledge and account stores.

Source and latest documentation ↗

SECTION 03

Requirements and getting started

Deploy the documented postmaster-mcp.yml stack in Docker/Portainer. Initial setup needs internet access; mail features require an IMAP/SMTP account. The default host mapping is port 8787.

Prerequisites

Docker / PortainerInternet on first startIMAP/SMTP for mail

Quick start

  1. 1Deploy postmaster-mcp.yml as a Portainer stack.
  2. 2Open the dashboard on the configured host.
  3. 3Configure an authorized IMAP/SMTP identity for mail features.
SECTION 04

Limitations and operating boundaries

Account encryption keys must be backed up with the database. Recipient authorization is required for sending. Exact configuration, compatibility and releases are documented upstream.

Key boundaries

Encryption

Account encryption keys must be backed up with the database.

Recipient policy

Recipient authorization is required for sending.

Configuration

Exact configuration, compatibility and releases are documented upstream.

Source and latest documentation ↗

Need a custom integration?

This repository is a public software project, separate from paid professional AI consulting. For integration with existing systems, see the dedicated service.

Explore AI consulting →