AIsa Agent Mail

one.aisaPublished by aisa.oneOfficial publisherv1.0.1Updated Oct 24, 2026

Inboxes, threads, drafts and sending, built for agents.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

A remote MCP endpoint that gives an AI assistant agent-oriented email: inboxes, threads, drafts and sending.

What you can do
  • Manage inboxes built for agents
  • Read and follow email threads
  • Create and manage drafts
  • Send email messages
When to use it
Useful when an assistant needs its own email presence — receiving and reading messages, organizing conversations into threads, preparing drafts, and sending mail on the user's behalf.
Requirements
Remote streamable HTTP endpoint at mcp.aisa.one; no local package or environment variables. Authentication is OAuth and required, so the user must sign in and authorize the connection.
Before you install
The assistant can send email and create drafts, which are outward-facing actions that may be hard to undo. Access is granted through OAuth to the user's account, so review the scopes requested. Message content handled by the server goes to a third-party service.

Installation

In SourceWeft

  1. Open AIsa Agent Mail 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/one.aisa%2Fagent-mail/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": {
    "aisa-agent-mail": {
      "type": "http",
      "url": "https://mcp.aisa.one/mail/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.1LatestSep 16, 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.

Other Aisa integrations