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