feasibility-on-address — Bucky MCP Prompt

feasibility-on-address is one of 4 prompts on the Bucky MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke feasibility-on-address from your client

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

Other prompts on this server

• compare-two-sites
• draft-investor-report
• explain-zoning-result

Bucky also offers 2 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.