Interactive Feedback MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Node.js environment setting | production |
| OPENAI_API_KEY | No | Your OpenAI API key for Speech-to-Text functionality (optional) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| interactive_feedbackC | Request interactive feedback for a given project directory and summary |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'interactive_feedback' follows a clear verb_noun pattern.
One tool is too few for a server named 'Interactive Feedback MCP', which suggests a broader scope for handling feedback interactions. A single tool feels thin and limited for such a domain.
The tool surface is severely incomplete for an interactive feedback system. It only provides a request function, with no obvious capabilities for managing, updating, or retrieving feedback, creating significant gaps in coverage.