Verify email in Cursor
Cursor reads MCP servers from an mcp.json file, globally or per project. Add the Qualisend endpoint and the agent can verify addresses and clean lists while it writes your signup flow.
- MCP endpoint
- https://app.qualisend.com/api/mcp
- Authentication
- Sign-in or API key
- Available on
- All plans. Enterprise admins can restrict which MCP servers members may run; team admins can distribute shared servers through a team marketplace.
Connect it to Cursor
You need a Qualisend account - the free plan includes 100 verification credits that never expire - and Cursor itself. Steps checked against Anysphere's documentation in September 2026.
- 1
Open the MCP settings
Open Customize in the sidebar, then click MCPs. Older builds put it under Cursor Settings -> Tools & Integrations.
- 2
Add a custom MCP server
The Add button opens mcp.json for editing. You can also edit it directly: ~/.cursor/mcp.json for every project, or <project>/.cursor/mcp.json for one.
- 3
Paste the entry
Use the block below. For sign-in instead of a key, delete the headers object entirely so Cursor sees the 401 and starts the OAuth flow.
- 4
Save and connect
The server appears in the list. If it needs sign-in, click Connect and approve in the browser. A green dot and a visible tool list means it is live.
Sign-in or API key
Either. Leave headers out and Cursor runs the browser sign-in when it sees the 401; include a bearer header and it uses your API key instead. The header path has been the more reliable of the two.
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
~/.cursor/mcp.json (or <project>/.cursor/mcp.json)Export QUALISEND_API_KEY in the environment Cursor itself was launched from - a GUI launch often does not inherit your shell profile.
{
"mcpServers": {
"qualisend": {
"url": "https://app.qualisend.com/api/mcp",
"headers": {
"Authorization": "Bearer ${env:QUALISEND_API_KEY}"
}
}
}
}Worth knowing
- Remote entries have no type field. The presence of url is what makes it remote - adding "type": "stdio" breaks it.
- ${env:NAME} only resolves against the environment Cursor was started from. Launching from Finder or the Start menu usually means your shell profile was never read.
- Never commit .cursor/mcp.json with a literal key in it - the file is plaintext on disk.
- Cursor caps how many MCP tools can be enabled at once. If you run several servers, turn off the tools you do not need.
What to ask once it is connected
There are no commands to learn. Ask in your own words and Cursor picks the right tool - there are twelve, covering verification, sending-domain deliverability and blacklist checks.
What Cursor 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 Cursor 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.
Cursor FAQ
Anysphere's own reference: Cursor 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.