Skip to main content
Glama
noopstudios

Interactive Feedback MCP

by noopstudios

Interactive Feedback MCP

Developed by Fábio Ferreira (@fabiomlferreira). Check out dotcursorrules.com for more AI development enhancements.

Simple MCP Server to enable a human-in-the-loop workflow in AI-assisted development tools like Cursor. This server allows you to run commands, view their output, and provide textual feedback directly to the AI. It is also compatible with Cline and Windsurf.

Interactive Feedback UI - Main View Interactive Feedback UI - Command Section Open

Prompt Engineering

For the best results, add the following to your custom prompt in your AI assistant, you should add it on a rule or directly in the prompt (e.g., Cursor):

Whenever you want to ask a question, always call the MCP interactive_feedback.
Whenever you’re about to complete a user request, call the MCP interactive_feedback instead of simply ending the process. Keep calling MCP until the user’s feedback is empty, then end the request.

This will ensure your AI assistant uses this MCP server to request user feedback before marking the task as completed.

Related MCP server: Spec-driven Development MCP Server

💡 Why Use This?

By guiding the assistant to check in with the user instead of branching out into speculative, high-cost tool calls, this module can drastically reduce the number of premium requests (e.g., OpenAI tool invocations) on platforms like Cursor. In some cases, it helps consolidate what would be up to 25 tool calls into a single, feedback-aware request — saving resources and improving performance.

Configuration

This MCP server uses Qt's QSettings to store configuration on a per-project basis. This includes:

  • The command to run.

  • Whether to execute the command automatically on the next startup for that project (see "Execute automatically on next run" checkbox).

  • The visibility state (shown/hidden) of the command section (this is saved immediately when toggled).

  • Window geometry and state (general UI preferences).

These settings are typically stored in platform-specific locations (e.g., registry on Windows, plist files on macOS, configuration files in ~/.config or ~/.local/share on Linux) under an organization name "FabioFerreira" and application name "InteractiveFeedbackMCP", with a unique group for each project directory.

The "Save Configuration" button in the UI primarily saves the current command typed into the command input field and the state of the "Execute automatically on next run" checkbox for the active project. The visibility of the command section is saved automatically when you toggle it. General window size and position are saved when the application closes.

Installation (Cursor)

Instalation on Cursor

  1. Prerequisites:

    • Python 3.11 or newer.

    • uv (Python package manager). Install it with:

      • Windows: pip install uv

      • Linux/Mac: curl -LsSf https://astral.sh/uv/install.sh | sh

  2. Get the code:

    • Clone this repository: git clone https://github.com/noopstudios/interactive-feedback-mcp.git

    • Or download the source code.

  3. Navigate to the directory:

    • cd path/to/interactive-feedback-mcp

  4. Install dependencies:

    • uv sync (this creates a virtual environment and installs packages)

  5. Run the MCP Server:

    • uv run server.py

  6. Configure in Cursor:

    • Cursor typically allows specifying custom MCP servers in its settings. You'll need to point Cursor to this running server. The exact mechanism might vary, so consult Cursor's documentation for adding custom MCPs.

    • Manual Configuration (e.g., via mcp.json) Remember to change the /Users/fabioferreira/Dev/scripts/interactive-feedback-mcp path to the actual path where you cloned the repository on your system.

      {
        "mcpServers": {
          "interactive-feedback-mcp": {
            "command": "uv",
            "args": [
              "--directory",
              "/Users/fabioferreira/Dev/scripts/interactive-feedback-mcp",
              "run",
              "server.py"
            ],
            "timeout": 600,
            "autoApprove": [
              "interactive_feedback"
            ]
          }
        }
      }
    • You might use a server identifier like interactive-feedback-mcp when configuring it in Cursor.

For Cline / Windsurf

Similar setup principles apply. You would configure the server command (e.g., uv run server.py with the correct --directory argument pointing to the project directory) in the respective tool's MCP settings, using interactive-feedback-mcp as the server identifier.

Development

To run the server in development mode with a web interface for testing:

uv run fastmcp dev server.py

This will open a web interface and allow you to interact with the MCP tools for testing.

Available tools

Here's an example of how the AI assistant would call the interactive_feedback tool:

<use_mcp_tool>
  <server_name>interactive-feedback-mcp</server_name>
  <tool_name>interactive_feedback</tool_name>
  <arguments>
    {
      "project_directory": "/path/to/your/project",
      "summary": "I've implemented the changes you requested and refactored the main module."
    }
  </arguments>
</use_mcp_tool>

Acknowledgements & Contact

If you find this Interactive Feedback MCP useful, the best way to show appreciation is by following Fábio Ferreira on X @fabiomlferreira.

For any questions, suggestions, or if you just want to share how you're using it, feel free to reach out on X!

Also, check out dotcursorrules.com for more resources on enhancing your AI-assisted development workflow.

Available Tools

1 tool
interactive_feedbackB

Request interactive feedback for a given project directory and summary

ParametersJSON Schema
NameRequiredDescriptionDefault
project_directoryYesFull path to the project directory
summaryYesShort, one-line summary of the changes

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are present, so the description alone must disclose behavior. It only says 'request' without explaining whether the tool blocks, returns feedback, or opens a UI, leaving significant ambiguity.

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?

The description is a single, well-front-loaded sentence with no extraneous words. Every part is necessary to convey the core purpose.

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

Completeness2/5

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

Given no output schema and simple parameters, the description should explain the outcome or return value of the request. It does not mention what the agent can expect after invoking the tool, leaving a significant gap.

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% with clear parameter descriptions. The tool description does not add additional meaning beyond the schema, so baseline score of 3 applies.

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?

The description clearly states the verb 'Request' and the resource 'interactive feedback', scoped to a project directory and summary, which is specific and unambiguous.

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

Usage Guidelines3/5

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

No usage guidelines are provided, but there are no sibling tools to differentiate. The description implies usage for requesting feedback but lacks explicit when-to-use or alternative context.

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

TDQS

A3.9/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion between tools. The single tool 'interactive_feedback' serves a unique purpose.

Naming Consistency5/5

The single tool name follows a clear verb_noun pattern ('interactive_feedback'), and there are no other names to compare for inconsistency.

Tool Count5/5

The server is dedicated to interactive feedback, and one tool is perfectly scoped for this narrow purpose. Adding more tools would be unnecessary.

Completeness5/5

For the stated purpose of requesting interactive feedback on a project directory and summary, this single tool fully covers the expected functionality with no obvious gaps.

Maintenance

ActivityInactive
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

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/noopstudios/interactive-feedback-mcp'

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