PO6 Mailbox

com.po6Published by po6.comOfficial publisherv1.0.0Updated Oct 24, 2026

Give AI agents secure access to your email via private aliases with dedicated mailbox storage.

The publisher's own server: mailbox.bot

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

PO6 Mailbox gives AI agents secure access to email through private aliases with dedicated mailbox storage, via a remote OAuth-protected endpoint.

What you can do
Connect an assistant to a private email alias backed by its own mailbox storage, so the agent can work with mail sent to that address rather than a personal inbox. Access is granted through OAuth sign-in to the PO6 service. The manifest lists no individual tools, so the exact operations available are not documented here.
When to use it
Useful when you want an AI agent to handle email for a specific purpose without exposing your main inbox, by giving it a dedicated private alias and mailbox.
Requirements
A remote MCP endpoint at mcp.po6.com over streamable HTTP, plus a PO6 account and OAuth authorization. No local runtime, packages, environment variables or headers are declared.
Before you install
The server requires OAuth access to a PO6 mailbox, so review what account and mailbox data you authorize. Email content handled by the agent passes through the PO6 service. The available tools are not listed, so confirm what the agent can read, send or delete before relying on it.

Installation

In SourceWeft

  1. Open PO6 Mailbox in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.po6%2Fmailbox/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "po6-mailbox": {
      "type": "http",
      "url": "https://mcp.po6.com/"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Mailbox integrations