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