Promptopia MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROMPTS_DIR | No | Directory to store prompt templates |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_promptC | Adds a new prompt to the system (single content format) |
| update_promptC | Updates an existing prompt (supports both single content and multi-message formats) |
| get_promptB | Gets a prompt by its ID |
| list_promptsB | Lists all available prompts |
| delete_promptC | Deletes a prompt by its ID |
| apply_promptC | Applies variables to a template prompt and returns the result |
| add_multi_message_promptC | Adds a new multi-message prompt with role-based messages |
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 has a clearly distinct purpose: add_multi_message_prompt and add_prompt handle different prompt creation formats, while apply_prompt, delete_prompt, get_prompt, list_prompts, and update_prompt cover specific CRUD operations. There is no overlap or ambiguity between tools.
All tools follow a consistent verb_noun pattern (e.g., add_prompt, delete_prompt, list_prompts) with clear, descriptive names. The naming is uniform throughout, making it easy to understand each tool's function at a glance.
With 7 tools, the server is well-scoped for managing prompts, covering creation (in two formats), retrieval, listing, updating, deletion, and application. This count is appropriate, providing comprehensive functionality without being overwhelming.
The tool set offers complete CRUD coverage for prompts, including both single-content and multi-message formats, along with an apply_prompt tool for variable substitution. There are no obvious gaps, enabling full lifecycle management of prompts.