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