Use Zipawa inside Claude

Connect Zipawa's live, ZIP-level disaster & emergency event context to Claude — or any AI assistant that speaks the Model Context Protocol — so it can tell you where a campaign would be tone-deaf, before you hit send. No code required.

Option 1 — Add the connector (no install, free)

In Claude's settings, add a custom connector and paste this URL. It works instantly, needs no API key, and runs in any MCP-compatible client:

https://zipawa.com/mcp

The free connector screens up to 50 ZIP codes per request — plenty to ask “where should I not market today?” in plain language.

Option 2 — Run the package (for developers)

Prefer a local server with your own API key and the full limits (1,000 ZIPs per call)? Add the npm package to your MCP client config:

{
  "mcpServers": {
    "zipawa": {
      "command": "npx",
      "args": ["-y", "@zipawa/mcp"],
      "env": { "ZIPAWA_API_KEY": "za_your_key" }
    }
  }
}

Get a free API key → (5,000 ZIP screenings/month, no credit card).

What you can ask

What it can do

check_event_contextFull live event context for your ZIP codes — what's forecast, active, or in recovery, with severity, time windows, plain-language descriptions, and official source links.
get_suppressionsThe fast answer: which ZIP codes to suppress from marketing right now, and which are clear.

Wire it into your own systems

The same data powers the Zipawa REST API — filter by timing, category, and severity across thousands of ZIPs in one call.

Get your free API key