city_overview — InfraNode MCP Prompt

city_overview is one of 4 prompts on the InfraNode MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke city_overview from your client

• Claude Code InfraNode Prompt/city_overview run in your project directory
• Claude Desktop InfraNode Prompt/city_overview ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor InfraNode Prompt/city_overview ~/.cursor/mcp.json
• VS Code InfraNode Prompt/city_overview .vscode/mcp.json
• Zed InfraNode Prompt/city_overview ~/.config/zed/settings.json
• Windsurf InfraNode Prompt/city_overview ~/.codeium/windsurf/mcp_config.json
• Cline InfraNode Prompt/city_overview ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI InfraNode Prompt/city_overview ~/.gemini/settings.json
• Grok InfraNode Prompt/city_overview .mcp.json (in your project root)
• ChatGPT InfraNode Prompt/city_overview Settings → Connectors → Advanced → Developer mode
• Claude.ai InfraNode Prompt/city_overview Settings → Connectors → Add custom connector
• LangChain InfraNode Prompt/city_overview pip install langchain-mcp-adapters

Other prompts on this server

• city_briefing
• compare_air_quality
• commute_check

InfraNode also offers 3 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, 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 prompt's arguments.