Waypost
Independent project / local MCP Beta

Mail and files.Calendar handoffs.

A local CLI and MCP for your Proton account.

Supported routes
MailBridge / IMAP
DriveOfficial CLI
CalendarICS + links
WaypostLocal process · MCP / CLI
Each service keeps its own setup and limits.

Three services. Three routes.

Official services, connected locally.

ServiceRouteWhat to expect
MailProton Mail BridgeRead mail directly or through an authenticated helper. Bridge requires a paid Mail plan.
DriveOfficial Proton Drive CLIList, inspect, download, and optionally upload through the official CLI.
CalendarICS exports + refreshable linksRead an agenda from an export or Proton link. Prepare files for import in Proton Calendar.

Connect your agent.

Node.js 22.14+ · Source setup

01Build and check the local setup

Terminal
git clone https://github.com/baney75/waypost
cd waypost
npm ci --ignore-scripts
npm run build
node dist/cli.js init
node dist/cli.js tools

Connect one service using the setup guide, then run node dist/cli.js doctor. Set up Bridge and the Drive CLI separately. Follow the service setup notes for requirements.

02Add Waypost to your MCP client

MCP client configuration
{
  "mcpServers": {
    "waypost": {
      "command": "node",
      "args": [
        "/absolute/path/to/waypost/runtime/waypost.mjs",
        "mcp"
      ]
    }
  }
}

Use node dist/cli.js agent-config generic to print your paths. Mail sends and Drive uploads start disabled.

Know the handoff.

Waypost runs locally; data passed to an agent follows that agent’s own data policies. Calendar reads exports or share links; Proton link updates can lag by eight hours. An import file becomes a saved event only after you import it. Review security guidance and service boundaries before connecting.