Connect Zipawa to Claude: let your AI tell you where not to market

More and more marketers draft, schedule, and even send campaigns through AI assistants like Claude. It's fast — but your assistant has a blind spot: it has no idea that a wildfire tore through three of the ZIP codes on your send list this morning.

That's the gap Zipawa's connector closes. Zipawa tracks live disaster and emergency events — wildfires, hurricanes, floods, federal disaster declarations — and maps them down to the ZIP code. Connect it to Claude through the Model Context Protocol (MCP), and your assistant can check that context in the same conversation where it's writing your campaign.

Setup takes about a minute, no code

In Claude's settings, add a custom connector and paste https://zipawa.com/mcp. There's a full walkthrough on the Use Zipawa in Claude page. From then on, you can just ask, in plain language:

• “Before I send this promo to 90001, 93534, and 33401 — anywhere I should hold off?”
• “What's happening in ZIP 99558 right now, and until when?”

Claude calls Zipawa, sees that (say) 93534 is in an active wildfire zone, and tells you to drop it from the send — with the reason and a link to the official source. No dashboards, no CSV exports, no integration project.

When you outgrow the connector

The free connector screens up to 50 ZIPs per request — enough for a quick gut-check before a send. When you need to screen thousands at once or wire suppression into your own ESP or campaign tooling, the same data is available through the REST API, the free list checker, and the npm package for developers. It's all the same event feed underneath.