No2Bounce for Windsurf

Every marketing team knows the quiet cost of a bad email list: bounced campaigns, wasted sends, and a sender reputation that takes months to repair after one bad blast. Most teams do not catch it until the bounce report lands, and by then the damage is done. The No2Bounce MCP server moves that check earlier, into the conversation where you are already planning your outreach. 

MCP, the Model Context Protocol, lets Cascade reach outside the editor and call real external tools on your behalf. Instead of copying an address into a separate dashboard, you just ask. The No2Bounce MCP server connects Cascade directly to the validation API, so a check that used to interrupt your work becomes one line in the same thread.

• Single address: a deliverability score out of 100, a status (valid, invalid, risky), and a sub-status explaining

why: confirmed mailbox, catch-all domain, role-based address, or likely bounce. 

• Bulk lists: up to 10,000 addresses per request, returned as a downloadable CSV. 

• Long-running jobs: poll a job by tracking ID and pull results whenever they are ready, useful for auditing an old list or validating before a CRM import. 

• Account status: confirm your API key is active and check your remaining credit balance, so you are never caught mid-campaign.

First make sure MCP is switched on. Open Windsurf Settings with Cmd and comma, or Ctrl and comma on Windows, go to Advanced Settings, find the Cascade section, and enable Model Context Protocol. 

Then install the server with one npm command, grab your API key from the No2Bounce dashboard, and add a short block to the Windsurf MCP config file. On macOS and Linux it lives at ~/.codeium/windsurf/mcp_config.json; on Windows at %USERPROFILE%\.codeium\windsurf\mcp_config.json. The quickest way to open it is the MCPs icon in the top right of the Cascade panel, then Configure. 

npm install -g no2bounce-mcp 

{ 

 "mcpServers": { 

 "no2bounce": { 

 "command": "no2bounce-mcp", 

 "args": ["--api-key=YOUR_API_KEY"] 

 } 

 }

} 

Refresh the server list and the No2Bounce tools appear in Cascade. Windsurf lets you toggle individual tools rather than whole servers, so you can expose only the checks your team actually uses. There is no server to host, no build step, nothing else to maintain, and your API key stays local the whole time. 

The entire setup above can be handed to Cascade itself as a single prompt, no manual file editing required. Paste the prompt below, replace YOUR_API_KEY with your real token, and let it do the rest. 

Install and set up the No2Bounce MCP server for me. Run "npm install -g no2bounce-mcp" globally, then locate my Windsurf MCP config file for this OS (create it if it does not exist), and add a "no2bounce" entry under mcpServers using command "no2bounce-mcp" and args ["--api-key=YOUR_API_KEY"]. Show me the final config file content, then tell me to refresh the MCP server list and confirm the no2bounce tools are available. 

From there, it is just conversation. Paste an address, paste a list, or ask about your account, and let Cascade check it before you hit send. 

• Get your API key → https://app.no2bounce.com/api

Package Info

• View on npmx : https://npmx.dev/package/no2bounce-mcp
• Published by no2bounce-com on npm : https://www.npmjs.com/~no2bounce-com