add_prompt
Adds a new prompt to the project-specific prompt directory.
LABSCO 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
USE CASES
01
Keeping prompts out of chat history
Register a prompt once with its variables declared, then call it by name from any client.
02
Finding the prompt you wrote months ago
Filter by the tags you gave it rather than scrolling the whole list.
03
Improving a prompt that is nearly right
Run it through optimisation and store the refined version in the registry.
04
Bootstrapping a new machine
Copy the bundled defaults into your prompt directory without overwriting anything you already have.
05
Auditing what a prompt actually says
Read the raw JSON definition, variables and metadata included, rather than the rendered version.
7 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
delete_prompt
Deletes a prompt from the project-specific directory. If a user global default with the same ID exists, it will become active.
filter_prompts_by_tags
Lists active prompts (project-specific or user global defaults) that match all specified tags.
get_prompt_file_content
Retrieves the raw JSON definition of the active prompt (project-specific or user global default).
load_default_prompts
Loads all default prompts from the default_prompts_data directory into the active prompt directory, skipping any that already exist.
refine_and_add_prompt
Optimizes a prompt using Claude Prompt Optimizer techniques, then adds the refined version to the registry.
update_prompt
Updates an existing prompt. Updates are always written to the project-specific directory, creating an override if necessary.
BEFORE YOU INSTALL
What to know first
Tools you get
7 tools when we connected. refine_and_add_prompt is undocumented. Prompts themselves come through prompts/list and prompts/get, and some clients cannot call these management tools.
Requires
- Node.js 18 or higher
- npm (or yarn)
- Docker (optional), only to run the server in a container
Where it runs
Both documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 7 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx mcp-promptregistryMCP Clients
Claude Desktop, Amazon Q
JSON
{
"mcpServers": {
"mcp-promptregistry": {
"command": "npx",
"args": [
"mcp-promptregistry"
],
"env": {
"PROMPT_REGISTRY_PROJECT_DIR": "<YOUR_PROMPT_REGISTRY_PROJECT_DIR>"
}
}
}
}
