get_drought_summary — US Drought Monitor MCP Tool Read-only
get_drought_summary
(get drought summary) is one of 3 tools on the
US Drought Monitor
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_drought_summary from your client
- Claude Code US Drought Monitor get_drought_summary run in your project directory
- Claude Desktop US Drought Monitor get_drought_summary ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor US Drought Monitor get_drought_summary ~/.cursor/mcp.json
- VS Code US Drought Monitor get_drought_summary .vscode/mcp.json
- Zed US Drought Monitor get_drought_summary ~/.config/zed/settings.json
- Windsurf US Drought Monitor get_drought_summary ~/.codeium/windsurf/mcp_config.json
- Cline US Drought Monitor get_drought_summary ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI US Drought Monitor get_drought_summary ~/.gemini/settings.json
- Grok US Drought Monitor get_drought_summary .mcp.json (in your project root)
- ChatGPT US Drought Monitor get_drought_summary Settings → Connectors → Advanced → Developer mode
- Claude.ai US Drought Monitor get_drought_summary Settings → Connectors → Add custom connector
- LangChain US Drought Monitor get_drought_summary pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http drought https://mcp.olyport.com/drought/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.