ma_target_screen — gapup mcp MCP Prompt

ma_target_screen is one of 8 prompts on the gapup mcp MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke ma_target_screen from your client

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

Other prompts on this server

• competitive_brief
• kyc_due_diligence
• ai_act_readiness
• country_market_entry
• climate_risk_portfolio
• research_meta_review
• compliance_full_audit

gapup mcp also offers 19 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.