io.github.SuperAngryMonkey/iris is an MCP server that microsoft 365 mail MCP that drafts but cannot send: no Mail.Send scope. Its tool list has not been published yet over stdio and sse, requires no API key, and scores 53/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"iris": {
"env": {
"IRIS_CLIENT_ID": "<application client id>",
"IRIS_TENANT_ID": "<directory tenant id>"
},
"args": [
"iris-mcp"
],
"command": "uvx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Microsoft 365 mail server for AI agents that cannot send email.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
uvx 'iris-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked iris-mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in communication
Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite
Programmable email inbox for AI agents — JMAP, PoW auth, stdio MCP server.
A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
The official MCP server to send emails and interact with Resend
MCP Security Weekly
Get CVE alerts and security updates for io.github.SuperAngryMonkey/iris and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Microsoft 365 mail server for AI agents that cannot send email.
Not "will not". Cannot. iris requests the delegated Graph scope Mail.ReadWrite
and never Mail.Send. The access token it holds has no capability to transmit a
message, so no prompt, no jailbreak and no bug in this code can make one go out.
It writes drafts into a folder in your mailbox. You open Outlook and press Send.
That is the whole design. Everything else is detail.
The usual worry about giving an agent your mailbox is that it will send something you did not sanction — to the wrong person, with the wrong tone, or because someone talked it into doing so. The common answer is a confirmation prompt, which is a guardrail: code that asks permission, and code can be bypassed.
iris removes the capability instead. Microsoft Graph will reject a send attempt made with this token, because the consent screen you approved never included that permission. The security boundary is Microsoft's, not this program's, and it holds even if this program is wrong.
The trade is real: a human is in the loop on every message, by construction. If you want autonomous sending, iris is the wrong tool.
uvx iris-mcp # run without installing
pip install iris-mcp
Python 3.10+.
You must register your own Entra application. There is no shared app registration and no hosted service — iris talks directly from your machine to your tenant. This is deliberate: a shared app would mean trusting someone else's client ID with access to your mail.
Mail.ReadWrite. Add nothing else. Do not add Mail.Send — if it is
present, the guarantee above is void.Then add iris to your MCP client:
{
"mcpServers": {
"iris": {
"command": "uvx",
"args": ["iris-mcp"],
"env": {
"IRIS_CLIENT_ID": "<application client id>",
"IRIS_TENANT_ID": "<directory tenant id>"
}
}
}
}
Sign in once: call iris_login, open the URL, enter the code, then call
iris_login_finish. The token cache is written next to the server, mode 600.
| Tool | What it does |
|---|---|
iris_login | Starts device-code sign-in, returns a URL and a code |
iris_login_finish | Completes sign-in; safe to call repeatedly while you type the code |
iris_auth_status | Who is signed in, which scopes, and whether Graph is reachable |
iris_create_draft | Writes a draft (to/cc/bcc, subject, body or HTML, optional reply-to) |
iris_list_drafts | Lists what is waiting in the draft folder |
iris_update_draft | Revises a draft in place |
iris_delete_draft | Deletes a draft; requires confirm=true |
Into a dedicated top-level mail folder, AI Drafts by default
(IRIS_DRAFT_FOLDER). It is created on first use. Set the variable to an empty
string to use the normal Drafts folder instead.
These are real drafts and Outlook sends them normally — but because they live in their own folder, they do not appear in the Drafts view. That is the point: agent-written mail sits somewhere you have to go and look, rather than mixed in with your own half-finished messages.
One wrinkle worth knowing: Graph's createReply always lands a reply in Drafts
first, so iris moves it afterwards, and a move assigns a new message id.
recipients.allow, one address or domain per line.
Absent or empty means all recipients are permitted. Point IRIS_ALLOWLIST
elsewhere if you prefer.