Run your newsletter with your own AI agent
SimpleNewsletter365 exposes an authenticated MCP server with full parity to the web app: your agent can do everything you can do, within your own permissions. Destructive and high-risk actions always come back to you for approval.
MCP is enabled by default. Review policy and your personal grant under Settings → MCP after connecting.
Start in one paste
Paste this into your AI agent to get set up
Copy the prompt below into Codex. It sends Codex to the live setup guide and walks you through connecting, whether or not you already have an account.
I want to use SimpleNewsletter365, a Microsoft 365-native newsletter tool, through its MCP server so you can run my newsletter with me: drafting, audience, sends, reporting, and organization admin. First, read https://www.simplenewsletter365.com/llms.txt for the current capabilities, tools, and exact setup steps, and treat it as the source of truth. Then help me get set up: 1. I need a Microsoft 365 work or school account to sign in with during the OAuth step. If I do not have a SimpleNewsletter365 organization yet, you can create it for me over MCP after connecting: accounts_list (empty), then legal_accept, then account_create. MCP is enabled by default. 2. Use Codex's default OAuth callback. Do not add mcp_oauth_callback_port to my config or ask me to restart before login. 3. Replace any older entry, then add the server with --oauth-client-id simplenewsletter365-mcp-public and --oauth-resource https://app.simplenewsletter365.com/mcp before running codex mcp login simplenewsletter365 --scopes mcp,offline_access. 4. I will complete Microsoft sign-in and approve the consent screen myself. 5. After OAuth succeeds, stop using browser or computer automation for SimpleNewsletter365. Use the MCP tools for all supported work. 6. Call accounts_list with no arguments first to discover my account id (creating the organization first if the list is empty), then list the MCP tools you can see and tell me, in plain language, what you can and cannot do within my permissions. If a requested action is not exposed or granted through MCP, explain the limitation instead of switching back to browser automation. Throughout: act only within my permissions, do not claim unavailable bundles are usable, and keep my recipient data private.
The prompt points to llms.txt, which always reflects the current tools and setup steps. Browser use ends after sign-in and consent. From that point, the agent should work through MCP instead of clicking through the app.
Full parity
Run the whole newsletter with your agent
All five bundles are grantable: drafting, reporting, audience management, send operations, and organization admin, 106 tools in total. Every tool calls the same application services and permission checks as the web app, so parity never means extra privilege.
Draft and author
Create a draft or clone a past newsletter, set its subject and body, reference images already uploaded in the app, validate it, and render a safe server-side preview.
Read your reports
Read delivery summaries, click engagement with top links, per-recipient metrics, short-link events, and the send recipient list, with recipient identity gated the same way it is in the app.
Manage your audience
List, create, and update contacts, import from CSV, OneDrive, Outlook, or Microsoft Bookings, manage segments and signup forms, and read subscriber history, all behind the same ManageContacts permission as the app.
Send with your approval
Check mailbox and audience readiness, request a send, and pause, resume, or stop it. Every real send waits for a confirmation that only you can approve.
Administer the organization
Team invitations, member permissions, custom domains, short links, plan changes, and MCP policy, with access-changing steps gated behind web-only approvals.
Know its own access
Read the account context to see exactly which capabilities and permissions the connection holds for an account before it acts.
Authorization
You authorize the agent, and you set the limits
Access is granted through a standard OAuth 2.1 PKCE flow with an explicit consent step, not an API key you paste into a bot. The agent receives a scoped MCP token that carries your identity and nothing more.
You authorize once
Your agent runs an OAuth 2.1 PKCE flow, and you approve an explicit consent screen that names the client and what it is asking for. Nothing connects until you say yes.
Scoped to your permissions
The connection carries your identity and acts only within the permissions your membership already grants. It can never do more in the product than you can.
Microsoft tokens stay server-side
Your Microsoft 365 and mailbox tokens are never placed on the agent's token and never leave the server. The agent only ever holds a narrowly scoped MCP token.
Enabled by default and revocable
An owner can disable MCP or limit bundles for the organization. Each member can review or revoke their own client grant from Settings.
Clear boundary
High-risk actions always keep a human in the loop
Your agent can prepare a live send, reshape audiences, and manage the organization, but every destructive or security-sensitive step creates a confirmation only you can approve, in the app or with a one-time code. Access-changing actions always require approval in the web app itself.
The connection still stays within the signed-in user's permissions, organization policy, and personal client grant. Microsoft 365 and mailbox tokens remain on the server and never become part of the MCP token.
Works with supported MCP clients
Codex connects through the curated public client
simplenewsletter365-mcp-public. Add the MCP URL with the
client ID and resource, then complete OAuth PKCE authorization using
Codex's default callback. No config edit or preliminary restart is
required. Dynamic Client Registration is not enabled. Read the
security overview for how
identity, tokens, and tenant isolation are handled.
Send your first newsletter from your own mailbox
Start free with 10,000 sends a month and unlimited contacts. No card, no new password, no migration.