Skip to main content
SentFromAI ships an open Model Context Protocol (MCP) server — sentfromai-mcp on npm — so an AI agent can use email as first-class tools: create inboxes, send and reply, search, manage threads, webhooks and allow/block rules — without writing a single API call. The agent simply calls a tool.

​
Why MCP

Application sign-in is a separate capability. The optional Agent Login beta companion keeps signing keys and application sessions locally. Installing the mail plugin or connecting the hosted mail endpoint does not enable that companion or approve an agent identity. With the REST API your code orchestrates email. With MCP, the agent itself decides when to check its inbox, draft a reply, or escalate — SentFromAI’s operations appear directly in the model’s tool list.

​
Connect

Use an existing API key or follow Set up your agent to create one through REST when signup is enabled. Bootstrap happens before connecting MCP. An unclaimed account permits reads within its limits; sending and other changes require its human claim. The same inbox and key remain after claiming. Configure the key through a protected host credential field or a private MCP configuration file. Never paste a real key into command-line arguments. For the stdio commands below, configure SENTFROMAI_API_KEY in the server environment privately before starting it.
As a plugin — asks for the key when you enable it and adds a skill that teaches Claude email etiquette:
Or as a plain MCP server:
The server is a thin stdio wrapper over the REST API — no state of its own, and it runs wherever your agent runs (Node 20+). Source and issues: github.com/sentfromai/sentfromai-mcp; it is also listed in the official MCP registry as ai.sentfrom/mcp.

​
Hosted endpoint (remote MCP)

If your host only speaks remote MCP, or you would rather not run anything locally, connect to the hosted endpoint instead of npx:
Same 21 tools, same tenant scoping, served over Streamable HTTP. Two ways to authenticate:
  • API key: send Authorization: Bearer sf_live_…. Works everywhere a bearer header can be set.
  • Sign in: hosts that support MCP OAuth (claude.ai, ChatGPT) discover SentFromAI’s authorization server automatically and open a sign-in to your SentFromAI account. The connection then acts for your organization’s tenant.
The endpoint is stateless (one JSON-RPC request per HTTP request, no sessions). Tool calls run against the same API as the REST routes, so suppression, allow/block rules, plan limits and usage metering apply identically.

​
Available tools

Every tool carries MCP annotations: reads are marked read-only, send_message, reply_to_message, forward_message and send_draft are marked as reaching the outside world, and delete_* as destructive, so hosts can group them and confirm the irreversible ones. API failures come back as tool results with the HTTP status (a 401 means the key is wrong, a 402 that the plan limit is reached), so the agent can tell you rather than retry. Because the tools map onto the same endpoints documented in the API reference, everything you read here applies — threading, idempotency, suppression, and attachments all behave identically.

​
Configuration

Tools inherit the key’s tenant scope: an agent can only see and act on its own tenant’s inboxes, threads, and rules. Suppression and allow/block rules are enforced server-side, so a misbehaving agent can’t mail past them.