Feedbacks — Claude Code MCP server for visual feedback
Feedbacks brings website annotations, session recordings and team discussion together so a coding agent can inspect a reported issue and its project context.
Open on GitHubWhat Feedbacks does
Feedbacks collects screenshot pins, text replacement suggestions, browser recordings and diagnostics around a reported issue. A team can discuss the evidence, assign work and track progress. Through MCP, an agent can read approved project instructions and reviewer guidance.
Setup starts with a shared team server. Connect the Chrome extension next, then add project context and configure each developer’s personal MCP access. One installation serves one organization. A production deployment needs HTTPS, PostgreSQL and private S3-compatible storage, so plan for those services before choosing that setup. The server and clients use the Apache-2.0 license.
What it helps with
- pin a visual issue to a screenshot
- compare a bug report with a browser session recording
- give an agent approved project guidance
- bundle discussion, media and diagnostics for review
- track assigned feedback and its progress
Example prompts for the agent
- Inspect the Feedbacks screenshot report and suggest a change using the approved project context.
- Compare this issue with its Feedbacks session recording and browser diagnostics.
- Review the discussion and describe how to verify the agreed change.
How to install Feedbacks
Install
The MCP registry has no launch command for it: see the repository README
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Feedbacks
How do I install Feedbacks for Claude Code?
Set up the team server first, then install and connect the Chrome extension. Add project context and configure each developer’s personal MCP access afterward; one deployment serves one organization.
What does Feedbacks do?
It brings visual annotations, session recordings and browser diagnostics into a shared review workflow. An agent can read approved project context through MCP.
What does a production self-hosted setup need?
It requires HTTPS, PostgreSQL and private S3-compatible storage. The team server comes before the browser extension and individual MCP setup.
