developer_feasibility — Buildability MCP Prompt
developer_feasibility
is one of 7 prompts on the
Buildability
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke developer_feasibility from your client
- Claude Code Buildability Prompt/developer_feasibility run in your project directory
- Claude Desktop Buildability Prompt/developer_feasibility ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Buildability Prompt/developer_feasibility ~/.cursor/mcp.json
- VS Code Buildability Prompt/developer_feasibility .vscode/mcp.json
- Zed Buildability Prompt/developer_feasibility ~/.config/zed/settings.json
- Windsurf Buildability Prompt/developer_feasibility ~/.codeium/windsurf/mcp_config.json
- Cline Buildability Prompt/developer_feasibility ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Buildability Prompt/developer_feasibility ~/.gemini/settings.json
- Grok Buildability Prompt/developer_feasibility .mcp.json (in your project root)
- ChatGPT Buildability Prompt/developer_feasibility Settings → Connectors → Advanced → Developer mode
- Claude.ai Buildability Prompt/developer_feasibility Settings → Connectors → Add custom connector
- LangChain Buildability Prompt/developer_feasibility pip install langchain-mcp-adapters
Other prompts on this server
Read from the server itself, by connecting to it and calling prompts/list on 14 November 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.