namailu.cz Agent Email

cz.namailuPublished by namailu.czOfficial publisherv0.9.2Updated Oct 24, 2026

namailu.cz gives your AI agent its own email inbox: read and send mail over MCP, with OAuth.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

namailu.cz gives an AI assistant its own email inbox, letting it read and send mail over MCP with OAuth sign-in.

What you can do
  • Read mail in the agent's own namailu.cz inbox
  • Send email from that inbox
  • Connect over MCP with OAuth authentication
When to use it
Useful when you want an assistant to handle email on its own address — reading incoming messages and sending replies — rather than acting through your personal mailbox.
Requirements
A remote MCP endpoint at mcp.namailu.cz over streamable HTTP. OAuth authentication is required, so you need a namailu.cz account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Before you install
The assistant can send email from its inbox, so outgoing messages may reach real recipients; review what it sends. Access is granted through OAuth to your namailu.cz account, and mail content is handled by that third-party service.

Installation

In SourceWeft

  1. Open namailu.cz Agent Email 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/cz.namailu%2Fagent-email/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": {
    "namailu-cz-agent-email": {
      "type": "http",
      "url": "https://mcp.namailu.cz/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. v0.9.2LatestSep 16, 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.