Who actually supports MCP Resources and Prompts?

The pattern: headless and enterprise orchestration agents converge on Tools as the lowest common denominator: it's the primitive that maps cleanly onto a single request/response turn. Single-developer desktop apps (Claude Desktop, Windsurf/Devin Desktop, Gemini CLI) moved fastest on Resources and Prompts, because a human is sitting there to browse a resource list or invoke a slash-style prompt. GitHub's cloud coding agent is the sharpest data point: its docs explicitly state Resources and Prompts are dropped in the headless agent, even though the editor-side Copilot Chat supports both.