letterport

dev.letterportPublished by letterport.devOfficial publisherv1.0.0Updated Oct 26, 2026

Real email inboxes for AI agents: create addresses, read mail as JSON, reply in threads.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Remote MCP server that gives an AI assistant real email inboxes: create addresses, read incoming mail as JSON, and reply within threads.

What you can do
  • Create email addresses for an agent to receive mail at
  • Read incoming messages as structured JSON
  • Reply within existing email threads
  • Connect over a remote streamable HTTP endpoint with OAuth sign-in or an API key
When to use it
Useful when an assistant needs a working email identity rather than a read-only mailbox: receiving messages, parsing them, and answering in the same thread, for example for agent-driven correspondence or sign-up flows that require email.
Requirements
A remote endpoint at api.letterport.dev over streamable HTTP; no local package or runtime. Authentication is required: OAuth through the browser, or an Authorization header carrying a Bearer API key for clients that do not sign in that way.
Before you install
The server holds real inboxes and can send replies, so messages it writes go out under your address. The Authorization header carries a secret API key; keep it out of logs and shared configs. Mail content is handled by a third-party service.

Installation

In SourceWeft

  1. Open letterport 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/dev.letterport%2Fletterport/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": {
    "letterport": {
      "type": "http",
      "url": "https://api.letterport.dev/mcp"
    }
  }
}

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.0LatestOct 23, 2026

Score

67% 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.