Skip to content
IMAP logo

IMAP MCP server

Receive new email trigger

IMAP is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
4
Works with
Any MCP client
Auth
Custom auth
License
MIT, open source
Updated
September 2026

About the IMAP MCP server

Connect IMAP once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches IMAP and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

IMAP tools your AI can run

Once connected, your assistant can call any of these IMAP actions by asking in plain language.

  • Mark Email as Read/Unread

    Sets the read status of an email

    3 fields

  • Copy Email

    Copy an email to another mailbox

    3 fields

  • Move Email

    Move an email to another mailbox

    3 fields

  • Delete Email

    Permanently delete an email

    3 fields

Triggers

IMAP events your agent can watch

These start a run the moment something happens in IMAP, so work gets picked up on its own.

  • New Email

    Trigger when a new email is received

    2 fields

Give your assistant IMAP

Connect IMAP once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

IMAP MCP, answered.

No. That is the point of it. One Activepieces server exposes IMAP alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect IMAP in Activepieces, enable the server under Settings โ†’ MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 4 tools, including Mark Email as Read/Unread, Copy Email, Move Email, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.