Expose MCP Server Prompts as Slash Commands Like Claude Code

[baron]

What feature would you like to see?

The MCP protocol defines MCP server prompts as "a standardized way for servers to expose prompt templates to clients". This is currently well supported by Claude Code and VS Code.

This allows MCP Servers to:

1. Provide well-maintained and up-to-date custom prompts to users
2. Free users from manually checking and refreshing available prompts from MCP providers
3. Live updates to prompts without restarts
4. Better discoverability inside the existing Codex slash popup
5. Structured parameters, fewer “how do I call this?” failures
6. Better security than copy-pasted prompts
7. Respects company policies that do not allow custom prompts
8. Ecosystem parity and portability

This makes it extremely convenient to invoke tools like RepoPrompt by @provencher which involve sophisticated workflows subject to frequent updates.

  /RepoPrompt:rp-build (MCP)           Build with RepoPrompt MCP context_builder → chat → implement. A structured workflow for implementing features using deep codebase context.
                                       (arguments: task)
  /RepoPrompt:rp-investigate (MCP)     Deep bug investigation with RepoPrompt MCP tools. A systematic protocol for investigating issues using context_builder and structured analysis.
                                       (arguments: issue)

Codex already supports MCP servers and a keyboard-first command palette; adding MCP prompt discovery (prompts/list) + execution (prompts/get) as slash commands unlocks centrally managed, updatable, parameterized workflows with less user friction than local prompt files and better governance than copy-paste.

Additional information

No response

[w-winter]

+1