READ_ONLY, DISABLE_IMPORT, DISABLE_EXPORT and DISABLE_VERSION_ROLLBACK let you hand an agent a prompt library it can read and use but cannot rewrite or export — which is the shape most teams actually want. `get-policy-status` reports which of those flags are live, so the restriction is checkable rather than assumed.
A manager for a folder of prompt files. Each prompt is a plain file; the server adds fuzzy search, categories and tags, variable substitution, favourites, full version history and JSON import/export on top of them.
- `list-prompts`, `get-prompt`, `create-prompt`, `update-prompt` and `delete-prompt` cover the file lifecycle
- `search-prompts` matches filenames and, when you ask it to, content — with a similarity `threshold` and a result `limit` you set per call
- `process-template` fills in `{{variable}}` placeholders, and `list-template-variables` tells you which ones a file expects
- A built-in library of 12 templates across 5 categories, browsed with `list-template-categories` and `search-templates`, rendered by `render-template` or turned into a new file by `create-prompt-from-template`
- Version history is first class: `list-prompt-versions`, `compare-prompt-versions`, `get-prompt-version` and `rollback-prompt`
- `export-prompts` and `import-prompts` move the whole library as JSON, with checksum validation and an automatic backup before import
- `tag-prompt`, `categorize-prompt`, `list-by-category`, `favorite-prompt` and `list-favorites` keep a large library navigable
Node.js v18 or higher and npm. Published as mcp-prompt-manager, version 1.0.0; the documented path is to clone the repository and point node at server.js. PROMPTS_DIR chooses where prompts live, LOG_DIR where logs go. A Dockerfile and compose file are in the repo.
Build from source — clone the repository and build it, then point your client at the binary