Skip to content

Cursor Pipefire Prompt/why_spam

How to: Cursor Pipefire why_spam

client:Cursor transport:streamable-http prompt:why_spam

Add Pipefire to Cursor

  1. 01

    Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "pipefire": {
      "url": "https://pipefire.ai/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

    why_spam is surfaced in the client's prompt or command menu. Unlike a tool, you invoke it deliberately — Cursor will not call it for you.

  3. 04

    If it does not appear, check that Pipefire is connected and that you are looking at its prompts rather than its tools.

Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs

Same prompt, other clients

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.