feedback-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FEEDBACK_TIMEOUT | No | 超时时间（ms） | 300000 |
| FEEDBACK_LANGUAGE | No | 界面语言（zh/en） | zh |
| FEEDBACK_MAX_TOKENS | No | 最大输出token数 |
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 |
|---|---|
| interactive_feedbackA | Show a dialog to the user with your message and wait for their response. Use this to ask questions, confirm decisions, or get input when blocked. Keep the message concise and readable — the user reads it, so summarize rather than dumping raw logs. |
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 1 tool
Only one tool exists, so there is no possibility of ambiguity. The tool's purpose is clearly distinct by default.
With a single tool named 'interactive_feedback', there is no inconsistency. The name follows a clear verb_noun pattern that is perfectly consistent.
A single tool feels thin for most servers, but given the narrow purpose of interactive feedback, it is borderline appropriate. The tool is not trivial, but the server could benefit from additional related tools.
For the stated purpose of showing a dialog and waiting for a response, this single tool covers the core functionality completely. No obvious gaps exist within the defined scope.