Summary
Prompts as files you can diff, exposed as prompts your client already understands.
Because everything is a JSON file in one directory, your prompt library lives in version control alongside your code and a prompt change is reviewed like anything else. The tools exist for the times hand-editing a file is the wrong shape, and refine_and_add_prompt is the one that does more than bookkeeping.
What it is
A file-based prompt server. Prompts live as JSON in one directory, are exposed through MCP's standard prompt listing and templating, and are managed through tools rather than by hand-editing.
What you get
- add_prompt to register a prompt with an ID, content, description, tags and declared variables
- update_prompt and delete_prompt to change or remove one
- get_prompt_file_content to read back the raw JSON definition of the active prompt
- filter_prompts_by_tags to list the prompts matching every tag you name
- load_default_prompts to copy the bundled defaults into your active directory, skipping any that already exist
- refine_and_add_prompt — optimise a prompt first, then add the refined version to the registry
- Prompts appear through the standard MCP prompt list, with template variables filled in when the client asks for one
Requirements
Node. The prompt directory location is configurable; without it, prompts go into a folder under your home directory. A container image is buildable from the repository if you want the registry isolated.
Setup effort
One command — npx mcp-promptregistry