@cyanheads/fema-mcp-server 0.1.1

package/README.md

@@ -0,0 +1,340 @@
+<div align="center">
+  <h1>@cyanheads/fema-mcp-server</h1>
+  <p><b>Query FEMA disaster declarations, public assistance grants, housing aid, and NFIP flood insurance claims via MCP. STDIO or Streamable HTTP.</b>
+  <div>8 Tools • 1 Resource</div>
+  </p>
+</div>
+
+<div align="center">
+
+[![Version](https://img.shields.io/badge/Version-0.1.1-blue.svg?style=flat-square)](./CHANGELOG.md) [![License](https://img.shields.io/badge/License-Apache%202.0-orange.svg?style=flat-square)](./LICENSE) [![Docker](https://img.shields.io/badge/Docker-ghcr.io-2496ED?style=flat-square&logo=docker&logoColor=white)](https://github.com/users/cyanheads/packages/container/package/fema-mcp-server) [![MCP SDK](https://img.shields.io/badge/MCP%20SDK-^1.29.0-green.svg?style=flat-square)](https://modelcontextprotocol.io/) [![npm](https://img.shields.io/npm/v/@cyanheads/fema-mcp-server?style=flat-square&logo=npm&logoColor=white)](https://www.npmjs.com/package/@cyanheads/fema-mcp-server) [![TypeScript](https://img.shields.io/badge/TypeScript-^6.0.3-3178C6.svg?style=flat-square)](https://www.typescriptlang.org/) [![Bun](https://img.shields.io/badge/Bun-v1.3.11-blueviolet.svg?style=flat-square)](https://bun.sh/)
+
+</div>
+
+<div align="center">
+
+[![Install in Claude Desktop](https://img.shields.io/badge/Install_in-Claude_Desktop-D97757?style=for-the-badge&logo=anthropic&logoColor=white)](https://github.com/cyanheads/fema-mcp-server/releases/latest/download/fema-mcp-server.mcpb) [![Install in Cursor](https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/en/install-mcp?name=fema-mcp-server&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIkBjeWFuaGVhZHMvZmVtYS1tY3Atc2VydmVyIl19) [![Install in VS Code](https://img.shields.io/badge/VS_Code-Install_Server-0098FF?style=for-the-badge&logo=visualstudiocode&logoColor=white)](https://vscode.dev/redirect?url=vscode:mcp/install?%7B%22name%22%3A%22fema-mcp-server%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22%40cyanheads%2Ffema-mcp-server%22%5D%7D)
+
+[![Framework](https://img.shields.io/badge/Built%20on-@cyanheads/mcp--ts--core-67E8F9?style=flat-square)](https://www.npmjs.com/package/@cyanheads/mcp-ts-core)
+
+</div>
+
+---
+
+## Tools
+
+Eight tools covering the OpenFEMA data surface — convenience tools for the headline datasets, SQL analytics over large NFIP result sets via DuckDB canvas, and a generic escape hatch for datasets the convenience tools don't cover:
+
+| Tool | Description |
+|:---|:---|
+| `fema_search_disasters` | Search federal disaster declarations by state, incident type, declaration type, date range, and county |
+| `fema_get_disaster` | Fetch all designated-area records for a specific disaster by disaster number |
+| `fema_get_public_assistance` | Public assistance funded projects for a disaster or state — where federal recovery money went |
+| `fema_get_housing_assistance` | Individual assistance housing data for a disaster — owner and renter breakdowns by county/ZIP |
+| `fema_search_nfip` | NFIP flood insurance claims for a state, county, or ZIP, with optional DataCanvas spillover for SQL analytics |
+| `fema_dataframe_describe` | List columns and row counts for DataCanvas tables staged by `fema_search_nfip` |
+| `fema_dataframe_query` | Run a SELECT query against a DataCanvas table staged by `fema_search_nfip` |
+| `fema_query_dataset` | Generic OData query against any OpenFEMA v2 dataset — escape hatch for datasets the convenience tools don't cover |
+
+### `fema_search_disasters`
+
+The primary entry point — "what disasters were declared in Texas in 2025?"
+
+- Filter by state (2-letter code), incident type (Hurricane, Flood, Wildfire, etc.), declaration type (`DR`/`EM`/`FM`), date range, and county
+- Returns deduplicated declaration-level summaries — one row per declaration, not per designated area
+- Includes disaster number (the join key for PA and housing tools), title, state, incident type, declaration/incident dates, programs declared (IA/PA/HM), and `designatedAreaCount`
+- Paginated via `limit` / `offset`
+
+---
+
+### `fema_get_disaster`
+
+Fetch all designated-area records for a specific FEMA disaster number.
+
+- Returns every county/municipality row for the declaration with programs activated, incident period, and FIPS codes
+- Use after `fema_search_disasters` to drill into a specific event; the disaster number chains to PA and housing tools
+- `DisasterDeclarationsSummaries` returns one row per designated area — a single declaration can span dozens of counties
+
+---
+
+### `fema_get_public_assistance`
+
+Retrieve PA funded project details — where federal recovery money went after a disaster.
+
+- Filter by `disaster_number`, `state`, or `county`; at least one of `disaster_number` or `state` is required
+- Returns applicant, damage category, project size/status, federal share obligated, and total obligated
+- Useful for journalists, researchers, and oversight analysts tracking federal grant flows
+
+---
+
+### `fema_get_housing_assistance`
+
+Individual assistance housing data for a disaster, broken down by county and ZIP.
+
+- Returns owner and renter breakdowns via `type` param (`owners`/`renters`/`both`)
+- Fields include valid registrations, total inspected, total damage, approved IHP amounts, repair/rental/other-needs amounts, and max grants
+- Covers `HousingAssistanceOwners` and `HousingAssistanceRenters` datasets in a single call
+
+---
+
+### `fema_search_nfip`
+
+NFIP flood insurance claims with optional DuckDB-backed SQL analytics for large result sets.
+
+- Requires at minimum a `state` filter — unfiltered NFIP Claims is 2.7M rows
+- Additional filters: `county_code`, `zip_code`, `year_from`, `year_to`; pagination via `limit`
+- When `CANVAS_PROVIDER_TYPE=duckdb` is set and results exceed the inline cap, the full result set spills to a DataCanvas table and returns a `canvas_id` handle
+- Use `fema_dataframe_describe` to inspect the schema, then `fema_dataframe_query` for aggregation, grouping, and time-series analysis without re-fetching
+
+---
+
+### `fema_dataframe_describe` / `fema_dataframe_query`
+
+In-conversation SQL analytics over NFIP Claims data staged by `fema_search_nfip` on a DuckDB-backed DataCanvas.
+
+- `fema_dataframe_describe`: lists columns, types, and row count for a canvas table — use before writing a query
+- `fema_dataframe_query`: runs a single SELECT statement against the staged table; standard DuckDB SQL (GROUP BY, SUM, window functions, time-series)
+- Workflow: `fema_search_nfip` (with canvas enabled) → `fema_dataframe_describe` → `fema_dataframe_query`
+- Read-only — writes, DDL, and DROP are rejected by the framework SQL gate
+
+---
+
+### `fema_query_dataset`
+
+Generic OData query against any OpenFEMA v2 dataset — the escape hatch for datasets the convenience tools don't cover.
+
+- Accepts raw `$filter`, `$select`, `$orderby`, `limit`, and `offset` params
+- Dataset name must match an actual OpenFEMA endpoint (e.g. `FimaNfipPolicies`, `IndividualAssistanceHousingRegistrantsLargeDisasters`)
+- Validates that the API returns JSON (Content-Type check) and surfaces structured error codes on 400 responses
+
+## Resources and prompts
+
+| Type | Name | Description |
+|:---|:---|:---|
+| Resource | `fema://disaster/{disasterNumber}` | Summary for a specific FEMA disaster declaration — title, state, incident type, programs, incident period |
+
+All resource data is also reachable via tools. Use `fema_get_disaster` for the same data with pagination and full designated-area detail.
+
+## Features
+
+Built on [`@cyanheads/mcp-ts-core`](https://www.npmjs.com/package/@cyanheads/mcp-ts-core):
+
+- Declarative tool, resource, and prompt definitions — single file per primitive, framework handles registration and validation
+- Unified error handling — handlers throw, framework catches, classifies, and formats
+- Pluggable auth: `none`, `jwt`, `oauth`
+- Swappable storage backends: `in-memory`, `filesystem`, `Supabase`, `Cloudflare KV/R2/D1`
+- Structured logging with optional OpenTelemetry tracing
+- STDIO and Streamable HTTP transports
+
+FEMA/OpenFEMA-specific:
+
+- Typed OpenFEMA REST client with OData parameter building (`%24`-encoded to satisfy Akamai's Drupal layer), response parsing, and structured error classification (JSON 400 vs HTML 404)
+- Automatic deduplication of `DisasterDeclarationsSummaries` — one row per designated area collapsed to declaration-level summaries with `designatedAreaCount`
+- NFIP Claims guard: `state` filter is required to prevent unbounded 2.7M-row fetches
+- DataCanvas spillover for NFIP analytics — large NFIP result sets materialize as DuckDB tables queryable via SQL without re-fetching
+- No API keys required — OpenFEMA is a free, public API
+
+Agent-friendly output:
+
+- Disaster number is the explicit join key across all datasets — every tool that touches a disaster surfaces it prominently so agents can chain calls without re-searching
+- Typed error contracts on every tool — `invalid_state`, `no_results`, `missing_filter`, `state_required`, `unknown_dataset`, `invalid_filter` — with recovery hints telling agents the concrete next step
+- `designatedAreaCount` on search results so agents know whether to drill in with `fema_get_disaster` without having to fetch the full record first
+
+## Getting started
+
+Add the following to your MCP client configuration file.
+
+```json
+{
+  "mcpServers": {
+    "fema-mcp-server": {
+      "type": "stdio",
+      "command": "bunx",
+      "args": ["@cyanheads/fema-mcp-server@latest"],
+      "env": {
+        "MCP_TRANSPORT_TYPE": "stdio",
+        "MCP_LOG_LEVEL": "info"
+      }
+    }
+  }
+}
+```
+
+Or with npx (no Bun required):
+
+```json
+{
+  "mcpServers": {
+    "fema-mcp-server": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["-y", "@cyanheads/fema-mcp-server@latest"],
+      "env": {
+        "MCP_TRANSPORT_TYPE": "stdio",
+        "MCP_LOG_LEVEL": "info"
+      }
+    }
+  }
+}
+```
+
+Or with Docker:
+
+```json
+{
+  "mcpServers": {
+    "fema-mcp-server": {
+      "type": "stdio",
+      "command": "docker",
+      "args": [
+        "run", "-i", "--rm",
+        "-e", "MCP_TRANSPORT_TYPE=stdio",
+        "ghcr.io/cyanheads/fema-mcp-server:latest"
+      ]
+    }
+  }
+}
+```
+
+For Streamable HTTP, set the transport and start the server:
+
+```sh
+MCP_TRANSPORT_TYPE=http MCP_HTTP_PORT=3010 bun run start:http
+# Server listens at http://localhost:3010/mcp
+```
+
+To enable DuckDB-backed SQL analytics for NFIP Claims:
+
+```json
+{
+  "mcpServers": {
+    "fema-mcp-server": {
+      "type": "stdio",
+      "command": "bunx",
+      "args": ["@cyanheads/fema-mcp-server@latest"],
+      "env": {
+        "MCP_TRANSPORT_TYPE": "stdio",
+        "CANVAS_PROVIDER_TYPE": "duckdb"
+      }
+    }
+  }
+}
+```
+
+### Prerequisites
+
+- [Bun v1.3.0](https://bun.sh/) or higher (or Node.js v24+).
+- No API keys required — OpenFEMA is a free, public API.
+- Optional: set `CANVAS_PROVIDER_TYPE=duckdb` to enable SQL analytics over large NFIP Claims result sets.
+
+### Installation
+
+1. **Clone the repository:**
+
+```sh
+git clone https://github.com/cyanheads/fema-mcp-server.git
+```
+
+2. **Navigate into the directory:**
+
+```sh
+cd fema-mcp-server
+```
+
+3. **Install dependencies:**
+
+```sh
+bun install
+```
+
+4. **Configure environment:**
+
+```sh
+cp .env.example .env
+# edit .env — no required vars, but CANVAS_PROVIDER_TYPE=duckdb enables SQL analytics
+```
+
+## Configuration
+
+All configuration is validated at startup via Zod schemas in `src/config/server-config.ts`. Key environment variables:
+
+| Variable | Description | Default |
+|:---------|:------------|:--------|
+| `FEMA_BASE_URL` | Override the OpenFEMA API base URL. | `https://www.fema.gov/api/open/v2` |
+| `FEMA_REQUEST_TIMEOUT_MS` | Per-request HTTP timeout in milliseconds. NFIP county queries can be slow. | `30000` |
+| `CANVAS_PROVIDER_TYPE` | Set to `duckdb` to enable DataCanvas for NFIP Claims analytics. Without it, `fema_search_nfip` inlines results up to the cap. | — |
+| `MCP_TRANSPORT_TYPE` | Transport: `stdio` or `http`. | `stdio` |
+| `MCP_HTTP_PORT` | HTTP server port. | `3010` |
+| `MCP_AUTH_MODE` | Auth mode: `none`, `jwt`, or `oauth`. | `none` |
+| `MCP_LOG_LEVEL` | Log level (`debug`, `info`, `warning`, `error`, etc.). | `info` |
+| `LOGS_DIR` | Directory for log files (Node.js only). | `<project-root>/logs` |
+| `OTEL_ENABLED` | Enable [OpenTelemetry instrumentation](https://github.com/cyanheads/mcp-ts-core/tree/main/docs/telemetry). | `false` |
+
+See [`.env.example`](./.env.example) for the full list of optional overrides.
+
+## Running the server
+
+### Local development
+
+- **Build and run:**
+
+  ```sh
+  # One-time build
+  bun run rebuild
+
+  # Run the built server
+  bun run start:stdio
+  # or
+  bun run start:http
+  ```
+
+- **Run checks and tests:**
+
+  ```sh
+  bun run devcheck   # Lint, format, typecheck, security
+  bun run test       # Vitest test suite
+  bun run lint:mcp   # Validate MCP definitions against spec
+  ```
+
+### Docker
+
+```sh
+docker build -t fema-mcp-server .
+docker run --rm -e MCP_TRANSPORT_TYPE=stdio fema-mcp-server
+```
+
+The Dockerfile defaults to HTTP transport, stateless session mode, and logs to `/var/log/fema-mcp-server`. OpenTelemetry peer dependencies are installed by default — build with `--build-arg OTEL_ENABLED=false` to omit them. The `@duckdb/node-api` native binary is copied from the build stage, so the production image doesn't need build tools.
+
+## Project structure
+
+| Directory | Purpose |
+|:----------|:--------|
+| `src/index.ts` | `createApp()` entry point — registers tools/resources and inits services. |
+| `src/config` | Server-specific environment variable parsing and validation with Zod. |
+| `src/mcp-server/tools` | Tool definitions (`*.tool.ts`) — one file per tool. |
+| `src/mcp-server/resources` | Resource definitions (`*.resource.ts`). |
+| `src/services/openfema` | OpenFEMA REST API client — OData param builder, response parser, error classifier, retry wrapper. |
+| `src/services/canvas` | DataCanvas integration — DuckDB spillover for large NFIP result sets. |
+| `tests/` | Unit and integration tests mirroring `src/`. |
+
+## Development guide
+
+See [`CLAUDE.md`](./CLAUDE.md) for development guidelines and architectural rules. The short version:
+
+- Handlers throw, framework catches — no `try/catch` in tool logic
+- Use `ctx.log` for request-scoped logging, `ctx.state` for tenant-scoped storage
+- Register new tools and resources via the barrels in `src/mcp-server/*/definitions/index.ts`
+- Wrap external API calls: validate raw → normalize to domain type → return output schema; never fabricate missing fields
+
+## Contributing
+
+Issues and pull requests are welcome. Run checks and tests before submitting:
+
+```sh
+bun run devcheck
+bun run test
+```
+
+## License
+
+Apache-2.0 — see [LICENSE](./LICENSE) for details.

package/changelog/0.1.x/0.1.1.md

@@ -0,0 +1,41 @@
+---
+summary: "Initial public release — 8 tools, 1 resource over the OpenFEMA API (disaster declarations, public assistance, housing aid, NFIP claims) with DataCanvas SQL and OData injection hardening"
+breaking: false
+security: true
+---
+
+# 0.1.1 — 2026-06-05
+
+Initial public release of `@cyanheads/fema-mcp-server`. Provides 8 MCP tools and 1 resource over the [OpenFEMA API v2](https://www.fema.gov/about/openfema/api):
+
+- **`fema_search_disasters`** — search federal disaster declarations by state, incident type, declaration type, date range, and county
+- **`fema_get_disaster`** — fetch all designated-area records for a specific disaster by number
+- **`fema_get_public_assistance`** — public assistance funded projects for a disaster or state
+- **`fema_get_housing_assistance`** — individual assistance housing data by disaster — owner and renter breakdowns by county/ZIP
+- **`fema_search_nfip`** — NFIP flood insurance claims for a state, county, or ZIP, with optional DataCanvas spillover for SQL analytics
+- **`fema_dataframe_describe`** — list columns and row counts for DataCanvas tables staged by `fema_search_nfip`
+- **`fema_dataframe_query`** — run a SELECT query against a DataCanvas table staged by `fema_search_nfip`
+- **`fema_query_dataset`** — generic OData query against any OpenFEMA v2 dataset (escape hatch for datasets the convenience tools don't cover)
+- **`fema://disaster/{disasterNumber}`** resource — summary for a specific FEMA disaster declaration
+
+## Added
+
+- **`fema_search_disasters`** — search disaster declarations; deduplicated to one row per declaration with disaster number, title, state, incident type, declaration/incident dates, programs declared (IA/PA/HM), and `designatedAreaCount`
+- **`fema_get_disaster`** — returns all designated-area records for a disaster number with full program eligibility breakdown
+- **`fema_get_public_assistance`** — funded project records with applicant, project amount, category codes, and status; filterable by state, disaster number, county, and incident type
+- **`fema_get_housing_assistance`** — owner and renter household registrant and assistance totals by county and ZIP for a disaster
+- **`fema_search_nfip`** — NFIP claims with state/county/ZIP filters; spills to a named DuckDB DataCanvas table when result sets exceed the inline preview budget (`CANVAS_PROVIDER_TYPE=duckdb`)
+- **`fema_dataframe_describe`** — enumerates registered DataCanvas tables with column names, types, row count, and TTL; supports follow-up SQL analytics on NFIP data
+- **`fema_dataframe_query`** — single-statement SELECT SQL executed against DataCanvas tables via DuckDB; read-only, enforced by the framework SQL gate
+- **`fema_query_dataset`** — generic OData v4 escape hatch for any `/api/open/v2/` endpoint not covered by the convenience tools; accepts `$filter`, `$select`, `$orderby`, `$top`, `$skip`
+- **`fema://disaster/{disasterNumber}`** resource — disaster declaration summary keyed by disaster number
+- **`escapeODataString`** helper in `openfema-service.ts` — sanitizes user-supplied string values injected into OData `$filter` expressions across all tools
+- **DataCanvas support** (`CANVAS_PROVIDER_TYPE=duckdb`) — `fema_search_nfip` spills large result sets to named DuckDB tables for SQL follow-up; inline preview bounded at 100 KB
+
+## Changed
+
+- **`Dockerfile`** — copies `node_modules` from the build stage so `@duckdb/node-api`'s pre-compiled native binary is preserved in the production image without reinstalling build tools at runtime
+
+## Security
+
+- **OData injection hardening** — `escapeODataString` sanitizes single-quote characters (`'` → `''`) in all user-supplied string values before interpolation into OData `$filter` expressions in `fema_search_disasters`, `fema_get_public_assistance`, and `fema_search_nfip`; prevents filter injection via crafted string inputs

package/changelog/template.md

@@ -0,0 +1,127 @@
+---
+# FORMAT REFERENCE — do not edit. Copy this file to
+# `changelog/<major.minor>.x/<version>.md` (e.g. `changelog/0.8.x/0.8.6.md`)
+# to author a new release. Set that file's H1 to `# <version> — YYYY-MM-DD`
+# with a concrete date.
+
+# Required. One-line GitHub Release-style headline. 350 character cap.
+# Default short and scannable. Don't pad, don't stitch unrelated changes with
+# semicolons — pick the headline. Quotes required: unquoted YAML treats `: `
+# inside the value as a key separator and fails GitHub's strict parser.
+summary: ""
+
+# Set `true` when consumers must change code to upgrade: API removals,
+# signature changes, config renames, behavior changes that break existing
+# usage. Flagged as `Breaking` in the rollup.
+breaking: false
+
+# Set `true` if this release contains any security fix. Pairs with the
+# `## Security` section below. Flagged as `Security` in the rollup so
+# users can triage upgrade urgency at a glance.
+security: false
+
+# Optional free-form notes for maintenance agents processing this release.
+# Not rendered in CHANGELOG — consumed by agents running `maintenance` on
+# downstream servers. Use for adoption instructions that don't fit the
+# human-facing sections: new files to create, fields to populate, one-time
+# migration steps. Omit the field entirely when there's nothing to say.
+# agent-notes: |
+#   <instructions for downstream maintenance agents>
+---
+
+# <version> — YYYY-MM-DD
+
+<!--
+  AUTHORING GUIDE — applies to the new per-version file you create from this
+  template.
+
+  Audience: someone scanning release notes to decide what affects them. Lead
+  each bullet with the symbol or concept name in **bold** so they can skip
+  what's irrelevant and zoom in on what's not.
+
+  Tone: terse, fact-dense, not verbose. Default to one sentence per bullet —
+  name the symbol, state what changed, stop. Use a second sentence only when
+  it carries weight. If a bullet feels long, it is.
+
+  Cut: mechanism walkthroughs (those belong in JSDoc, CLAUDE.md/AGENTS.md, or the
+  relevant skill), ceremonial framings ("This release introduces…",
+  backwards-compat paragraphs), file-by-file test enumerations, internal
+  implementation notes. Prefer code/symbol names over English re-explanations.
+
+  Narrative intro: skip by default. Add one short sentence only when the
+  release theme genuinely needs framing the bullets can't carry.
+
+  Sections: Keep a Changelog order — Added, Changed, Deprecated, Removed,
+  Fixed, Security. Include only sections with entries; delete the rest
+  (including the commented-out scaffolding below). Don't ship empty headers.
+
+  Include: every distinct fact a reader needs to adopt or audit the release —
+  new exports, signatures, lint rule IDs, env vars, breaking changes, version
+  bumps on shipped skills. Nothing more.
+
+  Links: link issues, PRs, docs, or skills where they help a reader jump to
+  context. Once per item per entry — don't re-link the same issue in summary,
+  narrative, and bullet. Skip links for inline symbol names; code spans speak
+  for themselves.
+
+  Issue/PR URLs: use full URLs. GitHub's bare `#NN` auto-link only resolves
+  inside its own UI, not in npm reads or local editors.
+
+      [#38](https://github.com/cyanheads/mcp-ts-core/issues/38)   ← issue
+      [#42](https://github.com/cyanheads/mcp-ts-core/pull/42)     ← PR
+
+  Verify numbers exist before linking (`gh issue view NN`, `gh pr view NN`).
+  Never speculate on a future number — `#42` for an upcoming PR silently
+  resolves to whatever real item already owns 42, and timeline previews pull
+  in that unrelated item's metadata.
+
+  TAG ANNOTATIONS — the annotated tag body renders as the GitHub Release body
+  via `gh release create --notes-from-tag`. The tag is a derivative of this
+  changelog entry — a condensed, scannable version, not a copy. Format:
+
+    <theme — omit version number, GitHub prepends it>
+                                                          ← blank line
+    <1-2 sentence context: what this release does>
+                                                          ← blank line
+    Dependency bumps:                                     ← section header
+                                                          ← blank line
+    - `@cyanheads/mcp-ts-core` ^0.9.1 → ^0.9.6          ← bullet
+                                                          ← blank line
+    Changed:                                              ← only sections with entries
+                                                          ← blank line
+    - `format()` output includes `query` in text mode
+                                                          ← blank line
+    Added:
+                                                          ← blank line
+    - `manifest.json` scaffolded for MCPB bundle support
+    - Install badges (Claude Desktop, Cursor, VS Code)
+                                                          ← blank line
+    <N> tests pass; `bun run devcheck` clean.             ← footer
+
+  Never a flat comma-separated string. Always structured markdown with
+  sections. The tag must scan well as a rendered GitHub Release page.
+-->
+
+## Added
+
+-
+
+## Changed
+
+-
+
+<!-- ## Deprecated
+
+- -->
+
+<!-- ## Removed
+
+- -->
+
+## Fixed
+
+-
+
+<!-- ## Security
+
+- -->

package/dist/config/server-config.d.ts

@@ -0,0 +1,9 @@
+/**
+ * @fileoverview Server-specific environment variable configuration for fema-mcp-server.
+ * @module config/server-config
+ */
+export declare function getServerConfig(): {
+    baseUrl: string;
+    requestTimeoutMs: number;
+};
+//# sourceMappingURL=server-config.d.ts.map

package/dist/config/server-config.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"server-config.d.ts","sourceRoot":"","sources":["../../src/config/server-config.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAeH,wBAAgB,eAAe;;;EAM9B"}

package/dist/config/server-config.js

@@ -0,0 +1,22 @@
+/**
+ * @fileoverview Server-specific environment variable configuration for fema-mcp-server.
+ * @module config/server-config
+ */
+import { z } from '@cyanheads/mcp-ts-core';
+import { parseEnvConfig } from '@cyanheads/mcp-ts-core/config';
+const ServerConfigSchema = z.object({
+    baseUrl: z.string().default('https://www.fema.gov/api/open/v2').describe('OpenFEMA API base URL'),
+    requestTimeoutMs: z.coerce
+        .number()
+        .default(30000)
+        .describe('HTTP request timeout in milliseconds'),
+});
+let _config;
+export function getServerConfig() {
+    _config ??= parseEnvConfig(ServerConfigSchema, {
+        baseUrl: 'FEMA_BASE_URL',
+        requestTimeoutMs: 'FEMA_REQUEST_TIMEOUT_MS',
+    });
+    return _config;
+}
+//# sourceMappingURL=server-config.js.map

package/dist/config/server-config.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"server-config.js","sourceRoot":"","sources":["../../src/config/server-config.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,OAAO,EAAE,CAAC,EAAE,MAAM,wBAAwB,CAAC;AAC3C,OAAO,EAAE,cAAc,EAAE,MAAM,+BAA+B,CAAC;AAE/D,MAAM,kBAAkB,GAAG,CAAC,CAAC,MAAM,CAAC;IAClC,OAAO,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,OAAO,CAAC,kCAAkC,CAAC,CAAC,QAAQ,CAAC,uBAAuB,CAAC;IACjG,gBAAgB,EAAE,CAAC,CAAC,MAAM;SACvB,MAAM,EAAE;SACR,OAAO,CAAC,KAAK,CAAC;SACd,QAAQ,CAAC,sCAAsC,CAAC;CACpD,CAAC,CAAC;AAEH,IAAI,OAAuD,CAAC;AAE5D,MAAM,UAAU,eAAe;IAC7B,OAAO,KAAK,cAAc,CAAC,kBAAkB,EAAE;QAC7C,OAAO,EAAE,eAAe;QACxB,gBAAgB,EAAE,yBAAyB;KAC5C,CAAC,CAAC;IACH,OAAO,OAAO,CAAC;AACjB,CAAC"}

package/dist/index.d.ts

@@ -0,0 +1,7 @@
+#!/usr/bin/env node
+/**
+ * @fileoverview fema-mcp-server MCP server entry point.
+ * @module index
+ */
+export {};
+//# sourceMappingURL=index.d.ts.map

package/dist/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":";AACA;;;GAGG"}

package/dist/index.js

@@ -0,0 +1,45 @@
+#!/usr/bin/env node
+/**
+ * @fileoverview fema-mcp-server MCP server entry point.
+ * @module index
+ */
+import { createApp } from '@cyanheads/mcp-ts-core';
+import { femaDisasterResource } from './mcp-server/resources/definitions/fema-disaster.resource.js';
+import { femaDataframeDescribe } from './mcp-server/tools/definitions/fema-dataframe-describe.tool.js';
+import { femaDataframeQuery } from './mcp-server/tools/definitions/fema-dataframe-query.tool.js';
+import { femaGetDisaster } from './mcp-server/tools/definitions/fema-get-disaster.tool.js';
+import { femaGetHousingAssistance } from './mcp-server/tools/definitions/fema-get-housing-assistance.tool.js';
+import { femaGetPublicAssistance } from './mcp-server/tools/definitions/fema-get-public-assistance.tool.js';
+import { femaQueryDataset } from './mcp-server/tools/definitions/fema-query-dataset.tool.js';
+import { femaSearchDisasters } from './mcp-server/tools/definitions/fema-search-disasters.tool.js';
+import { femaSearchNfip } from './mcp-server/tools/definitions/fema-search-nfip.tool.js';
+import { setCanvas } from './services/canvas/canvas-accessor.js';
+import { initOpenFemaService } from './services/openfema/openfema-service.js';
+await createApp({
+    tools: [
+        femaSearchDisasters,
+        femaGetDisaster,
+        femaGetPublicAssistance,
+        femaGetHousingAssistance,
+        femaSearchNfip,
+        femaDataframeQuery,
+        femaDataframeDescribe,
+        femaQueryDataset,
+    ],
+    resources: [femaDisasterResource],
+    prompts: [],
+    setup(core) {
+        initOpenFemaService(core.config, core.storage);
+        setCanvas(core.canvas);
+    },
+    instructions: 'FEMA disaster and flood data server. Primary entry points:\n' +
+        '- fema_search_disasters: find federal disaster declarations by state/type/date\n' +
+        '- fema_get_disaster: all designated areas for a specific disaster number\n' +
+        '- fema_get_public_assistance: PA funded projects (where recovery money went)\n' +
+        '- fema_get_housing_assistance: IA housing grants by county/ZIP\n' +
+        '- fema_search_nfip: NFIP flood insurance claims (requires state filter; stages to canvas for SQL)\n' +
+        '- fema_query_dataset: generic OData access to any OpenFEMA v2 dataset\n' +
+        '- fema://disaster/{number}: read-once disaster summary resource\n' +
+        'Disaster number is the join key across all PA and IA tools.',
+});
+//# sourceMappingURL=index.js.map

package/dist/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":";AACA;;;GAGG;AAEH,OAAO,EAAE,SAAS,EAAE,MAAM,wBAAwB,CAAC;AACnD,OAAO,EAAE,oBAAoB,EAAE,MAAM,8DAA8D,CAAC;AACpG,OAAO,EAAE,qBAAqB,EAAE,MAAM,gEAAgE,CAAC;AACvG,OAAO,EAAE,kBAAkB,EAAE,MAAM,6DAA6D,CAAC;AACjG,OAAO,EAAE,eAAe,EAAE,MAAM,0DAA0D,CAAC;AAC3F,OAAO,EAAE,wBAAwB,EAAE,MAAM,oEAAoE,CAAC;AAC9G,OAAO,EAAE,uBAAuB,EAAE,MAAM,mEAAmE,CAAC;AAC5G,OAAO,EAAE,gBAAgB,EAAE,MAAM,2DAA2D,CAAC;AAC7F,OAAO,EAAE,mBAAmB,EAAE,MAAM,8DAA8D,CAAC;AACnG,OAAO,EAAE,cAAc,EAAE,MAAM,yDAAyD,CAAC;AACzF,OAAO,EAAE,SAAS,EAAE,MAAM,sCAAsC,CAAC;AACjE,OAAO,EAAE,mBAAmB,EAAE,MAAM,yCAAyC,CAAC;AAE9E,MAAM,SAAS,CAAC;IACd,KAAK,EAAE;QACL,mBAAmB;QACnB,eAAe;QACf,uBAAuB;QACvB,wBAAwB;QACxB,cAAc;QACd,kBAAkB;QAClB,qBAAqB;QACrB,gBAAgB;KACjB;IACD,SAAS,EAAE,CAAC,oBAAoB,CAAC;IACjC,OAAO,EAAE,EAAE;IACX,KAAK,CAAC,IAAI;QACR,mBAAmB,CAAC,IAAI,CAAC,MAAM,EAAE,IAAI,CAAC,OAAO,CAAC,CAAC;QAC/C,SAAS,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;IACzB,CAAC;IACD,YAAY,EACV,8DAA8D;QAC9D,kFAAkF;QAClF,4EAA4E;QAC5E,gFAAgF;QAChF,kEAAkE;QAClE,qGAAqG;QACrG,yEAAyE;QACzE,mEAAmE;QACnE,6DAA6D;CAChE,CAAC,CAAC"}

package/dist/mcp-server/resources/definitions/fema-disaster.resource.d.ts

@@ -0,0 +1,9 @@
+/**
+ * @fileoverview Resource: fema://disaster/{disasterNumber} — disaster declaration summary.
+ * @module mcp-server/resources/definitions/fema-disaster
+ */
+import { z } from '@cyanheads/mcp-ts-core';
+export declare const femaDisasterResource: import("@cyanheads/mcp-ts-core").ResourceDefinition<z.ZodObject<{
+    disasterNumber: z.ZodString;
+}, z.core.$strip>, undefined, undefined>;
+//# sourceMappingURL=fema-disaster.resource.d.ts.map

package/dist/mcp-server/resources/definitions/fema-disaster.resource.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"fema-disaster.resource.d.ts","sourceRoot":"","sources":["../../../../src/mcp-server/resources/definitions/fema-disaster.resource.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,OAAO,EAAY,CAAC,EAAE,MAAM,wBAAwB,CAAC;AAIrD,eAAO,MAAM,oBAAoB;;wCAgE/B,CAAC"}