MCP Feedback Enhanced
Related Servers
Alternatives to MCP Feedback Enhanced
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to request human actions or decisions by opening a local browser page for input, allowing the agent to pause and wait for human response.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to request human input through a web interface, allowing them to pause execution and wait for responses via interactive tools like single questions, multiple choice selections, hypothesis challenges, and decision workflows.5 npm2MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI models to ask users questions through a local web interface, supporting batch questions, multi-select, and free text for human-in-the-loop interactions.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to collect interactive user feedback through a modern GUI that supports text input, multiple image uploads (via file selection or clipboard paste), allowing users to provide comprehensive feedback with screenshots and comments.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables human-in-the-loop checkpoints for AI agents, allowing them to pause and wait for human input via a web UI, then seamlessly resume execution.39MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to request human input through a web interface during execution. Supports single questions, multiple choice selections, hypothesis challenges, and decision workflows for human-in-the-loop interactions.5 npmMIT
TDQS
Scored across 2 tools
The two tools serve clearly different purposes: interactive_feedback collects user feedback, while get_system_info retrieves environment details. There is no overlap or ambiguous boundary between them.
Both tools use snake_case, which is consistent. However, get_system_info follows a verb_noun pattern while interactive_feedback is adjective_noun, a minor deviation from a strict convention.
With only two tools, the server is very thin even for a focused feedback utility. It provides one primary action and one auxiliary utility, landing at the borderline of 'too few'.
The surface covers feedback collection (text, images, command validation) and system information. It lacks obvious lifecycle operations such as listing, retrieving, or clearing past feedback, which may limit real-world use.