ea_flood_features — TerraMCP MCP Tool
ea_flood_features
(ea flood features) is one of 33 tools on the
TerraMCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call ea_flood_features from your client
- Claude Code TerraMCP ea_flood_features run in your project directory
- Claude Desktop TerraMCP ea_flood_features ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TerraMCP ea_flood_features ~/.cursor/mcp.json
- VS Code TerraMCP ea_flood_features .vscode/mcp.json
- Zed TerraMCP ea_flood_features ~/.config/zed/settings.json
- Windsurf TerraMCP ea_flood_features ~/.codeium/windsurf/mcp_config.json
- Cline TerraMCP ea_flood_features ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TerraMCP ea_flood_features ~/.gemini/settings.json
- Grok TerraMCP ea_flood_features .mcp.json (in your project root)
- ChatGPT TerraMCP ea_flood_features Settings → Connectors → Advanced → Developer mode
- Claude.ai TerraMCP ea_flood_features Settings → Connectors → Add custom connector
- LangChain TerraMCP ea_flood_features pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http terramcp https://terramcp.earth/mcp
Other tools on this server
- search_sources
- get_source
- list_categories
- top_sources
- get_consultant
- nrw_stations
- nrw_measures
- nrw_readings
- os_names
- ea_groundwater_stations
- ne_designated_sites
- wq_sampling_points
- wq_measurements
- sepa_stations
- sepa_series
- sepa_values
- bgs_collections
- bgs_features
- planning_entities
- flood_zone_at_point
- tide_stations
- tide_readings
- rainfall_stations
- rainfall_latest
- flood_find_stations
- flood_get_readings
- flood_list_warnings
- ea_hydro_series
- nrfa_station_info
- nrfa_get_timeseries
- usgs_daily
- dem_clip
This list was read from the server itself, by connecting to it and calling tools/list on 17 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.