result_widget_get_weather — Weather MCP MCP Resource
result_widget_get_weather
is one of 3 resources on the
Weather MCP
MCP server. Connect the server and your client can attach it as context.
by client
How to attach result_widget_get_weather from your client
- Claude Code Weather MCP Resource/result_widget_get_weather run in your project directory
- Claude Desktop Weather MCP Resource/result_widget_get_weather ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Weather MCP Resource/result_widget_get_weather ~/.cursor/mcp.json
- VS Code Weather MCP Resource/result_widget_get_weather .vscode/mcp.json
- Zed Weather MCP Resource/result_widget_get_weather ~/.config/zed/settings.json
- Windsurf Weather MCP Resource/result_widget_get_weather ~/.codeium/windsurf/mcp_config.json
- Cline Weather MCP Resource/result_widget_get_weather ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Weather MCP Resource/result_widget_get_weather ~/.gemini/settings.json
- Grok Weather MCP Resource/result_widget_get_weather .mcp.json (in your project root)
- ChatGPT Weather MCP Resource/result_widget_get_weather Settings → Connectors → Advanced → Developer mode
- Claude.ai Weather MCP Resource/result_widget_get_weather Settings → Connectors → Add custom connector
- LangChain Weather MCP Resource/result_widget_get_weather pip install langchain-mcp-adapters
Other resources on this server
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.