prompte-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| enhance_promptB | Enhance a prompt with the best prompt engineering technique for its intent. |
| list_techniquesB | List all 8 available prompt engineering techniques with acceptance stats. |
| get_statsB | Get session totals and current config snapshot. |
| record_feedbackC | Record whether an enhancement was helpful. |
| get_configA | Read the current ~/.prompte/config.json |
| set_configA | Write a config value to ~/.prompte/config.json |
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 6 tools
Each tool has a distinct purpose with no overlap: enhance_prompt modifies prompts, get_config/set_config handle configuration, get_stats provides usage data, list_techniques enumerates methods, and record_feedback captures user responses. The descriptions clearly differentiate their functions.
Most tools follow a verb_noun pattern (enhance_prompt, get_config, get_stats, set_config, record_feedback), but list_techniques uses a verb_object pattern which is slightly inconsistent. Overall, the naming is readable and predictable with only minor deviation.
With 6 tools, this server is well-scoped for prompt engineering management. Each tool serves a clear role in the workflow: configuration, enhancement, technique listing, feedback, and statistics. The count is neither too sparse nor bloated.
The toolset fully covers the prompt engineering domain: it supports configuration management (get/set), enhancement with techniques (enhance_prompt, list_techniques), feedback collection (record_feedback), and monitoring (get_stats). There are no obvious gaps for core operations.