swath-mcp
# Swath MCP Server
MCP server for [Swath API](https://swathapi.com) — **America's first AI-native storm intelligence API**. Radar-verified hail and damaging-wind swaths, and every property under them, inside Claude, ChatGPT, or any MCP client.
[](https://glama.ai/mcp/servers/@vibecodebeast/swath-mcp)
## Tools
| Tool | What it does |
|---|---|
| `find_storms` | Radar-verified storms (hail ≥ threshold, wind) for an area/timeframe |
| `get_swath_report` | Every property under a swath — roof age, owner-occupancy, assessed value |
| `get_report_quote` | Exact credit cost of a report before you run it |
| `email_report` | Emails you the report summary |
| `lookup_property` | Storm history + parcel intel for one address |
| `create_monitor` / `list_monitors` | Watch a territory; webhook + email alerts on radar verification |
| `get_usage` | Credits used / remaining |
| `show_swath_map` | Gradient swath map image |
## Quick start (Claude Desktop)
```json
{
"mcpServers": {
"swath": {
"command": "npx",
"args": ["-y", "tsx", "/path/to/swath-mcp/src/index.ts"],
"env": { "SWATH_API_KEY": "sk_..." }
}
}
}
```
No key yet? Every tool answers with a signup hint — get a free key (100 credits) at [swathapi.com](https://swathapi.com).
**claude.ai / ChatGPT users:** you don't need this repo — add the hosted connector instead: `https://swathapi.com/mcp` (OAuth, no key handling). See [swathapi.com/integrations](https://swathapi.com/integrations).
## Env
- `SWATH_API_KEY` — your API key (`sk_...`)
- `SWATH_API_URL` — API base (default `https://swathapi.com`)
## Data honesty
Hail is verified against NOAA MRMS radar; wind against measured NWS storm reports. No forecasts, no fabricated uptime — see [swathapi.com/status](https://swathapi.com/status).
Developed by [vibecodebeast.ai](https://vibecodebeast.ai).
TDQS
Scored across 8 tools
Each tool targets a clearly distinct action: finding storms, pricing a report, fetching report data, mapping a swath, emailing a summary, looking up a property, listing monitors, and checking usage. The close pairing of get_swath_report and get_report_quote is resolved by the quote tool explicitly costing without returning rows.
All tool names follow a consistent verb_noun snake_case pattern (get_swath_report, find_storms, list_monitors, show_swath_map). Verb choices match their actions and no mixed casing or stylistic drift is present.
Eight tools is well-scoped for a storm-swath data API. Each tool earns its place covering discovery, quotation, retrieval, visualization, delivery, property lookup, account state, and usage.
The core workflow of finding a storm, quoting and fetching a swath report, viewing it on a map, and emailing a summary is well covered. The main gaps are that list_monitors has no corresponding create/update/delete tools, and there is no dedicated storm detail endpoint beyond find_storms.