Loading...
Loading...
Found 13 Skills
Add email capabilities to AI agents using popular frameworks. Provides pre-built tools for TypeScript and Python frameworks including Vercel AI SDK, LangChain, Clawdbot, OpenAI Agents SDK, and LiveKit Agents. Use when integrating AgentMail with agent frameworks that need email send/receive tools.
Read, search, summarize, and triage AgentMail inboxes through the connected MCP server. Use for ANY request to look at, search, or process mail — even a simple 'search my inbox for X' or 'any new mail?'; the read workflow applies regardless of task size. Also use to summarize conversations, inspect attachments, manage read/unread labels, or find messages needing a reply; do not use for sending or drafting (agentmail-send-email), inbox administration (agentmail-manage-inboxes), or MCP connection setup (agentmail-mcp).
Send and receive emails programmatically using the AgentMail CLI. Use when agents need to manage inboxes, send/receive emails, handle threads, drafts, webhooks, and domains via command line.
Give AI agents their own email inboxes using the AgentMail API. Use when building email agents, sending/receiving emails programmatically, managing inboxes, handling attachments, organizing with labels, creating drafts for human approval, or setting up real-time notifications via webhooks/websockets. Supports multi-tenant isolation with pods.
Comprehensive guide to why and how AI agents should use email. Use when evaluating whether an agent needs email, comparing email infrastructure options (AgentMail vs Gmail API vs Resend vs SendGrid vs SES), understanding security risks like prompt injection via email and OAuth credential exposure, or exploring common agent email use cases such as customer support agents, sales outreach, verification flows, and browser automation.
Email infrastructure for AI agents. Create accounts, send/receive emails, manage webhooks, and check karma balance via the AgentMail API.
Comprehensive guide to the AgentMail Python and TypeScript SDKs. Use when building AI agents that need their own email inboxes, sending or receiving emails programmatically, managing threads and conversations, handling attachments, creating drafts for human-in-the-loop approval, setting up real-time notifications via webhooks or WebSockets, configuring custom domains, managing allow/block lists, using pods for multi-tenant isolation, or integrating email into any AI agent workflow. Covers the full AgentMail API with code examples, best practices, and production patterns.
Draft, send, reply to, or forward email through the connected AgentMail MCP server. Use for ANY request to send, reply to, or forward mail — even a quick one-line send or a simple forward that looks like a single tool call; the sending rules apply regardless of task size. Also use to compose messages, create or schedule drafts for review, or send to named recipients; do not use for reading or triaging mail (agentmail-check-email), inbox administration (agentmail-manage-inboxes), or MCP connection setup (agentmail-mcp).
AgentMail MCP server for email tools in AI assistants. Use when setting up AgentMail with Claude Desktop, Cursor, VS Code, Windsurf, or other MCP-compatible clients. Provides tools for inbox management, sending/receiving emails, and thread handling.
Create, list, inspect, update, or delete AgentMail inboxes through the connected MCP server. Use for ANY inbox lifecycle request — even a quick list-inboxes or a simple delete; deletion safeguards apply regardless of task size. Also use when the user asks for a new agent email address, wants inbox details changed, or removes an inbox; do not use for sending mail (agentmail-send-email), reading or triage (agentmail-check-email), or MCP connection setup (agentmail-mcp).
Create accounts for an agent at third-party services with AgentID, using an AgentMail inbox as the agent's identity, and see where each inbox already has an account. Use for ANY request like "create an account at Firecrawl", "sign my agent up for Turso", "get my agent a web search API", "log my agent back in to Firecrawl", "sign in with the auth token this page shows", "which services is this inbox signed up for?", or browsing the AgentID app marketplace. Do not use for sending or reading mail (agentmail-send-email, agentmail-check-email), inbox lifecycle on its own (agentmail-manage-inboxes), or MCP connection setup (agentmail-mcp).
Use when an agent needs to send outreach, reply to inbound, sign up for a service, or log into a site via the user's autark-provisioned AgentMail inbox. Everything goes through `autark mail`.