To give an AI agent its own email, create a separate nicemails mailbox for it and connect the agent over MCP. The agent can then read and search that mailbox, pick up verification codes, organize messages and send mail, using only the permissions and mailboxes you grant. A message to a new recipient waits for your approval.
Agents that sign up for services, wait for verification codes or follow up on replies need an address that receives mail like a real inbox. Connecting an agent to your personal inbox hands it everything in there: private conversations, password resets and receipts.
A dedicated mailbox keeps the agent’s mail apart from yours. You can limit a connection to that one mailbox, see what the agent did, and switch it off at any time without touching your own email.
Each nicemails mailbox is a real, independent mailbox, not an alias that forwards to another inbox. It has its own address, its own Inbox, Sent, Archive, Spam and Trash folders, its own sender name and its own storage. You manage it alongside your other mailboxes from one account, in the web app, through the REST API or over MCP.
nicemails runs a remote MCP server with 8 tools. Read-only tools never change your mail. Tools that change data are marked, so your client can ask you before each call.
list_mailboxes lists the mailboxes the connection can use, with their storage usage.create_mailbox creates a new mailbox within your plan’s limits. It needs the Manage permission and a connection that is not limited to one mailbox.list_messages lists one folder of a mailbox, newest first.search searches every folder of the selected mailboxes, including Spam.get_message reads one message with its body, attachment details and delivery status, without marking it as read.send_message queues an email from one of your mailboxes. New recipients need your approval first.move moves a message to another folder in the same mailbox.flag marks a message as read or unread, starred or answered.A typical request is “check the agent’s mailbox for the code from the service I just signed up for”. The agent searches the mailbox, opens the newest matching message and reads the code from it.
research-agent. Names use 2 to 63 lowercase letters, digits, dots or hyphens.In other agents, such as ChatGPT or Cursor, add the same address as a connector, then sign in and approve access.
For an agent without OAuth sign-in, or a program that runs unattended, create an API key instead: open Settings → API keys, select Create API key and choose AI agent (MCP) as its purpose. The key is shown only once. nicemails can also copy a prompt for your agent that includes the key and how to connect.
On every plan, each mailbox sends to at most 50 recipients per UTC day, and API keys default to 50 recipients per UTC day. New accounts have lower daily limits for their first 14 days. Every recipient in To, Cc or Bcc counts once. See Pricing for every limit.
Yes. The address receives mail like any other inbox, so after a sign-up the agent can find the confirmation email or code with search or get_message. Follow each service’s terms; the Acceptable Use Policy does not allow creating accounts or mailboxes in bulk.
Only if you allow it. When you approve a connection or create an API key, you can limit it to one mailbox. Every permission then applies only to that mailbox.
Only to recipients you emailed from the web app, or trusted at an earlier approval, within the last 30 days, and only if you granted the Send permission. Any other recipient needs your approval on a nicemails confirmation page first.
Agents and apps that support MCP connectors with OAuth sign-in connect by adding the server address, signing in and approving access. Other clients can send an API key as an HTTP header. The setup guide covers both.
You can start for free. Free includes 3 mailboxes and sending to 50 recipients a month through MCP. Pro costs $10 a month for 100 mailboxes and 3,000 recipients a month.