Gemini, Google's assistant, supports MCP servers in three different ways: Gemini CLI for technical teams, Gemini Enterprise for businesses, and the consumer app where Google has made it available.
Gemini is developed by Google DeepMind. Announced in late 2023, it replaced Bard in 2024. It is known for its very long context, which lets it read large volumes at once, and for its integration with Google Workspace.
For MCP, Google has opened several doors that look nothing alike: a command-line tool, an enterprise version managed by the admin, and “custom apps” in the consumer app, rolled out gradually by country and language.
For a company in Europe or Switzerland, the safest route today is Gemini CLI, or Gemini Enterprise if your organization uses it.
| Developer | Google DeepMind (United States, United Kingdom) |
|---|---|
| Gemini CLI | Settings file, OAuth sign-in detected automatically |
| Gemini Enterprise | Custom MCP server added by the admin |
| Consumer app | Custom apps, rolled out gradually by country and language |
| Strength | Very long context, integration with Google Workspace |
A year of campaign statistics, dozens of templates: Gemini compares and summarizes without splitting them up.
Teams that work in Docs or Sheets find their email marketing figures in the same assistant.
Gemini CLI automates repetitive tasks: test lists, imports, pre-send checks.
With Gemini Enterprise, the admin adds Mailpro once for the authorized teams.
Gemini CLI: in ~/.gemini/settings.json, add a server under mcpServers with "httpUrl": "<server address>" (the server address shown in your Mailpro account, on the AI Assistants (MCP) page).
In Gemini CLI, run /mcp auth mailpro: the Mailpro sign-in page opens, sign in and accept the permissions. /mcp list shows the tools.
Gemini Enterprise: the admin registers Mailpro as a custom MCP server in the admin console.
In Mailpro, on the AI Assistants page, set how it sends: with approval or direct, with a daily cap.
The Gemini consumer app lets you add an app using an MCP server address, but for now Google limits this to certain countries, languages and personal accounts: check its settings.
It is the door that works everywhere and the best documented; the OAuth sign-in is detected automatically.
In the enterprise version, the admin declares the MCP servers; depending on the setup, they may have to enter the OAuth addresses manually.
Custom apps in the consumer app are aimed at personal accounts; with a Google Workspace account, go through Gemini Enterprise.
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, through Gemini CLI or Gemini Enterprise. Custom apps in the consumer app are not available everywhere yet.
The admin adds Mailpro as a custom MCP server; authorized users then sign in with their own Mailpro account.
No, by default every send waits for your approval in Mailpro; direct sending is set assistant by assistant.
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.
