agentmailer-mcp
Skill1 starsChanged 3 months agoMITView on GitHub
Connect to AgentMailer's hosted MCP server, complete human-approved OAuth, or troubleshoot authentication in Claude Code, Codex, Cursor, and other MCP clients.
In this repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-email-patternsSkill
- agentmailer-a2aSkill
- agentmailer-check-emailSkill
- agentmailer-cliSkill
- agentmailer-emailSkill
- agentmailer-eventsSkill
- agentmailer-inboxSkill
- agentmailer-manage-inboxesSkill
- agentmailer-mcpSkill
- agentmailer-sdkSkill
- agentmailer-securitySkill
- agentmailer-send-emailSkill
- agentmailerSkill
- agentmailer-toolkitSkill
- agent-email-patternsSkill
- agentmailer-a2aSkill
- agentmailer-check-emailSkill
- agentmailer-cliSkill
- agentmailer-emailSkill
- agentmailer-eventsSkill
- agentmailer-inboxSkill
- agentmailer-manage-inboxesSkill
- agentmailer-sdkSkill
- agentmailer-securitySkill
- agentmailer-send-emailSkill
- agentmailerSkill
- agentmailer-toolkitSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 6 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use the universal Streamable HTTP endpoint:
- Distinctive: line 12
Prefer the client's native remote-MCP configuration so it can discover OAuth from AgentMailer's protected-resource metadata.
- Distinctive: line 26
Every first-time signup requires human approval.
- Very specific: line 28
Call auth_me and require a trusted identity with inboxes:create before creating an identity inbox.
- Very specific: line 29
Call list_inboxes as a low-risk functional check.
- Very specific: line 30
If no existing inbox fits, call create_inbox with a stable idempotency key and an optional lowercase username.
- Very specific: line 31
Verify the returned address ends in @agentmailer.ai.
- Very specific: line 33
If the client cannot complete MCP OAuth or needs direct REST access, follow https://api.agentmailer.ai/auth.md exactly.
- Very specific: line 35
Do not call create_inbox with an unverified credential.
- Distinctive: line 39
Read references/troubleshooting.md when connection, OAuth, or permission checks fail.
- Distinctive: line 46
Never claim the connection works until an authenticated tool call succeeds.
- Distinctive: line 50
Use the human-approved signup example to understand the approval boundary, then the
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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, thenclaude mcp login agentmailer. - Codex: run
codex mcp add agentmailer --url https://api.agentmailer.ai/mcp, thencodex 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.mdexactly. - 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:
- Call
auth_meand require a trusted identity withinboxes:createbefore creating an identity inbox. Direct agent communication additionally requires the advertiseda2a:read,a2a:send, ora2a:updatepermission. - Call
list_inboxesas a low-risk functional check. - If no existing inbox fits, call
create_inboxwith a stable idempotency key and an optional lowercase username. - 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

