mcp-feedback-enhanced
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_DEBUG | No | Debug mode | false |
| MCP_LANGUAGE | No | Force UI language (zh-TW, zh-CN, en) | |
| MCP_WEB_HOST | No | Web UI host binding | 127.0.0.1 |
| MCP_WEB_PORT | No | Web UI port | 8765 |
| MCP_DESKTOP_MODE | No | Desktop application mode | false |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| interactive_feedbackA | Interactive feedback collection tool for LLM agents. USAGE RULES:
IMPORTANT: The response may include a [NEW TASK] prefix. This means the user explicitly wants to switch to a completely new task. When you see [NEW TASK], you should: (1) deprioritize any ongoing work, (2) clear your TODO list, and (3) focus entirely on the new request that follows. Args: project_directory: Project directory path for context summary: Summary of AI work completed for user review timeout: Timeout in seconds for waiting user feedback (default: 600 seconds) Returns: list: List containing TextContent and MCPImage objects representing user feedback |
| get_system_infoA | 獲取系統環境資訊 Returns: str: 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 2 tools
The two tools serve entirely different purposes—interactive_feedback collects user feedback during tasks, while get_system_info retrieves system environment information. There is no overlap or ambiguity in their intended use.
Both names are readable and descriptive, but they follow different patterns: interactive_feedback is an adjective-noun compound, while get_system_info uses a verb-noun construction. The inconsistency is noticeable but not chaotic.
Only two tools are provided, which feels thin for a server that claims to be 'feedback-enhanced'. Additionally, get_system_info is unrelated to feedback, making the set seem arbitrary and under-scoped.
The feedback tool covers a single interactive loop, but there are no supporting tools for managing feedback history or controlling the process. get_system_info is unrelated and does not help complete any feedback lifecycle, leaving significant gaps.