MCP Prompts Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level for the server | info |
| PROMPTS_DIR | No | Directory to store prompts when using file storage | ./prompts |
| SERVER_NAME | No | Name of the MCP server | mcp-prompts |
| STORAGE_TYPE | No | The type of storage to use | file |
| SERVER_VERSION | No | Version of the MCP server | 1.0.0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_promptB | Add a new prompt. Set isTemplate and variables to make it a template that apply_template can fill. |
| get_promptC | Get a prompt by its ID. |
| list_promptsA | List prompts, optionally filtered by tags (any match) or a search term. |
| update_promptC | Update fields of an existing prompt; its version is incremented. |
| delete_promptC | Delete a prompt by its ID. |
| apply_templateB | Fill a template prompt's {{variables}} and return the resulting text. |
| get_statsB | Counts of prompts and templates, with the tags and categories in use. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct action on the prompt resource: add, get, list, update, delete, apply_template, and get_stats. The only potential confusion is between get_prompt and apply_template, but the descriptions make the distinction between retrieving raw vs. rendered text clear.
All tools follow a consistent verb_noun pattern (delete_prompt, add_prompt, get_prompt, list_prompts, update_prompt, apply_template, get_stats), with only a trivial pluralization difference in list_prompts. Conventions are predictable and readable.
Seven tools is a well-scoped set for a prompt management server, covering exactly the CRUD lifecycle plus templating and stats. Every tool earns its place with no redundancy.
Full CRUD is present (add, get, list, update, delete), plus templating via apply_template and aggregate info via get_stats, and search/filter is folded into list_prompts. This covers the domain's lifecycle with no obvious dead ends.