Innmail for Agents

app.innmailPublished by innmail.appOfficial publisherv2.0.0Updated Oct 24, 2026

Email inbox for an AI agent: threads, send, reply, drafts, verification codes, calendar.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Remote MCP endpoint that gives an AI agent its own Innmail email inbox: threads, sending, replies, drafts, verification codes and calendar.

What you can do
  • Read and work with email threads in the agent's Innmail inbox
  • Send messages and reply within threads
  • Create and manage drafts
  • Retrieve verification codes from incoming mail
  • Access calendar items tied to the inbox
When to use it
Useful when an assistant needs its own email identity to send and receive mail, follow conversations, pick up sign-in verification codes, or coordinate calendar items, rather than acting through a person's mailbox.
Requirements
A remote streamable HTTP endpoint at the provider's site; no local package. Requires an Innmail account and an API key created under Developers after joining the beta, sent as a bearer token in the Authorization header.
Before you install
The API key is a secret sent in the Authorization header and grants access to the agent's mailbox. The server can send and reply to email and handle verification codes, so messages leave the account and codes can be used to complete sign-ins; review what the assistant is allowed to send.

Installation

In SourceWeft

  1. Open Innmail for Agents in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/app.innmail%2Fagents/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.

{
  "mcpServers": {
    "innmail-for-agents": {
      "type": "http",
      "url": "https://www.innmail.app/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v2.0.0LatestOct 23, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.