Verify email in Gemini CLI
The Gemini CLI has MCP support built in and is free and open source. Add the Qualisend endpoint and Gemini can verify addresses and clean lists from the terminal.
- MCP endpoint
- https://app.qualisend.com/api/mcp
- Authentication
- Sign-in or API key
- Available on
- Free and open source on all platforms. Gemini Code Assist in VS Code reads the same ~/.gemini/settings.json; the JetBrains plugin takes the same mcpServers block in an mcp.json file in the IDE configuration directory instead.
Connect it to Gemini CLI
You need a Qualisend account - the free plan includes 100 verification credits that never expire - and Gemini CLI itself. Steps checked against Google's documentation in September 2026.
- 1
Add the server with a key
Add --scope user to write the global config rather than the project one.
gemini mcp add --transport http \ -H "Authorization: Bearer qs_live_…" \ qualisend https://app.qualisend.com/api/mcp - 2
Or add it for sign-in
Leave the header off, then run /mcp auth qualisend inside the CLI and finish in the browser.
gemini mcp add --transport http qualisend https://app.qualisend.com/api/mcp - 3
Check it
Start gemini and run /mcp list - qualisend should show a green Ready, with its tools listed.
/mcp list
Sign-in or API key
Either. Drop the header flag and the CLI sees the 401 and tells you to run /mcp auth qualisend, which opens the browser - it no longer starts that flow by itself. Keep the flag and it uses your Qualisend API key.
Check that it worked
Ask "how many Qualisend credits do I have left?". A number back means you are connected - that tool is free, so it costs nothing to test.
Config file
~/.gemini/settings.json (or <project>/.gemini/settings.json)url with "type": "http" pins Streamable HTTP. url on its own also works - the CLI tries Streamable HTTP first and falls back to SSE. This is exactly what gemini mcp add writes.
{
"mcpServers": {
"qualisend": {
"url": "https://app.qualisend.com/api/mcp",
"type": "http",
"headers": {
"Authorization": "Bearer $QUALISEND_API_KEY"
},
"timeout": 30000,
"trust": false
}
}
}Worth knowing
- Use url, the same as most other clients. The older httpUrl field still works but is deprecated, and gemini mcp add never writes it - so a config from the command and a config copied from an old guide will not match.
- timeout is in milliseconds in this file (30000 = 30 seconds), unlike Goose where it is seconds.
- Sign-in needs a browser on the machine. On a headless box or over SSH, use the API key instead.
- Leave trust as false unless you want every tool call to skip its confirmation prompt.
- mcpServers stays a top-level key even in newer releases that nest other settings. Do not move it.
What to ask once it is connected
There are no commands to learn. Ask in your own words and Gemini CLI picks the right tool - there are twelve, covering verification, sending-domain deliverability and blacklist checks.
What Gemini CLI can reach
Only the verification tools, scoped to the single workspace you connect. It cannot reach another customer's data, your billing, or any admin function, and it never sees how a check is performed - just the verdict and the score. Authentication is an explicit token in a request header, never a cookie, so there is no session for a malicious page to borrow. Revoke it from Gemini CLI or from your Qualisend dashboard at any time; sign-in access also expires on its own within an hour. Full detail is on the MCP documentation page.
Gemini CLI FAQ
Google's own reference: Gemini CLI MCP docs
Using something else?
It is the same endpoint everywhere. Pick your client:
Any other MCP-compatible client works too - Cline, JetBrains AI Assistant and the rest all take the same Streamable HTTP endpoint. The MCP documentation has the transport and authentication details.
Start free with 100 credits that never expire, then paste the endpoint.