Verbinden Sie Claude, Cursor, Windsurf und andere KI-Tools mit über 80 US-Bundesquellen für Umwelt- und Infrastrukturdaten.
GeoTap aggregiert Daten von FEMA, USGS, EPA, NOAA, USDA, USFWS, DOT, Census und weiteren – zugänglich über das MCP (Model Context Protocol).
Web-App: geotapdata.com – kein Programmieren erforderlich; zeichnen Sie auf einer Karte und erkunden Sie Daten visuell.
Node.js (v18 oder neuer) – hier herunterladen
Eine E-Mail-Adresse zur Registrierung für Ihren API-Schlüssel
Gehen Sie auf geotapdata.com/developers und registrieren Sie sich mit Ihrer E-Mail-Adresse, um einen kostenlosen API-Schlüssel zu erhalten.
Ihr API-Schlüssel wird an Ihre E-Mail-Adresse gesendet. Speichern Sie ihn – Sie werden ihn im nächsten Schritt benötigen.
Wählen Sie unten Ihr KI-Tool aus und folgen Sie den Anweisungen. Der MCP-Server wird automatisch über npx installiert – kein manueller Download erforderlich.
Öffnen Sie Claude Desktop
Gehen Sie zu Settings (Zahnrad-Symbol) → Developer → Edit Config
Dies öffnet Ihre claude_desktop_config.json-Datei. Fügen Sie Folgendes hinzu (ersetzen Sie your-api-key-here durch Ihren tatsächlichen Schlüssel):
{
"mcpServers": {
"geotap": {
"command": "npx",
"args": ["-y", "geotap-mcp-server"],
"env": {
"GEOTAP_API_KEY": "your-api-key-here"
}
}
}
}Speicherort der Konfigurationsdatei:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Starten Sie Claude Desktop vollständig neu (beenden und erneut öffnen)
Sie sollten ein Hammer-Symbol (🔨) in der Chat-Eingabe sehen – das bedeutet, dass GeoTap verbunden ist
Führen Sie diesen Befehl aus, um GeoTap zu Ihren Claude Code MCP-Servern hinzuzufügen:
claude mcp add geotap -- npx -y geotap-mcp-serverSetzen Sie dann Ihren API-Schlüssel als Umgebungsvariable. Fügen Sie dies Ihrem Shell-Profil hinzu (~/.zshrc, ~/.bashrc usw.):
export GEOTAP_API_KEY="your-api-key-here"Starten Sie Ihr Terminal neu und starten Sie dann Claude Code. Die GeoTap-Tools sind automatisch verfügbar.
Öffnen Sie Cursor
Gehen Sie zu Settings (⌘ + , auf dem Mac, Strg + , unter Windows) → suchen Sie nach "MCP"
Klicken Sie auf "Edit in settings.json" oder fügen Sie es Ihrer .cursor/mcp.json-Datei hinzu:
{
"mcpServers": {
"geotap": {
"command": "npx",
"args": ["-y", "geotap-mcp-server"],
"env": {
"GEOTAP_API_KEY": "your-api-key-here"
}
}
}
}Starten Sie Cursor neu
Öffnen Sie das KI-Chat-Panel – die GeoTap-Tools erscheinen in der Liste der verfügbaren Tools
Öffnen Sie Windsurf
Gehen Sie zu Settings → MCP Servers (oder bearbeiten Sie direkt ~/.codeium/windsurf/mcp_config.json)
Hinzufügen:
{
"mcpServers": {
"geotap": {
"command": "npx",
"args": ["-y", "geotap-mcp-server"],
"env": {
"GEOTAP_API_KEY": "your-api-key-here"
}
}
}
}Starten Sie Windsurf neu
Für jeden MCP-Client kann der Server direkt ausgeführt werden:
# Install globally
npm install -g geotap-mcp-server
# Run with your API key
GEOTAP_API_KEY=your-api-key-here geotap-mcpDer Server kommuniziert über stdio – verweisen Sie Ihren MCP-Client auf den geotap-mcp-Befehl, wobei die Umgebungsvariable GEOTAP_API_KEY gesetzt ist.
Sobald die Verbindung hergestellt ist, bitten Sie Ihren KI-Assistenten, Daten für einen beliebigen Standort in den USA abzurufen. GeoTap sammelt Daten von allen über 80 Bundesquellen gleichzeitig – geben Sie einfach einen Standort an und fragen Sie dann, was Sie möchten:
"Collect site data for 123 Main St, Austin TX"Sobald die Daten zurückgegeben werden (~60-120 Sekunden), können Sie Folgefragen stellen wie:
"Liegt dieser Standort in einem Überschwemmungsgebiet?"
"Welche Bodentypen gibt es hier und wie hoch ist die Kurvennummer (curve number)?"
"Gibt es in der Nähe Bedenken hinsichtlich einer Kontamination?"
"Wie hoch ist der 100-jährige Niederschlag?"
"Welche Genehmigungen würde ich benötigen, um diesen Standort zu entwickeln?"
"Fassen Sie die wichtigsten Umweltrisiken zusammen"
Problem | Lösung |
Server startet nicht / "GEOTAP_API_KEY is required" | Stellen Sie sicher, dass Ihr API-Schlüssel im |
"npx: command not found" | Installieren Sie Node.js (v18+), das npx enthält |
Tools erscheinen nicht in Claude Desktop | Starten Sie Claude Desktop vollständig neu (beenden + neu öffnen, nicht nur das Fenster schließen) |
Ratenbegrenzungsfehler | Warten Sie einen Moment und versuchen Sie es erneut – Burst-Limits gelten pro Minute |
Related MCP server: PropertyScoop MCP Server
Behörde | Verfügbare Daten |
FEMA | Überschwemmungsgebiete, FIRM-Panels, Hochwasserversicherungs-Karten, Hochwasserabflussgrenzen |
USGS | Höhe (3DEP bei 1m/10m/30m), Geologie, Pegelstände, Grundwasser, Landnutzung (NLCD), StreamStats, National Streamflow Statistics (NSS) |
EPA | Wasserqualität (ATTAINS), Superfund-Standorte, Brownfields, TRI-Toxik-Freisetzungen, USTs, NPDES-Einleitungen |
NOAA | Niederschlag (Atlas 14), IDF-Kurven, Gezeitenstationen, Klimaprojektionen (CMIP6), Wetterstationen, Radar |
USDA/NRCS | Böden (SSURGO), Kurvennummern, hydrologische Bodengruppen, TR-55-Parameter |
USFWS | Feuchtgebiete (NWI), gefährdete Arten, kritischer Lebensraum |
DOT | Brücken, Tunnel, National Bridge Inventory |
Census | Demografie, Grenzen, TIGER-Geodaten |
USACE | Dämme, Deiche, Schifffahrtskanäle |
NHD | Flussläufe, Hydrografie, Wassereinzugsgebiete (HUC-8/10/12) |
Sonstige | Kraftwerke, Minen, Stammesgebiete, Gebäudegrundrisse und mehr |
Jede Antwort enthält eine Quellenangabe – die Bundesbehörde, den Datensatznamen und die Referenz-URL.
Variable | Beschreibung | Erforderlich |
| Ihr API-Schlüssel aus der Registrierung | Ja |
| Benutzerdefinierter API-Endpunkt (fortgeschritten) | Nein |
Regenwasserplanung: Niederschlag (Atlas 14, IDF-Kurven, Hyetographen), Kurvennummern, Konzentrationszeit, Spitzenabfluss
Hochwasseranalyse: Bulletin 17C Hochwasserhäufigkeit, Abflussdauerkurven, regionale Regressionsschätzungen
Abgrenzung von Wassereinzugsgebieten und hydrologische Modellierungseingaben (HEC-HMS, SWMM)
Niedrigwasseranalyse für NPDES-Genehmigungen (7Q10, 7Q2, harmonischer mittlerer Abfluss)
Klimaanpassungsfähige Designstürme für die Widerstandsfähigkeit der Infrastruktur
Umwelt-Due-Diligence bei Immobilientransaktionen
Standort-Machbarkeits- und Entwicklungsbewertung (Skala 0-100)
Screening auf Überschwemmungsgebiete, Feuchtgebiete und Kontamination
Analyse des Genehmigungswegs (Section 404, NPDES, Entwicklung in Überschwemmungsgebieten)
Phase I ESA Desktop-Datenerfassung (EPA-Standorte, Wasserqualität)
Unterstützung bei der Abgrenzung von Feuchtgebieten (NWI + Böden + Hydrologie)
Screening auf Lebensräume gefährdeter Arten (USFWS kritischer Lebensraum)
Bewertung der Beeinträchtigung der Wasserqualität (EPA ATTAINS 303(d)-Liste)
Beiträge sind willkommen! Bitte öffnen Sie ein Issue oder einen Pull Request.
MIT
Web-App: geotapdata.com
Issues: GitHub Issues
npm: geotap-mcp-server
Collect comprehensive environmental data from ALL 80+ federal data sources for a site. Accepts an address, lat/lng coordinates, or a GeoJSON geometry (Point or Polygon). Returns a jobId — poll with get_results until complete (60-120 seconds).
Data returned covers: flood zones, wetlands, soils, geology, contamination sites, water quality, seismic risk, rainfall, infrastructure, ecology, energy, demographics, and much more.
| Name | Required | Description | Default |
|---|---|---|---|
| address | No | US street address (e.g., "123 Main St, Houston TX"). If provided, the site is geocoded automatically. Use this OR lat/lng OR geometry. | |
| lat | No | Latitude of the site (e.g., 34.8441). Use with lng. | |
| lng | No | Longitude of the site (e.g., -82.4010). Use with lat. | |
| geometry | No | GeoJSON geometry (Point or Polygon). For advanced use — most users should use address or lat/lng instead. | |
| bufferAcres | No | Site area in acres when using a point location. Creates a circular buffer. Default: 1 acre. Range: 0.1–640. | |
| searchRadiusMiles | No | How far to search for nearby features (contamination, infrastructure, etc.). Default: 3 miles. Range: 0.5–10. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses async behavior, polling requirement, time estimate, and broad data coverage. It does not mention rate limits or availability constraints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise with two front-loaded paragraphs. Every sentence adds value with no redundancy or waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description covers the return format (jobId), polling mechanism, and data categories. It is fairly complete but could mention error handling or limits.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions for each parameter. The description adds value by summarizing the OR condition among address/lat-lng/geometry and providing default ranges for bufferAcres and searchRadiusMiles.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool collects comprehensive environmental data from 80+ federal sources, accepting address, lat/lng, or geometry. It uses a specific verb-resource combo and distinguishes from siblings like get_results.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explains how to use the tool (provide location input, receive jobId, poll with get_results) and gives typical completion time. It does not explicitly state when not to use it, but the context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get the GeoTap API discovery document. Returns a structured description of all data sources and capabilities.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully disclose behavior. It states the return value but omits side effects, authentication needs, rate limits, or other behavioral traits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no filler. Every sentence adds value: first states the verb and resource, second describes the return content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Without an output schema, the description should fully describe the return value. It says 'structured description' but lacks detail on format or structure, which is a gap for a tool that only outputs data.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With zero parameters, schema coverage is 100% automatically. The description adds no parameter details, but baseline for 0 params is 4, which is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it gets the GeoTap API discovery document, specifying the resource and action. It distinguishes from siblings 'collect_site_data' and 'get_results', which imply different operations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives. It does not mention that it should be used to discover capabilities before performing other actions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Check the status of a data collection job and retrieve results. Poll every 10 seconds until status is "completed".
When complete, present results as a SCANNABLE ENGINEERING DOCUMENT — not a data dump. An engineer needs to answer: (1) What kills the project? (2) What complicates permitting? (3) What's the baseline context?
CRITICAL FLAGS — scan results FIRST and lead with these if present:
FEMA Zone AE/AO/VE or SFHA=true → "Site intersects SFHA — Zone [X]" (CRITICAL)
Floodway present → "Regulatory floodway — no-rise certification required" (CRITICAL)
Superfund count > 0 → "NPL Superfund site within search radius" (CRITICAL)
Wetland count > 10 → "High wetland density — Section 404 permitting likely" (HIGH)
303(d) impaired water → "TMDL required, stricter discharge limits" (HIGH)
Brownfields > 3 → "Phase I ESA recommended" (MODERATE)
Soils with HSG D → "Poorly draining soils — stormwater design impact" (MODERATE)
SECTION ORDER (skip sections with no data):
Site overview — address, coordinates, county, elevation range, land cover, area
FEMA flood zones — table: zone | subtype | SFHA | risk level
Soils — per unit: HSG, drainage class, slope, flood frequency, building/septic limitations
Atlas 14 rainfall — IDF table (rows: 15min, 1hr, 6hr, 12hr, 24hr, 3day; cols: 2yr–100yr). Bold the 24hr row. Include Atlas 14 volume.
Natural hazard risk — NRI ratings by hazard type
Wetlands — count, type breakdown, Section 404 note
Water resources — streams with distances, impaired waters
Contamination — Superfund, brownfields (with distances/status), USTs, NPDES
Seismic & dams — ASCE 7-22 params (SDS, SD1, SDC), nearby dams with hazard rating
Infrastructure — hospitals, fire stations, schools, EMS counts
Demographics — population, median income, vacancy rate
FORMATTING:
Use markdown tables for flood zones, rainfall IDF, soils, brownfields
Cite source agencies (FEMA, NRCS, NOAA Atlas 14, EPA) not just "GeoTap"
Include distances and bearings for nearby features (e.g., "0.8 mi NW")
"_noData: true" means queried but nothing found — mention where relevant ("no Superfund sites" is positive)
End with: "Data sourced from US federal agencies via GeoTap. Verify critical findings before engineering or regulatory decisions."
| Name | Required | Description | Default |
|---|---|---|---|
| jobId | Yes | Job ID returned from collect_site_data |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations present, so description must disclose behavior. It explains polling mechanism and that it returns results, but does not mention failure modes, timeouts, or potential side effects. Still, it provides more than minimal info.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Description is extremely long (500+) with extensive output formatting instructions. While front-loaded with purpose, the verbosity reduces conciseness. Could be more succinct.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema, so description fully specifies output handling: critical flags, section order, formatting, and source attribution. Complete guidance for the agent to present results correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Only one parameter with 100% schema coverage. Schema description is adequate. Description does not add new meaning to the parameter beyond the schema, maintaining baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool checks status and retrieves results from a data collection job, with specific polling advice. It distinguishes from sibling tools like collect_site_data.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives explicit polling guidance (every 10 seconds until completed) and implies use after collect_site_data. Lacks explicit when-not-to-use or alternatives, but context is sufficient.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v3.0.5collect_site_dataget_llms_txtget_resultsScored across 3 tools
Each tool has a distinct purpose: collect_site_data starts data collection, get_results polls job status, and get_llms_txt provides API documentation. No overlap in functionality.
Tool names follow a consistent verb_noun pattern (e.g., collect_site_data, get_results), but get_llms_txt uses an abbreviation (llms) that is slightly less conventional, though still clear.
With only three tools, the server is minimal but appropriate for its focused scope: initiating data collection, polling for results, and accessing API documentation. It could benefit from a cancellation tool, but the count is reasonable.
The tool set covers the core workflow: submit job (collect_site_data), retrieve results (get_results), and discover capabilities (get_llms_txt). Missing options like canceling a job or listing previous jobs are minor omissions for a single-purpose API.
Weather, climate, terrain, fire and flood risk data for any point or polygon on Earth. Free tier.
Federal environmental records near any US location, with dates and provenance; never a safety score.
US site diligence for agents: parcels, power, flood, zoning rules and more, each with its source.
FEMA flood zone, hazard history and demographics for any US address, with sources on every answer.
