AgentMailer MCP

Connect MCP with human-approved OAuth

AgentMailer

@agentmailer

Install

$ openclaw skills install @agentmailer/agentmailer-mcp

AgentMailer MCP

Use the universal Streamable HTTP endpoint:

https://api.agentmailer.ai/mcp

Prefer the client's native remote-MCP configuration so it can discover OAuth from AgentMailer's protected-resource metadata. Do not ask the user to paste OAuth tokens into prompts, source files, or shell history.

Connect

Choose the shortest path for the active client:

  • Claude Code: run claude mcp add --transport http agentmailer https://api.agentmailer.ai/mcp, then claude mcp login agentmailer.
  • Codex: run codex mcp add agentmailer --url https://api.agentmailer.ai/mcp, then codex mcp login agentmailer.
  • OpenCode: add the remote server configuration, then run opencode mcp auth agentmailer.
  • OpenClaw: add the remote server configuration, then run openclaw mcp login agentmailer.
  • Hermes: add the remote server configuration, then run hermes mcp login agentmailer.
  • Server workloads: prefer OAuth-capable hosted MCP when the runtime supports it. For direct REST access, follow https://api.agentmailer.ai/auth.md exactly.
  • Other clients: add the endpoint as a remote HTTP MCP server, then run the client's MCP OAuth login or authenticate action.

Every first-time signup requires human approval. After authorization:

  1. Call auth_me and require a trusted identity with inboxes:create before creating an identity inbox. Direct agent communication additionally requires the advertised a2a:read, a2a:send, or a2a:update permission.
  2. Call list_inboxes as a low-risk functional check.
  3. If no existing inbox fits, call create_inbox with a stable idempotency key and an optional lowercase username.
  4. Verify the returned address ends in @agentmailer.ai; this unique handle names the same durable identity over email and direct agent communication.

If the client cannot complete MCP OAuth or needs direct REST access, follow https://api.agentmailer.ai/auth.md exactly. Do not invent or partially reproduce its signup and token procedure.

Do not call create_inbox with an unverified credential. A human_approval_required response means the approval ceremony is incomplete; show the existing approval URL or restart the documented signup flow instead of retrying blindly.

Diagnose

Read references/troubleshooting.md when connection, OAuth, or permission checks fail. Preserve the distinction between:

  • transport failure;
  • OAuth discovery or callback failure;
  • authenticated but insufficient permissions;
  • a successful connection with no inboxes yet.

Never claim the connection works until an authenticated tool call succeeds.

Examples

Use the human-approved signup example to understand the approval boundary, then the quickstart or CLI workflows for a low-risk authenticated check. Browse the complete examples catalog for application-specific integrations.

Top skills in this category

PollyReach

@pollyreach

PollyReach gives every AI agent a phone number and the ability to get things done over the phone — finding contacts, making calls, and completing tasks. Just...

56102k

gmail

@byungkyu

Gmail API integration with managed OAuth. Read, send, and manage emails, threads, labels, and drafts. Use this skill when users want to interact with Gmail. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Gmail connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Gmail action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Gmail examples; they add no Gmail capability - Gmail is itself an event source, so its own events are in `references/google-mail/triggers.md`, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).

7540k

WhatsApp Business

@byungkyu

WhatsApp Business API integration with managed OAuth. Send messages, manage templates, and handle conversations. Use this skill when users want to interact with WhatsApp Business. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a WhatsApp Business connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a WhatsApp Business action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with WhatsApp Business examples; they add no WhatsApp Business capability - WhatsApp Business is not an event source, a trigger cannot read WhatsApp Business data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).

6024k

AI Persona OS

@jeffjhunter

The complete operating system for OpenClaw 5.x agents. Built-in memory tool integration (memory_search, memory_get, DREAMS.md), Discord channel-routing fixes...

9512k

WeChat MP CN

@guohongbin-git

微信公众号监控 - 文章监控、阅读量追踪、舆情分析(WeChat Official Account)

4715k