mcpField
E
Email Sender x402

Email Sender x402

Remote
github.comCommunication0Updated 8w ago

About Email Sender x402

Email Sender x402 is an MCP and HTTP API for agents that need to send transactional email. It supports text and HTML messages, with per-call payment in USDC on Base instead of an API key.

Key features

  1. 01Send email to recipients
  2. 02Plain-text and HTML bodies
  3. 03Return delivery status and message ID
  4. 04Pay per call with USDC on Base

Use cases

  1. 01Send transactional email
  2. 02Deliver notifications and alerts
  3. 03Send password resets or order confirmations
  4. 04Distribute automated reports

MCP support

Exposes the `email_send_message` tool to MCP clients for sending email. Calls are paid per use through x402 in USDC on Base.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://email-send.api.klymax402.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

Email Send API

MCP Server x402 License: MIT

Send emails programmatically via Resend -- text or HTML body, delivery status, message ID. Transactional email. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

{
  "mcpServers": {
    "email-send": {
      "url": "https://email-send.api.klymax402.com/mcp"
    }
  }
}

Quickstart -- HTTP (x402)

curl -X POST "https://email-send.api.klymax402.com/api/send" \
  -H "Content-Type: application/json" \
  -d '{"to":"...","subject":"...","body":"..."}'
# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

ToolMethodPathPriceDescription
email_send_messagePOST/api/send$0.008Send an email message
email_send_message

Use this when you need to send an email to one or more recipients. Returns delivery confirmation in JSON.

Parameters

NameTypeRequiredDescription
tostringyesRecipient email address
fromstringnoSender email address (default: [email protected])
subjectstringyesEmail subject line
bodystringyesEmail body content (plain text)
htmlstringnoEmail body content (HTML, optional — overrides body)

Example response:

{"messageId":"msg_01abc123","status":"sent","timestamp":"2026-04-13T14:30:00Z","to":"[email protected]","from":"[email protected]","subject":"Your Report"}

When to use: sending transactional emails, notifications, alerts, password resets, order confirmations, and automated reports.

Not for: email validation (use email_verify_address), finding email addresses (use email_find_by_name), person data enrichment (use person_enrich_from_email).

Example agent prompts

  • "Send an email to one or more recipients"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)
  • Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.