Skip to main content
Glama
Dwsy

mcp-feedback-enhanced

by Dwsy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_DEBUGNoSet to 'true' to enable debug mode.false
MCP_LANGUAGENoForce UI language: 'zh-TW', 'zh-CN', or 'en'.auto-detect
MCP_WEB_HOSTNoHost binding for the Web UI. Use '0.0.0.0' for remote access.127.0.0.1
MCP_WEB_PORTNoPort for the Web UI (1024-65535).8765
MCP_DESKTOP_MODENoSet to 'true' to use 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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
interactive_feedbackA

Interactive feedback collection tool for LLM agents.

USAGE RULES:

  1. During any process, task, or conversation, whether asking, replying, or completing phased tasks, you must call this tool to ask for feedback.

  2. Unless receiving termination instructions, all steps must repeatedly call this tool.

  3. Whenever user feedback is received, if the feedback content is not empty, you must call this tool again and adjust behavior based on the feedback content.

  4. Only when the user explicitly indicates "end" or "no more interaction needed" can you stop calling this tool, and the process is considered complete.

  5. You should summarize what have done, and provide project directory through args to let user know what you have done to provide feedback for next step.

CONVERSATION_ID USAGE:

  • IMPORTANT: Always provide a consistent conversation_id for the same chat window or conversation thread

  • If your IDE or client provides a conversation/thread/chat ID, use it as the conversation_id

  • Using the same conversation_id will replace the previous feedback session for that conversation

  • This allows multiple AI conversations to have independent feedback sessions without interfering with each other

  • Examples:

    • Cursor: Use the conversation UUID from the chat window

    • VS Code: Use the conversation/thread identifier

    • If no ID is available: Generate a UUID once per conversation and reuse it

  • If conversation_id is not provided, a new one will be auto-generated (may cause session conflicts in multi-conversation scenarios)

QUICK OPTIONS FEATURE: You can provide quick selection options in the summary using XML format. Users can click checkboxes to select options.

Basic Format:

Format with Attributes (optional title, key, description):

Multiple option groups are supported:

User selections will be returned in the feedback with group numbers like "[1] A. First option".

get_system_infoA

獲取系統環境資訊

Returns: str: JSON 格式的系統資訊

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.8/5.0

Scored across 2 tools

Disambiguation5/5

The two tools are entirely unrelated: interactive_feedback handles user feedback collection while get_system_info retrieves system environment details. No overlap or confusion is possible.

Naming Consistency2/5

The naming patterns differ significantly: 'interactive_feedback' is a compound noun, while 'get_system_info' follows a verb_noun convention. The mix of styles is inconsistent and does not suggest a unified naming scheme.

Tool Count3/5

With only two tools, the server feels thin and under-scoped for a 'feedback-enhanced' purpose. While not as extreme as a single tool, the count is borderline and does not convincingly cover a full feedback workflow.

Completeness2/5

The server name implies a focus on feedback, yet only one tool is directly related, and get_system_info is a disconnected addition. There are no tools for managing or retrieving past feedback sessions, making the surface significantly incomplete.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources