Poppy 1.0 + MailSchema, experimental

Approve sends from your own agent.

A MAP-enabled personal agent receives a send request by email, reads the exact campaign from Nitrosend and asks for your approval. You see the email, audience, sender and timing. Your yes releases that version once.

How it works

From first contact to an approved send.

Poppy covers finding Nitrosend and signing in. MailSchema covers the approval.

1

Find Nitrosend

Nitrosend publishes a Poppy discovery file with our MCP server and the Operations and MailSchema MAP extensions. Your agent must have the MAP binding enabled for your mailbox and chosen Nitrosend account. Signing in alone does not enable it.

2

Sign in as itself

Standard OAuth, under the agent's own identity. Its client ID is a URL to its published metadata, and it proves who it is with a signed key (private_key_jwt), never a shared secret. Every sign-in needs your Allow in Nitrosend, for one account you choose.

The send-approvals scope reads send requests received by email and approves or declines them. Nothing else. It's never granted with full account access, so the agent that runs your account and the agent that approves your sends sign in separately.

3

Show you, then pass on your yes

When a send needs your approval, your agent reads it back from Nitrosend through its own sign-in, never from the email alone, and shows you the real email: subject, content, audience, sender and timing.

You say yes, your agent passes that on with Poppy's Operations extension, and Nitrosend sends that exact version, at most once. Your agent signs each of those calls, so a stolen token can't make one.

Why email

Poppy has no push channel yet. Email already is one.

Poppy can't reach your agent when it has no request open (push notifications are on Poppy's roadmap as a proposal). The approval email can. MailSchema adds a machine-readable action to that email, so the approval email every company already sends becomes something a personal agent can act on safely.

Campaign Send Approval
When a Nitrosend send needs your approval, the approval email carries these terms:
What goes outThe exact content
ToHow many people
FromWhich sender
WhenThe send time

Your agent then reads the same terms from Nitrosend through its own sign-in, never from the email alone, and shows them to you. See Campaign Send Approval in the MailSchema registry.
The guardrails

Your yes counts once. For that exact send.

Nitrosend enforces these on its side, whichever agent is asking.

Exact version

Sent once, as approved

Nitrosend sends only the exact version you approved, at most once.

Changes

Any change voids it

Change the content, audience, sender or schedule and the old approval no longer counts. You see the new terms.

Who decides

Your agent passes on your yes

Nitrosend only takes an approval your agent states came from you, never one it marks as its own call, and refuses any approval from the agent that asked for the send. Your agent can decline a send for you.

In Nitrosend

Approve in Nitrosend, as always

You can still approve a send in Nitrosend directly, the same way you do today.

poppy.json

What an agent reads first.

One MCP server, two extensions. If you run a platform that sends approval emails, use the same pattern: the binding is an open spec on mailschema.org, and Nitrosend's is the reference implementation.

Excerpt from Nitrosend's discovery file, with the MailSchema entry trimmed. Its full shape is in MailSchema's Poppy binding.
{
  "protocol_version": "1.0",
  "organization": { "name": "Nitrosend", "domain": "api.nitrosend.com" },
  "apis": [{ "type": "mcp", "url": "https://api.nitrosend.com/mcp" }],
  "extensions": {
    "operations": [{ "version": "3" }],
    "mailschema.org/map": [{ "version": "1" }]
  }
}
FAQ

Before you connect a personal agent.

Does this change how Claude, Cursor or Codex connect?

No. Existing MCP clients keep working exactly as before. Poppy adds another way in for personal agents.

Can an agent approve a send by itself?

Not on Nitrosend's terms. Nitrosend refuses an approval the agent marks as its own decision, and any approval from the agent that asked for the send. It takes your agent's word that the yes is yours: Nitrosend can't see you say it, so pick an agent you trust. You can always approve in Nitrosend instead.

What if the campaign changes after I approve it?

The approval no longer counts. If the content, audience, sender or schedule changes, you see the new terms and decide again.

What can an agent do with the send-approvals scope?

Read the campaign send requests you received by email, and approve or decline them. Nothing else. It's never granted together with full account access, which stays behind the mcp scope.

Is it live?

The experimental reference is available. You need a personal agent that implements MailSchema's Poppy binding and asks for your approval of each send. Connecting Claude, Cursor or Codex through ordinary MCP does not enable MAP email processing. You can still approve sends directly in Nitrosend.

What are Poppy and MailSchema?

Poppy (Personal Agent Protocol) is Sierra's open protocol, Apache 2.0 licensed, for personal agents to find a company, sign in and act for their user. MailSchema is an open schema, led by Nitrosend, that adds a machine-readable action to an email (Mail Action Protocol, MAP).

Humans approve. Agents operate.

Read the binding on mailschema.org, or connect Claude, Cursor or Codex the usual way today.

→ mailschema.org/specification/poppy