get_climate_profile — Criora climate risk MCP Tool Read-only
get_climate_profile
(get climate profile) is one of 22 tools on the
Criora climate risk
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_climate_profile from your client
- Claude Code Criora climate risk get_climate_profile run in your project directory
- Claude Desktop Criora climate risk get_climate_profile ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Criora climate risk get_climate_profile ~/.cursor/mcp.json
- VS Code Criora climate risk get_climate_profile .vscode/mcp.json
- Zed Criora climate risk get_climate_profile ~/.config/zed/settings.json
- Windsurf Criora climate risk get_climate_profile ~/.codeium/windsurf/mcp_config.json
- Cline Criora climate risk get_climate_profile ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Criora climate risk get_climate_profile ~/.gemini/settings.json
- Grok Criora climate risk get_climate_profile .mcp.json (in your project root)
- ChatGPT Criora climate risk get_climate_profile Settings → Connectors → Advanced → Developer mode
- Claude.ai Criora climate risk get_climate_profile Settings → Connectors → Add custom connector
- LangChain Criora climate risk get_climate_profile pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http criora https://criora.com/mcpOther tools on this server
- show_risk_map
- get_map_events
- get_map_warnings
- get_map_event
- find_place
- get_forecast
- get_climate_table
- get_climate_twin
- get_place_history
- get_hazards_near
- estimate_financial_impact
- assess_place
- list_hazards
- rank_by_forecast
- get_area_risk
- get_country_profile
- compare_countries
- rank_countries
- get_enso_outlook
- search
- fetch
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.