In the Microsoft world, Mailpro becomes a tool for your agents: in Copilot Studio, it is added as an MCP server in a few fields; in Microsoft 365 Copilot, it goes through a declarative agent deployed by the admin.
Microsoft 365 Copilot and Copilot Studio have been available since late 2023. Copilot Studio lets you build business agents without code; Microsoft 365 Copilot makes them available in Teams, Outlook and SharePoint.
Copilot Studio accepts MCP servers directly as tools: you give a name, a description (which the agent reads to know when to use the tool) and the address. The OAuth sign-in can use “Dynamic discovery”: Copilot Studio registers itself with Mailpro.
Connections go through Power Platform connectors: your admin's data loss prevention (DLP) policies also apply to Mailpro.
| Developer | Microsoft, Redmond (United States) |
|---|---|
| Copilot Studio | Agent › Tools › Add a tool › New tool › Model Context Protocol |
| Sign-in | OAuth 2.0 with “Dynamic discovery” (automatic registration) |
| Transport | Streamable HTTP only |
| Microsoft 365 Copilot | Via a declarative agent (Microsoft 365 Agents Toolkit), deployed by the admin |
It confirms an appointment or an order by SMS, within the cap you set for that agent.
The team asks it for the monthly newsletter; it prepares it in Mailpro, where it waits for your approval.
It reads the sending statistics and posts a summary every Monday.
The agent is triggered by your Power Platform flows and uses Mailpro like any other tool.
In Copilot Studio, open your agent, then Tools › Add a tool › New tool › Model Context Protocol.
Enter a name, a clear description (“send and track Mailpro emails and SMS”) and the server address shown in your Mailpro account, on the AI Assistants (MCP) page.
Choose OAuth 2.0 authentication, Dynamic discovery mode, then create the connection by signing in to Mailpro.
In Mailpro, on the AI Assistants page, set how this agent sends: with approval or direct, with a daily cap.
For Microsoft 365 Copilot, a developer builds a declarative agent with the Microsoft 365 Agents Toolkit (Visual Studio Code), and the admin deploys it from the Microsoft 365 admin center.
The agent picks its tools by reading their descriptions: a precise description keeps it from using Mailpro out of context.
If your admin blocks custom connectors, they will need to allow the Mailpro one in the environment's data policy.
Each connected agent appears separately in Mailpro, with its own cap and its own log.
On the Mailpro side, the rules are the same for every assistant: by default, each send waits for your approval, or goes out directly within a daily cap; a log keeps track of everything, and one click suspends all sends. The details.
Yes: Copilot Studio requires the Streamable HTTP transport and OAuth 2.0, which the Mailpro MCP server uses.
You need Copilot Studio to build the agent; use in Microsoft 365 Copilot depends on your Microsoft licenses.
Yes, if you allow direct sending, with a daily cap; otherwise, its sends wait for your approval.
All questions: AI assistants FAQ.
Create a free Mailpro account, connect your assistant from the AI Assistants page of your account, and stay in control of every send.
