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