Plug in. Done.
One-snippet setup for the runtime your agent already runs in. MCP-native for the agent IDEs, native SDKs for everything else.
Mails.ai for Cline — drop-in MCP server in VS Code
Same MCP server config as Claude Code and Cursor — pasted into Cline's MCP Settings panel. Mails.* tools auto-register, Cline's plan-mode previews tool calls before executing, and the autonomous-loop agent can send + read email as part of multi-step task runs.
Mails.ai for Continue — drop-in MCP server in VS Code + JetBrains
Continue runs in both VS Code and JetBrains IDEs. Drop the mails.ai MCP server config into ~/.continue/config.json and the same five mails.* tools become available to Continue's chat, autocomplete, and agent modes — same shape, two editor ecosystems covered.
Mails.ai for Windsurf — drop-in MCP server in Cascade
Windsurf's Cascade is one of the most capable autonomous IDE agents. Drop the mails.ai MCP server into Codeium's MCP config and Cascade auto-discovers the five mails.* tools — usable in plan mode (review before send) or write mode (autonomous execution).
Mails.ai with the Vercel AI SDK — tool definitions for serverless agents
Vercel AI SDK doesn't have first-class MCP-client primitives yet, so the integration is via the SDK's tool() helper wrapping the @mailsai/sdk client. Works seamlessly in Next.js Route Handlers, Server Actions, edge runtime, and node runtime.
Mails.ai with LangGraph — function tools for orchestrated agent flows
LangGraph doesn't have native MCP-client primitives, so the mails.ai integration is via @tool decorated functions wrapping the REST API. Pattern works in StateGraph nodes, conditional edges, and parallel-fanout flows. Full Python example with state persistence.
Mails.ai with Pydantic AI — typed agents for production Python
Pydantic AI brings the same type-safety obsession to agent code that Pydantic brought to data validation. mails.ai integrates as @agent.tool decorated functions with typed input schemas, dependency injection for the mails client, and structured output for downstream graph nodes.
Mails.ai for Claude Code — drop-in MCP server setup
One JSON snippet in ~/.claude.json and your Claude Code session has email. mails.send / mails.on_reply / mails.list_threads / mails.suppress / mails.get_reputation tools auto-discovered, no SDK install, no glue code.
Mails.ai for Cursor — drop-in MCP server setup
Same JSON snippet as Claude Code, dropped into ~/.cursor/mcp.json. Cursor auto-discovers the mails.* tools, surfaces them in the tool execution preview, and the in-IDE agent can send + read email without leaving the editor.
Mails.ai with the OpenAI Agents SDK — MCP server or function tools
OpenAI's Agents SDK speaks MCP via MCPServerStdio. Three lines wire mails.ai in. Or wrap the REST API as @function tools for fine-grained control. Both shapes documented here with full code.
Mails.ai with the Anthropic SDK — MCP-client or REST
The Anthropic SDK ships built-in MCP-client primitives. Three lines wire mails.ai in as a tool surface for any Claude conversation. Or use the @mailsai/sdk client directly for fine-grained control. Both paths documented here.
Built for agents.
Self-serve at every volume.
Public API opens Q3 2026. Drop ~6 lines into your agent and ship.
$ npm install @mailsai/sdk