Prompt Templates

A prompt template is a governed unit of prompt text: name, template_content, an arguments_schema describing the named placeholders it accepts, a version/version_hash pair, and the same risk_tags/compliance_tags/lifecycle_state shape used on tools. It belongs to exactly one MCP server.

Discovery does call prompts/list against an MCP HTTP server and pulls back each prompt's name, description, and argument list — but today that result is only used to compute a hash of the server's prompt set for drift detection and to count how many prompts a server exposes; it is not written into the prompt-template catalog as rows. In practice this means the list on this page reflects only templates registered directly through the create API, not ones a discovery pass has found automatically, even though the page's own empty state currently tells an operator to "run MCP discovery to populate."

The catalog card for a template shows its version, lifecycle state, the first twelve characters of its version hash, when it was last updated, and a 120-character preview of the template body — enough to identify a template without opening it. Search matches on name, description, and version. Risk and compliance tags exist on the underlying record but aren't currently surfaced on the card or used for filtering the way they are for tools.