find_signal — Zoning Signal MCP Prompt

find_signal is one of 5 prompts on the Zoning Signal MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke find_signal from your client

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

Other prompts on this server

• orient
• analyze_place
• corridor_outlook
• whats_changing

Zoning Signal also offers 4 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.