Skip to main content
Glama
NianLog

feedback-mcp-server

by NianLog

feedback-mcp-server v2.1.0

一个轻量级的 MCP (Model Context Protocol) 服务器,提供基于浏览器的交互式用户反馈功能,支持完整的 Markdown 渲染和语法高亮。

🌟 功能特性

🚀 核心功能

  • 轻量级浏览器窗口:Chrome/Edge App 模式,无地址栏,资源占用低

  • Markdown 渲染:完整的 Markdown 支持和语法高亮

  • 完全离线运行:代码高亮(Prism)本地化打包,无需网络或 CDN 即可工作

  • 可插拔 UI 后端:默认浏览器富文本;设 FEEDBACK_UI=native 改用系统原生对话框(约 10MB 内存,纯文本)

  • 安全防护:HTML 净化(sanitize-html)防止 XSS、CSP 安全响应头、仅监听 localhost 不暴露公网

  • 智能复制:支持复制为纯文本或 Markdown 格式

  • 多语言界面:中文和英文界面切换

  • 超时控制:可配置超时时间,自动关闭;超时与主动取消语义分离,便于 AI 准确判断

  • 多浏览器支持:Chrome / Edge(App 模式)、Firefox / Safari(普通窗口)

  • 跨平台支持:Windows、macOS 和 Linux

Related MCP server: Enhanced Interactive Feedback MCP Server

📦 安装

方式 1:使用 npx(推荐)

无需安装,直接在 Claude Desktop 中使用:

{
  "mcpServers": {
    "feedback": {
      "command": "npx",
      "args": ["-y", "feedback-mcp-server@latest"],
      "env": {
        "FEEDBACK_TIMEOUT": "300",
        "FEEDBACK_LANGUAGE": "zh",
        "FEEDBACK_THEME": "auto"
      }
    }
  }
}

方式 2:全局安装

npm install -g feedback-mcp-server@latest

配置:

{
  "mcpServers": {
    "feedback": {
      "command": "feedback-mcp-server",
      "env": {
        "FEEDBACK_TIMEOUT": "300",
        "FEEDBACK_LANGUAGE": "zh",
        "FEEDBACK_THEME": "auto"
      }
    }
  }
}

⚙️ 配置

环境变量

环境变量

描述

默认值

FEEDBACK_TIMEOUT

对话框超时(秒),最小 5,非法回退 300

300 (5 min)

FEEDBACK_LANGUAGE

界面语言(仅支持 zh / en,非法值回退 zh

zh

FEEDBACK_UI

UI 后端(选填):browser(富文本)/ native(系统对话框,约10MB)/ auto(优先 native,不可用回退 browser)

browser

FEEDBACK_THEME

主题(选填):auto(跟随系统)/ light / dark;手动切换会记忆覆盖

auto

推荐配置:

{
  "env": {
    "FEEDBACK_TIMEOUT": "300",
    "FEEDBACK_LANGUAGE": "zh",
    "FEEDBACK_THEME": "auto"
  }
}

🎯 使用方式

AI 会自动调用 interactive_feedback 工具,浏览器会打开对话框显示消息内容。

工具参数

  • message (必填): 要显示给用户的消息内容,支持完整的 Markdown 格式

返回值

{
  "submitted": boolean,   // 用户是否提交了响应
  "response": string,     // 用户输入的内容
  "timedOut": boolean     // 是否超时(与主动取消区分)
}

🎨 界面特性

  • Markdown 渲染:完整支持代码高亮、表格、列表等

  • 智能复制:支持复制为纯文本或 Markdown 格式

  • 快捷键Ctrl + Enter 提交,Esc 取消

  • 多语言界面:中文和英文切换

📝 使用示例

简单确认

{
  "message": "是否继续执行删除操作?此操作不可逆。"
}

代码审查结果

{
  "message": "## 代码审查结果\n\n发现以下问题:\n\n1. **类型错误**\n   ```typescript\n   const x: string = 123; // 类型不匹配\n   ```\n\n2. **性能问题**\n   - 未使用缓存\n   - 重复计算\n\n请确认是否修复?"
}

🛠️ 技术栈

  • Node.js + TypeScript

  • MCP SDK:@modelcontextprotocol/sdk

  • Markdown 渲染:marked + Prism.js(本地化,离线可用)

  • 安全净化:sanitize-html(剥离脚本/事件属性,防止 XSS)

📋 系统要求

  • Node.js >= 18.0.0

  • 操作系统:Windows 10+ / macOS 10.15+ / Linux

  • 浏览器:Chrome 或 Edge(推荐,App 模式);Firefox / Safari 亦支持(普通窗口模式)

🐛 故障排除

浏览器没有打开

  • 检查是否安装了 Chrome、Edge、Firefox 或 Safari

Firefox / Safari 下窗口带有地址栏

  • 这两种浏览器不支持 App 模式,会以普通窗口打开,属预期行为

对话框无法提交

  • 检查网络连接和防火墙设置

📋 更新日志

v2.1.0

  • 🐛 修复 browser 提交大文本失败:去除响应长度 10000 字符硬限制(保留 1MB 防滥用),修复提交 5-10KB 日志报 HTTP 400

  • ⏱️ FEEDBACK_TIMEOUT 改秒单位:默认 300s(5 分钟),更直观(原为毫秒)

  • 🗑️ 移除 FEEDBACK_MAX_TOKENS:硬截断输入不利正常使用,改由工具描述引导 AI 控制 message 长度

  • 🎨 主题跟随系统:新增 FEEDBACK_THEMEauto 默认跟随系统 / light / dark),手动切换仍可记忆覆盖

  • 🔧 工具描述精简:减少 token 占用

v2.0.0

  • 🏗️ 可插拔 UI 后端架构:拆分 dialog.tscore/(types、markdown、html-template)+ backends/(browser-backend、native-backend),统一 UIBackend 接口

  • native 后端(省内存):新增 FEEDBACK_UI=native,调用系统原生对话框(Linux zenity / macOS osascript / Windows PowerShell WinForms),内存从约 300MB 降到约 10MB

  • 📝 Markdown 轻量化:native 后端自动将 Markdown 转可读纯文本(不支持富文本渲染)

  • 🔧 配置:新增 FEEDBACK_UI 环境变量(选填,默认 browser,完全向后兼容)

  • 📦 资源:Windows native 脚本 assets/native/win-feedback.ps1 随包分发

v1.2.0

  • 🎨 界面重设计:移除蓝紫渐变与 emoji,采用石墨极简风格(中性灰 + 墨绿强调);暗色主题改为中性石墨深灰

  • 🔒 安全加固:引入 sanitize-html 净化 Markdown 渲染输出,防止 XSS;错误提示改用 textContent;新增 CSP / nosniff / Referrer-Policy 安全响应头

  • 🐛 正确性修复:HTTP 响应统一收口,消除重复写入竞态;超时改为独立端点,修正 timedOut 标志丢失;修复 Firefox 下复制按钮失效;submit/cancel 防重入

  • 🛠️ 可靠性:移除不可靠的 Windows start chrome 路径,统一浏览器探测;修复 path/process 变量遮蔽;MCP 握手版本号改为从 package.json 注入

  • 📦 完全离线:Prism 代码高亮本地化打包(精选常用语言),移除所有 CDN 依赖,无网环境正常工作

  • 🌐 工程化:补全"提交中/处理中"文案 i18n;FEEDBACK_TIMEOUT 下界校验、FEEDBACK_LANGUAGE 收紧为 zh/en;升级依赖修复 7 个安全漏洞

v1.1.2

  • 增强错误处理与重试机制

  • 新增主题切换、窗口位置记忆、快捷键提示

  • 增强浏览器兼容性(Safari/Firefox 支持)


Available Tools

1 tool
interactive_feedbackInteractive Feedback DialogA

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
messageYesText to show the user (Markdown supported). Keep it focused and readable.

Output Schema

ParametersJSON Schema
NameRequiredDescription
responseNoUser response content
timedOutNoWhether the dialog timed out
submittedYesWhether the user submitted a response

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, description carries full burden. It discloses dialog display and wait behavior but doesn't mention blocking or interruption nature, nor auth or side effects. Adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three concise sentences, front-loaded with main action. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Simple tool with one parameter, output schema exists. Description covers purpose, usage, and message guidelines. Return value implied but not stated; minor gap but overall complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline 3. Description adds advice on conciseness but largely reinforces schema description. No new semantic details beyond what schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description explicitly states the tool shows a dialog and waits for user response. The verb 'show' and resource 'dialog with user' are clear, and the purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit use cases: ask questions, confirm decisions, get input when blocked. Lacks explicit exclusions but effectively guides when to use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev2.1.0
    • First observedinteractive_feedback

TDQS

A4.1/5.0
Disambiguation5/5

Only one tool exists, so there is no possibility of ambiguity. The tool's purpose is clearly distinct by default.

Naming Consistency5/5

With a single tool named 'interactive_feedback', there is no inconsistency. The name follows a clear verb_noun pattern that is perfectly consistent.

Tool Count3/5

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.

Completeness5/5

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.

Maintenance

ActivityStale
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • A
    license
    B
    quality
    D
    maintenance
    A modern Model Context Protocol (MCP) server that enables AI assistants to collect interactive user feedback, supporting text and image-based responses.
    3
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    A MCP server that enables AI assistants to collect interactive user feedback with text and image support via a modern GUI.
    235
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    An MCP server that enables LLMs to ask users questions through a web interface with keyboard shortcuts, supporting single/multiple choice and custom input.
    14
    37
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/NianLog/feedback-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server