Browser Feedback MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FEEDBACK_PORT | No | Port for HTTP/WebSocket server | 9877 |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| install_widgetA | Deprecated — prefer the browser extension (setup_extension). Automatically install the feedback widget into a web application by injecting the script tag into an HTML file. Supports auto-detection of common entry points (index.html, etc.) or a specific file path. |
| uninstall_widgetA | Deprecated — prefer the browser extension (setup_extension). Remove the feedback widget from a web application by removing the injected script tag. |
| get_widget_snippetA | Deprecated — prefer the browser extension (setup_extension). Get the HTML snippet to add to a web app for browser feedback collection. |
| wait_for_browser_feedbackA | Wait for feedback from the browser widget. Blocks until user submits feedback. Returns screenshot, element info, console logs, and description. IMPORTANT: After receiving feedback, DO NOT call this tool again. Instead, analyze the feedback and take action (fix bugs, make changes, etc.). Only call this tool again if the user explicitly asks for more feedback or you need to verify your fix worked. |
| get_pending_feedbackA | Get all pending feedback that has been submitted. Use this to collect multiple annotations at once - user can submit several feedback items, then you call this to get them all. Returns an array of feedback items. After receiving, analyze ALL items and take action on each. |
| preview_pending_feedbackA | Preview all pending feedback without consuming it. Use this to see what feedback has been submitted without clearing the queue. Returns summaries of pending items (id, timestamp, description, selector). The browser widget also shows this information. |
| delete_pending_feedbackA | Delete a specific pending feedback item by ID. Use this when a user wants to remove feedback they submitted by mistake or that is no longer relevant. |
| wait_for_multiple_feedbackA | Wait for the user to submit multiple feedback items. Shows a prompt in the browser telling user to submit all their annotations, then click 'Done'. Returns array of all feedback. Use this when user wants to report multiple issues at once. |
| get_connection_statusB | Check if any browser clients are connected to the feedback server. |
| request_annotationA | Send a prompt to connected browsers asking user to annotate something specific. After calling this, use wait_for_browser_feedback ONCE to receive the response. Do not loop - act on the feedback received. |
| open_in_browserB | Open the project in the default browser. Automatically detects the project URL from common configuration files (.env, docker-compose.yml, etc.) or accepts an explicit URL. Can also just return the detected URL without opening. |
| setup_extensionA | Help the user install the browser extension for widget injection without modifying project files. Opens the extension directory and provides step-by-step instructions for Chrome and Firefox. |
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 12 tools
The retrieval tools overlap heavily: wait_for_browser_feedback, wait_for_multiple_feedback, get_pending_feedback, and preview_pending_feedback all return feedback items and differ mainly in blocking/consuming semantics. Descriptions do clarify the distinctions, but an agent could easily pick the wrong one. The three deprecated widget tools also overlap with each other and with setup_extension.
All tools use consistent snake_case verb_noun form (install_widget, get_pending_feedback, wait_for_multiple_feedback, etc.). The pattern is predictable and readable throughout, with no mixed conventions.
12 tools is reasonable for this scope, though three are marked deprecated, leaving effectively nine active tools. The count is slightly inflated by the legacy widget group that is being phased out in favor of the extension.
The domain (browser feedback collection) is well covered: installation/setup, connection status, multiple feedback retrieval modes, deletion, annotation requests, and browser opening. Coverage is strong, with only minor redundancy from the deprecated-but-retained widget tools.