AI Intervention Agent
When using AI CLIs/IDEs, agents can drift from your intent. This project gives you a simple way to intervene at key moments, review context in a Web UI, and send your latest instructions via interactive_feedback so the agent can continue on track.
Works with Cursor, VS Code, Claude Code, Augment, Windsurf, Trae, and more.
Quick start
Option 1: Using uvx (Recommended)
Configure your AI tool to launch the MCP server directly via uvx (this automatically installs and runs the latest version):
{
"mcpServers": {
"ai-intervention-agent": {
"command": "uvx",
"args": ["ai-intervention-agent"],
"timeout": 600,
"autoApprove": ["interactive_feedback"]
}
}
}Option 2: Using pip
First, install the package manually (please remember to manually
pip install --upgrade ai-intervention-agentperiodically to get updates):
pip install ai-intervention-agentConfigure your AI tool to launch the installed MCP server:
{
"mcpServers": {
"ai-intervention-agent": {
"command": "ai-intervention-agent",
"args": [],
"timeout": 600,
"autoApprove": ["interactive_feedback"]
}
}
}interactive_feedback is a long-running tool. Some clients have a hard request timeout, so the Web UI provides a countdown + auto re-submit option to keep sessions alive.
Default:
feedback.frontend_countdown=240secondsRange:
0(disabled) or[10, 3600]seconds. The default 240 stays under the common 300s session hard timeout; raise it intentionally when your client allows longer turns.
(Optional) Customize your config:
On first run,
config.tomlwill be created under your OS user config directory (see docs/configuration.md).Example:
[web_ui]
port = 8080
[feedback]
frontend_countdown = 240
backend_max_wait = 600- Only ask me through the MCP `ai-intervention-agent` tool; do not ask directly in chat or ask for end-of-task confirmation in chat.
- If a tool call fails, keep asking again through `ai-intervention-agent` instead of making assumptions, until the tool call succeeds.
ai-intervention-agent usage details:
- If requirements are unclear, use `ai-intervention-agent` to ask for clarification with predefined options.
- If there are multiple approaches, use `ai-intervention-agent` to ask instead of deciding unilaterally.
- If a plan/strategy needs to change, use `ai-intervention-agent` to ask instead of deciding unilaterally.
- Before finishing a request, always ask for feedback via `ai-intervention-agent`.
- Do not end the conversation/request unless the user explicitly allows it via `ai-intervention-agent`.Related MCP server: ai-intervention-agent
Screenshots
Key features
Real-time intervention: the agent pauses and waits for your input via
interactive_feedbackWeb UI: Markdown, code highlighting, and math rendering
Multi-task: tab switching with independent countdown timers
Auto re-submit: keep sessions alive by auto-submitting at timeout
Notifications: web / sound / system / Bark (loopback URLs auto-suppressed; LAN-IP suggestion surfaced in settings)
SSH / LAN friendly: works behind port forwarding; mDNS publishes a
<host>.localURL when the local network supports itServer self-info resource (
aiia://server/info): live runtime / fastmcp version / middleware chain / task-queue snapshot for cross-tool diagnosticsMCP-spec compliant (2025-11-25 protocol): tool annotations, server identity, and self-contained icons let ChatGPT Desktop / Claude Desktop / Cursor render the server natively without nagging "destructive operation" confirmations
Production-grade middleware:
ErrorHandling+RateLimiting(10 req/s, burst 20) +Timing+Loggingchain, with structuredtask.created/task.completedevents forwarded to the MCP client viactx.info
How it works
Your AI client calls the MCP tool
interactive_feedback.The MCP server ensures the Web UI process is running, then creates a task via HTTP (
POST /api/tasks).The browser (or VS Code Webview) renders the task using a dual-channel transport: SSE (
GET /api/events, withLast-Event-IDresume) for real-time updates, and HTTP polling as a safety net when SSE drops.When you submit feedback, the Web UI completes the task in the task queue.
The MCP server waits via SSE + a low-frequency HTTP poll (
GET /api/tasks/{task_id}), then returns your feedback (text + images) back to the AI client.Optionally, the MCP server triggers notifications (Bark / system / sound / web hints) based on your config. Bark URLs that resolve to loopback addresses are automatically suppressed and the Web UI surfaces a LAN-IP suggestion in the settings panel.
VS Code extension (optional)
Item | Value |
Purpose | Embed the interaction panel into VS Code’s sidebar to avoid switching to a browser. |
Install (Open VSX) | |
Download VSIX (GitHub Release) | |
Setting |
|
Other settings |
|
Configuration
Item | Value |
Docs (English) | |
Docs (简体中文) | |
Default template |
|
OS | User config directory |
Linux |
|
macOS |
|
Windows |
|
Architecture
flowchart TD
subgraph CLIENTS["AI clients"]
AI_CLIENT["AI CLI / IDE<br/>(Cursor, VS Code, Claude Code, ...)"]
end
subgraph MCP_PROC["MCP server process (Python)"]
MCP_SRV["ai-intervention-agent<br/>(server.py / FastMCP)"]
MCP_TOOL["MCP tool<br/>interactive_feedback"]
SVC_MGR["Service manager<br/>(ServiceManager)"]
CFG_MGR_MCP["Config manager<br/>(config_manager.py)"]
NOTIF_MGR["Notification manager<br/>(notification_manager.py)"]
NOTIF_PROVIDERS["Providers<br/>(notification_providers.py)"]
MCP_SRV --> MCP_TOOL
MCP_SRV --> CFG_MGR_MCP
MCP_SRV --> NOTIF_MGR
NOTIF_MGR --> NOTIF_PROVIDERS
end
subgraph WEB_PROC["Web UI process (Python / Flask)"]
WEB_SRV["Web UI service<br/>(web_ui.py / Flask)"]
WEB_CFG_MGR["Config manager<br/>(config_manager.py)"]
HTTP_API["HTTP API<br/>(/api/*)"]
TASK_Q["Task queue<br/>(task_queue.py)"]
WEB_FRONTEND["Browser frontend<br/>(static/js/app.js + multi_task.js)"]
WEB_SRV --> HTTP_API
WEB_SRV --> TASK_Q
WEB_SRV --> WEB_CFG_MGR
WEB_FRONTEND <-->|"SSE /api/events + poll /api/tasks"| HTTP_API
WEB_FRONTEND -->|submit feedback| HTTP_API
end
subgraph VSCODE_PROC["VS Code extension (Node)"]
VSCODE_EXT["Extension host<br/>(packages/vscode/extension.ts)"]
VSCODE_WEBVIEW["Webview frontend<br/>(webview.ts + webview-ui.js<br/>+ webview-notify-core.js + webview-settings-ui.js<br/>+ tri-state-panel.js)"]
VSCODE_EXT --> VSCODE_WEBVIEW
VSCODE_WEBVIEW <-->|"SSE /api/events + poll /api/tasks"| HTTP_API
VSCODE_WEBVIEW -->|submit feedback| HTTP_API
end
subgraph USER_UI["User interfaces"]
BROWSER["Browser<br/>(desktop/mobile)"]
VSCODE["VS Code<br/>(sidebar panel)"]
USER["User"]
end
CFG_FILE["config.toml<br/>(user config directory)"]
AI_CLIENT -->|MCP call| MCP_TOOL
MCP_TOOL -->|start/check Web UI| SVC_MGR
SVC_MGR -->|spawn/monitor| WEB_SRV
USER -->|input / click| WEB_FRONTEND
USER -->|input / click| VSCODE_WEBVIEW
BROWSER -->|load UI| WEB_FRONTEND
VSCODE -->|render UI| VSCODE_WEBVIEW
MCP_TOOL -->|"HTTP POST /api/tasks"| HTTP_API
MCP_TOOL -->|"HTTP GET /api/tasks/{task_id}"| HTTP_API
WEB_CFG_MGR <-->|read/write + watcher| CFG_FILE
CFG_MGR_MCP <-->|read/write + watcher| CFG_FILE
MCP_TOOL -->|trigger notifications| NOTIF_MGR
NOTIF_PROVIDERS -->|system / sound / Bark / web hints| USERThe diagram intentionally shows top-level processes and the most visible modules. Internal helpers — e.g.
state_machine.py(per-task lifecycle),web_ui_mdns.py(LAN service discovery via mDNS),web_ui_security.py(CSRF / origin / token gates),task_queue_singleton.py(single-process queue access),server_feedback.py(theinteractive_feedbackMCP tool body),enhanced_logging.py,protocol.py, etc. — live in the same two processes and are documented per-module underdocs/api/(English) anddocs/api.zh-CN/(中文).
Documentation
Docs index (by audience):
docs/README.md·docs/README.zh-CN.mdScripts index (CI gates / generators / QA):
scripts/README.mdRelease notes:
CHANGELOG.md· VS Code marketplace listing:packages/vscode/CHANGELOG.mdContributing:
CONTRIBUTING.md·CODE_OF_CONDUCT.mdAPI docs index:
docs/api/index.mdAPI docs (简体中文):
docs/api.zh-CN/index.mdMCP tool reference:
docs/mcp_tools.mdMCP 工具说明:
docs/mcp_tools.zh-CN.mdTroubleshooting / FAQ:
docs/troubleshooting.md·docs/troubleshooting.zh-CN.mdi18n contributor guide:
docs/i18n.md
Related projects
Acknowledgements
This project's heritage traces back to Fábio Ferreira (2024) and Pau Oliva (2025), whose original noopstudios/interactive-feedback-mcp and poliva/interactive-feedback-mcp seeded the MCP interactive_feedback tool surface. Their copyright notices are preserved in LICENSE per the MIT license terms. The v1.5.x line is a substantial rewrite — Web UI, VS Code extension, i18n, notification stack, CI/CD pipeline — owned and maintained by @xiadengma (PyPI / Open VSX / VS Code Marketplace publisher).
License
MIT License
Available Tools
1 toolinteractive_feedbackInteractive Feedback (人机协作反馈)A
Ask the human user for interactive feedback through the Web UI.
Use this tool whenever you need a human decision, clarification, confirmation, plan approval, design review, or final sign-off before continuing — especially when the next step has multiple valid approaches, irreversible side effects, or significant trade-offs.
Behavior:
Renders the resolved message (Markdown) and an optional list of options in a Web UI; the user submits text + selected options + optional images.
The call blocks until the user submits, the auto-resubmit countdown expires, or the configured backend timeout is reached.
On success, returns a list of MCP content blocks (text + image) that include the user reply, selected options, and an optional prompt suffix.
On parameter validation failure, raises
ToolErrorso the agent can retry with corrected arguments. On service / task failure, returns a configurable resubmit prompt instructing the agent to call this tool again, instead of silently dropping the request.
Cross-tool compatibility:
summary/promptare accepted as aliases formessageso the samemcp.jsonconfig can target other feedback MCP variants without retraining the agent.optionsis an alias forpredefined_options.project_directory,submit_button_text,timeout,timeout_seconds,feedback_type,priority,language,tags,user_id,task_idare accepted but ignored. They prevent the first-call validation failures observed when an agent reuses arguments shaped for a different feedback MCP server.
Note: this function is not the MCP registration site itself; server.py
wraps it with mcp.tool() to expose it to MCP clients.
R25.2: 函数体首行 import httpx 让下面 except httpx.HTTPError 在运行时
解析符号——本工具被 MCP 客户端首次调用时一次性付 ~55 ms 加载费,而 MCP server
cold-start 路径完全不会进入此函数(server.py 顶层 import 时只是定义而已)。
R44 FastMCP 最佳实践:ctx 关键字参数(FastMCP 自动注入)让本函数可以走
await _emit_ctx_info(ctx, ...) 把 task lifecycle 事件回送给 client
(Cursor / Claude Desktop / ChatGPT Desktop)。client 收到后会在 chat
sidebar 渲染一行进度日志,让人类用户能"看到工具确实在工作、正在等真人
回复",而不是猜"agent 是不是 hung 住了"。ctx 永远 keyword-only 且
默认 None,所以本工具被通过别的入口(pytest 直接调)调用时不会因为缺
ctx 而崩;具体安全语义见 _emit_ctx_info 的 docstring。
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | Accepted for compatibility; ignored by this server. | |
| prompt | No | Compatibility alias for `message`. Ignored when `message` is provided. | |
| loop_id | No | Loop engineering: optional stable identifier shared by every feedback round that belongs to the same goal / outer loop (agent-chosen, e.g. 'auth-refactor-2026-07'). Rounds that carry the same loop_id are grouped in the UI so the human reviewer can replay 'which rounds did this objective go through, and what was decided each time'. Length: clamped to 64 characters server-side. Omit for standalone one-shot questions (default behavior unchanged). | |
| message | No | Question, summary, or proposal to display to the human user. MUST be a non-empty string. Supports CommonMark / GitHub-Flavored Markdown (headings, lists, tables, fenced code blocks, links, inline code). Recommended length: 1-2000 characters; soft cap 1,000,000 characters (~1 MB UTF-8, R166); inputs longer than the cap are truncated with a trailing ellipsis marker. Best practices: (1) state the question clearly in the first line; (2) include the recommended/default answer when proposing options; (3) escape special characters properly in JSON (use \" for quotes, \n for newlines). If omitted, the server falls back to `summary` or `prompt` for cross-tool compatibility. | |
| options | No | Compatibility alias for `predefined_options`. Ignored when `predefined_options` is provided. | |
| summary | No | Compatibility alias for `message` (used by noopstudios/Minidoracat interactive-feedback-mcp variants). Ignored when `message` is provided. | |
| task_id | No | Accepted for compatibility (some agents pre-generate a trace ID and pass it through); this server always auto-generates an internal task ID and ignores the externally supplied value. Useful when the same `mcp.json` config also points at MCP variants that *do* honour an externally supplied task ID. | |
| timeout | No | Accepted for compatibility; this server uses its own configured backend timeout and auto-resubmit countdown. | |
| user_id | No | Accepted for compatibility; ignored by this server. | |
| language | No | Accepted for compatibility; UI language follows the user's saved settings. | |
| priority | No | Accepted for compatibility; ignored by this server. | |
| loop_phase | No | Loop engineering: optional free-form phase tag for this round, e.g. 'investigate' / 'implement' / 'verify' / 'review'. Helps the reviewer see where in the inner loop the agent currently is. Length: clamped to 32 characters server-side. | |
| header_label | No | Optional short chip / tag rendered above the prompt in the task pane to give a one-word context cue (e.g. 'Auth', 'DB', 'Layout', 'CSS', 'i18n'). Length: clamped to 16 characters server-side; single-word recommendation, no spaces if avoidable. Especially useful in multi-task mode where the user juggles 3+ concurrent feedback requests — the chip lets them visually distinguish task domains at a glance. If omitted or empty, no chip is shown (default existing layout). (mining-cycle-3 §2.1 — borrowed from gemini-cli ``ask_user.header`` schema.) | |
| feedback_type | No | Accepted for compatibility; ignored by this server. | |
| loop_objective | No | Loop engineering: optional one-sentence description of the loop's goal (e.g. 'Migrate auth/session.py to PyJWT 2.x with green integration tests'). Pass it on the first round of a loop_id; later rounds may omit it. Shown to the reviewer as loop context above the prompt. Length: clamped to 500 characters server-side. | |
| iteration_label | No | Loop engineering: optional round label such as 'iter-3' or 'attempt-2'. Shown with the loop context so multiple rounds of the same loop are distinguishable at a glance. Length: clamped to 32 characters server-side. | |
| timeout_seconds | No | Compatibility alias for `timeout` (used by some MCP clients that explicitly suffix the unit). Both fields are accepted for compatibility — this server ignores them and uses its own configured backend timeout / auto-resubmit countdown. When both are provided, this server logs a debug line and discards both, since neither overrides server config. | |
| success_criteria | No | Loop engineering: optional verifiable completion criteria the human should judge the evidence against (e.g. 'pytest all green + no new ruff warnings + docs regenerated'). Rendered alongside the loop context so the verdict is made against an explicit baseline. Length: clamped to 500 characters server-side. | |
| project_directory | No | Accepted for compatibility with other feedback MCP variants; this server ignores it (project context is taken from the running Web UI / config). | |
| predefined_options | No | Optional list of predefined choices the user can pick from (rendered as multi-select checkboxes alongside a free-text reply). Two canonical input shapes (v1.6.0+ — the legacy parallel-array shape `predefined_options_defaults` was removed in R167; use the dict form below to mark recommended options): (a) **RECOMMENDED** list[dict] of shape {"label": str, "default": bool} — mark the recommended option with `default: true` so the UI shows a pre-checked checkbox (field aliases accepted: "label"/"text"/"value", "default"/"selected"/"checked"); (b) list[str] — simple labels, all initially unchecked (use this when no recommendation is needed). Non-string and non-{label,...} items are silently dropped. Each option max length: 10000 characters (longer items truncated). Tips: (1) keep options short, action-oriented and mutually distinguishable; (2) PREFER the dict form for ANY recommended option — `{"label": "Apply", "default": true}`. The UI renders real pre-checked checkboxes, so do NOT use text-prefix hacks (adding marker words to the label) for marking recommendations; (3) the user may also ignore options and reply with free text. If omitted, the server falls back to `options` for cross-tool compatibility. | |
| submit_button_text | No | Accepted for compatibility; this server uses its own UI labels. | |
| feedback_placeholder | No | Optional textarea placeholder hint shown to the user when waiting for free-text feedback. Per-task override of the global ``page.feedbackPlaceholder`` i18n string. Examples: 'Paste the error stack trace', 'Describe the visual glitch', 'Reply 'ok' to approve or 'no' + reason to reject'. Length: clamped to 200 characters server-side (single-line placeholders only; longer text is silently truncated; the response includes ``placeholder_truncated: true`` + ``placeholder_original_length`` + ``placeholder_max_length`` when clamping activates so callers can warn). If omitted or empty, the UI uses its default i18n placeholder. (mining-cycle-3 §2.1 — borrowed from gemini-cli ``ask_user`` schema.) |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description clearly discloses blocking behavior (waits for user submission, auto-resubmit countdown, backend timeout), return contents (user reply, selected options, prompt suffix), and failure behavior (raises ToolError on validation failure, returns a resubmit prompt on service failure). It also documents ignored compatibility arguments and aliases. The annotations (readOnlyHint: false, destructiveHint: false) are not contradicted.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The opening is concise and front-loaded, but the description becomes extremely long and includes internal engineering references (R25.2, R44, mining-cycle-3 §2.1), implementation details about server.py import costs, ctx injection mechanics, and version-removal notes. Many of these details are not actionable for an agent selecting or invoking the tool and dilute the useful guidance.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (22 parameters, output schema present, many compatibility aliases), the description is complete: it covers blocking semantics, timeout behavior, failure handling, all alias/ignored parameters, loop-tracking fields, predefined option shapes, and result contents. No important invocation behavior is left unexplained.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Though the input schema already covers 100% of parameters, the description adds substantial semantics: alias precedence (summary/prompt for message, options for predefined_options), ignored compatibility fields, loop_id/loop_phase grouping semantics, predefined_options canonical shapes, and clamping behavior. This goes well beyond the schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a clear verb-resource pair: 'Ask the human user for interactive feedback through the Web UI.' It immediately states the tool's purpose and the kinds of situations it is for (human decision, clarification, confirmation, plan approval, design review, final sign-off).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives explicit when-to-use guidance: 'Use this tool whenever you need a human decision, clarification, confirmation, plan approval, design review, or final sign-off before continuing' and highlights trigger conditions like multiple valid approaches, irreversible side effects, or significant trade-offs. It also clarifies what it is not (the MCP registration site).
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.
1 tool update
v1.8.12- Changed
interactive_feedback1 field changed- removed
Input schema / properties / question_typeRemoved value: -{ - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "default": null, - "description": "Optional UI mode hint: when ``'yesno'``, the frontend hides the free-text textarea and renders a single-row Yes/No button pair. User's click submits the literal string 'yes' or 'no' as the feedback result — saves typing + Submit-button click for binary decisions (approve/reject, proceed/abort, etc.). Allowed values: ``'yesno'`` (current) or ``None`` (default: keep textarea + optional ``predefined_options`` checkboxes). Unknown values silently treated as None (forward-compat for future types like ``'choice'`` / ``'rating'`` once the frontend supports them). (mining-cycle-3 §2.1 — borrowed from gemini-cli ``ask_user`` schema.)" -}
1 tool update
v1.8.3- Changed
interactive_feedback5 fields changed- added
Input schema / properties / iteration_labelAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Loop engineering: optional round label such as 'iter-3' or 'attempt-2'. Shown with the loop context so multiple rounds of the same loop are distinguishable at a glance. Length: clamped to 32 characters server-side." +} - added
Input schema / properties / loop_idAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Loop engineering: optional stable identifier shared by every feedback round that belongs to the same goal / outer loop (agent-chosen, e.g. 'auth-refactor-2026-07'). Rounds that carry the same loop_id are grouped in the UI so the human reviewer can replay 'which rounds did this objective go through, and what was decided each time'. Length: clamped to 64 characters server-side. Omit for standalone one-shot questions (default behavior unchanged)." +} - added
Input schema / properties / loop_objectiveAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Loop engineering: optional one-sentence description of the loop's goal (e.g. 'Migrate auth/session.py to PyJWT 2.x with green integration tests'). Pass it on the first round of a loop_id; later rounds may omit it. Shown to the reviewer as loop context above the prompt. Length: clamped to 500 characters server-side." +} - added
Input schema / properties / loop_phaseAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Loop engineering: optional free-form phase tag for this round, e.g. 'investigate' / 'implement' / 'verify' / 'review'. Helps the reviewer see where in the inner loop the agent currently is. Length: clamped to 32 characters server-side." +} - added
Input schema / properties / success_criteriaAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Loop engineering: optional verifiable completion criteria the human should judge the evidence against (e.g. 'pytest all green + no new ruff warnings + docs regenerated'). Rendered alongside the loop context so the verdict is made against an explicit baseline. Length: clamped to 500 characters server-side." +}
1 tool update
v1.7.13- Changed
interactive_feedback3 fields changed- added
Input schema / properties / feedback_placeholderAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Optional textarea placeholder hint shown to the user when waiting for free-text feedback. Per-task override of the global ``page.feedbackPlaceholder`` i18n string. Examples: 'Paste the error stack trace', 'Describe the visual glitch', 'Reply 'ok' to approve or 'no' + reason to reject'. Length: clamped to 200 characters server-side (single-line placeholders only; longer text is silently truncated; the response includes ``placeholder_truncated: true`` + ``placeholder_original_length`` + ``placeholder_max_length`` when clamping activates so callers can warn). If omitted or empty, the UI uses its default i18n placeholder. (mining-cycle-3 §2.1 — borrowed from gemini-cli ``ask_user`` schema.)" +} - added
Input schema / properties / header_labelAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Optional short chip / tag rendered above the prompt in the task pane to give a one-word context cue (e.g. 'Auth', 'DB', 'Layout', 'CSS', 'i18n'). Length: clamped to 16 characters server-side; single-word recommendation, no spaces if avoidable. Especially useful in multi-task mode where the user juggles 3+ concurrent feedback requests — the chip lets them visually distinguish task domains at a glance. If omitted or empty, no chip is shown (default existing layout). (mining-cycle-3 §2.1 — borrowed from gemini-cli ``ask_user.header`` schema.)" +} - added
Input schema / properties / question_typeAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Optional UI mode hint: when ``'yesno'``, the frontend hides the free-text textarea and renders a single-row Yes/No button pair. User's click submits the literal string 'yes' or 'no' as the feedback result — saves typing + Submit-button click for binary decisions (approve/reject, proceed/abort, etc.). Allowed values: ``'yesno'`` (current) or ``None`` (default: keep textarea + optional ``predefined_options`` checkboxes). Unknown values silently treated as None (forward-compat for future types like ``'choice'`` / ``'rating'`` once the frontend supports them). (mining-cycle-3 §2.1 — borrowed from gemini-cli ``ask_user`` schema.)" +}
1 tool update
v1.6.3- Added
interactive_feedback
1 tool update
v1.6.2- Removed
interactive_feedback
1 tool update
v1.6.0- Changed
interactive_feedback20 fields changed- added
Input schema / properties / feedback_typeAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Accepted for compatibility; ignored by this server." +} - added
Input schema / properties / languageAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Accepted for compatibility; UI language follows the user's saved settings." +} - added
Input schema / properties / message / anyOfAdded value: +[ + { + "type": "string" + }, + { + "type": "null" + } +] - added
Input schema / properties / message / defaultAdded value: +null - changed
Input schema / properties / message / descriptionPrevious value: -"向用户展示的具体问题/提示(支持 Markdown)"New value: +"Question, summary, or proposal to display to the human user. MUST be a non-empty string. Supports CommonMark / GitHub-Flavored Markdown (headings, lists, tables, fenced code blocks, links, inline code). Recommended length: 1-2000 characters; hard limit 10000 (longer input is truncated). Best practices: (1) state the question clearly in the first line; (2) include the recommended/default answer when proposing options; (3) escape special characters properly in JSON (use \\\" for quotes, \\n for newlines). If omitted, the server falls back to `summary` or `prompt` for cross-tool compatibility." - removed
Input schema / properties / message / typeRemoved value: -"string" - added
Input schema / properties / optionsAdded value: +{ + "anyOf": [ + { + "items": {}, + "type": "array" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Compatibility alias for `predefined_options`. Ignored when `predefined_options` is provided." +} - changed
Input schema / properties / predefined_options / descriptionPrevious value: -"可选的预定义选项列表,供用户单选/多选"New value: +"Optional list of predefined choices the user can pick from (rendered as multi-select checkboxes alongside a free-text reply). Three input shapes are accepted (v1.5.20+): (a) list[str] — simple labels, all initially unchecked; (b) list[dict] of shape {\"label\": str, \"default\": bool} — let the recommended option start pre-checked without any extra param (aliases: \"label\"/\"text\"/\"value\", \"default\"/\"selected\"/\"checked\"); (c) list[str] paired with the sibling param `predefined_options_defaults` (parallel boolean array). Non-string and non-{label,...} items are silently dropped. Each option max length: 500 characters (longer items are truncated). Tips: (1) keep options short, action-oriented and mutually distinguishable; (2) prefer the dict form `{\"label\": \"Apply\", \"default\": true}` to mark the recommended/default answer — the UI now renders real pre-checked checkboxes, so do NOT rely on text-prefix hacks for marking recommended options; (3) the user may also ignore options and reply with free text. If omitted, the server falls back to `options` for cross-tool compatibility." - added
Input schema / properties / predefined_options_defaultsAdded value: +{ + "anyOf": [ + { + "items": {}, + "type": "array" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Optional sibling array (v1.5.20+) for the `list[str]` shape of `predefined_options`: each element decides whether the corresponding checkbox starts pre-checked. Truthy aliases (case-insensitive, trimmed): True / 1 / 1.0 / \"true\" / \"yes\" / \"on\" / \"selected\"; everything else (including None / 0 / lists / dicts) → False. Length is silently truncated when longer than `predefined_options` and padded with False when shorter. Ignored when `predefined_options` already uses the {\"label\", \"default\"} dict form (which takes precedence)." +} - added
Input schema / properties / priorityAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Accepted for compatibility; ignored by this server." +} - added
Input schema / properties / project_directoryAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Accepted for compatibility with other feedback MCP variants; this server ignores it (project context is taken from the running Web UI / config)." +} - added
Input schema / properties / promptAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Compatibility alias for `message`. Ignored when `message` is provided." +} - added
Input schema / properties / submit_button_textAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Accepted for compatibility; this server uses its own UI labels." +} - added
Input schema / properties / summaryAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Compatibility alias for `message` (used by noopstudios/Minidoracat interactive-feedback-mcp variants). Ignored when `message` is provided." +} - added
Input schema / properties / tagsAdded value: +{ + "anyOf": [ + { + "items": {}, + "type": "array" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Accepted for compatibility; ignored by this server." +} - added
Input schema / properties / task_idAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Accepted for compatibility (some agents pre-generate a trace ID and pass it through); this server always auto-generates an internal task ID and ignores the externally supplied value. Useful when the same `mcp.json` config also points at MCP variants that *do* honour an externally supplied task ID." +} - added
Input schema / properties / timeoutAdded value: +{ + "anyOf": [ + { + "type": "integer" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Accepted for compatibility; this server uses its own configured backend timeout and auto-resubmit countdown." +} - added
Input schema / properties / timeout_secondsAdded value: +{ + "anyOf": [ + { + "type": "integer" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Compatibility alias for `timeout` (used by some MCP clients that explicitly suffix the unit). Both fields are accepted for compatibility — this server ignores them and uses its own configured backend timeout / auto-resubmit countdown. When both are provided, this server logs a debug line and discards both, since neither overrides server config." +} - added
Input schema / properties / user_idAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Accepted for compatibility; ignored by this server." +} - removed
Input schema / requiredRemoved value: -[ - "message" -]
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap. The tool's purpose of collecting interactive human feedback is clearly defined and easily distinguishable from any potential future tools.
The single tool name 'interactive_feedback' follows a clear, descriptive snake_case convention. Consistency is trivially maintained since there are no other tools to compare, and the name accurately reflects its function.
A single tool feels thin for an 'AI Intervention Agent', even if the scope is narrow. It is borderline on the lower end of the tool-count spectrum, but the tool is non-trivial and well-defined, so it is not severely inappropriate.
For its stated purpose of collecting interactive feedback from a human user, the tool covers the full lifecycle: requesting input, providing options, handling timeouts/retries, and returning results. There are no obvious missing operations within this narrow domain.
Maintenance
Related MCP Connectors
Human-in-the-loop review and approval for AI agents. Audit trail, approval policies, native MCP.
Human-in-the-loop for AI agents over MCP: durable approvals with a hosted review page & audit trail
Zero-secret MCP gateway for AI agents: risk-scored, audited calls with human-in-the-loop approval.
Live data grids for AI agents. Push structured data; humans review, agents read back via MCP.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceHuman-in-the-Loop authorization gateway for AI Agents. Securely pause MCP workflows and route high-risk actions to human approvers via Slack or Email.64 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables real-time user intervention for MCP agents via a Web UI and interactive_feedback tool, allowing users to review context and send instructions when agents drift from intent.MIT

Datashift MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceEnables AI agents to submit tasks for human or AI review and receive decisions via MCP tools, adding human review checkpoints to workflows.MIT- AlicenseAqualityDmaintenanceRuntime quality validation for AI agent outputs. Detect hallucinations, enforce scope compliance, and score output quality — all via MCP.627 npmMIT