MCP Is RSS for AI: More Use Cases for Model Context Protocol - I like this: “I’m inclined to think of MCP as RSS for AI.” // Once prompts are used as intended - to be user initiated activity in the UI, we’ll see if things evolve. Think of an MCP prompt as adding a new button, or command to the UI…sort of. Most MCP things now are “tools” reading data or writing data, the AI puts some text into the tool, some text comes out. But, the tool user is the AI, not the human. Of course, the human can tell the AI to use it. We have demos of configuring Cloud Foundry this way. An MCP prompt’s user it meant to be a human, directly typing or clicking something. This might be too nuanced of a distinction and turn out not to be useful. The MCP clients, like Claude need better implementations of it (it should start with auto-complete slash commands, the example in the MCP spec!). // Another point: the MCP spec is making a big semantic gamble on the distinction between tools, prompts, and resources. Looking at all the tools so far, the others aren’t needed to get the functionality you want, but they do seem like a cleaner design. The people writing the MCP Servers will determine if those extra semantics (prompts and resources) are useful, needed.