Verify email in Zed
Zed's agent panel speaks MCP natively. Add the Qualisend endpoint and the agent can verify addresses and clean lists while you work.
- MCP endpoint
- https://app.qualisend.com/api/mcp
- Authentication
- Sign-in or API key
- Available on
- All Zed builds on macOS, Linux and Windows.
Connect it to Zed
You need a Qualisend account - the free plan includes 100 verification credits that never expire - and Zed itself. Steps checked against Zed Industries's documentation in September 2026.
- 1
Open the MCP settings
Settings -> AI -> MCP Servers, or run agent: open settings from the command palette and select MCP Servers.
- 2
Add a remote server
Click Add Server in the page header and choose Add Remote Server.
- 3
Name it and paste the endpoint
Call it qualisend and paste the endpoint into URL. Leave Headers empty to sign in through the browser, or add an Authorization header set to Bearer qs_live_... right there - there is no separate auth field.
https://app.qualisend.com/api/mcp - 4
Authenticate and check
With no header present, Zed prompts you to sign in through the browser. Open the Agent Panel and confirm the Qualisend tools appear in the tool picker.
Sign-in or API key
Either. Leave the header out and Zed prompts you to sign in through the standard MCP flow; include it 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
~/.config/zed/settings.json on macOS and Linux, %APPDATA%\Zed\settings.json on Windows (or <project>/.zed/settings.json)macOS included - Zed does not use ~/Library/Application Support for this.
{
"context_servers": {
"qualisend": {
"url": "https://app.qualisend.com/api/mcp",
"headers": {
"Authorization": "Bearer qs_live_…"
}
}
}
}Worth knowing
- The settings key is context_servers, not mcpServers. A snippet copied from Cursor or Claude is ignored outright.
- There is no type or transport field for remote servers - url is the only required field, with optional headers, timeout, enabled and oauth.
- No environment-variable interpolation in headers, so the key goes in literally. Do not commit .zed/settings.json.
- If you see no Add Remote Server button, update Zed. Very old builds were stdio-only and needed a bridge process.
What to ask once it is connected
There are no commands to learn. Ask in your own words and Zed picks the right tool - there are twelve, covering verification, sending-domain deliverability and blacklist checks.
What Zed 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 Zed 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.
Zed FAQ
Zed Industries's own reference: Zed 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.