Feedbacks MCP server
Commit Nov 13, 2026Provides coding assistants with visual website feedback, session replays, and debugging context through screenshots and annotations.
Also known as Softinator-TechLabs/feedbacks-oss, feedbacks-oss
- Stars
- 37
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.2.3
- Last commit
- Nov 13, 2026
- License
- Apache-2.0
What is Feedbacks MCP?
Feedbacks provides coding assistants with visual website feedback, session replays, and debugging context through screenshots and annotations.
Summary generated from the project's README
About Feedbacks MCP server
Feedbacks provides a way for developers and AI agents to access visual website feedback and debugging context. It allows users to share screenshots, text replacement suggestions, and session recordings that include console, network, and performance timelines. This tool is designed for teams that want to keep discussions, browser diagnostics, and project context in a single location to investigate bugs and verify changes.
Users must first set up a team server, which can be self-hosted using Docker, PostgreSQL, and S3-compatible storage. The workflow involves installing a Chrome extension and connecting it to the server. Once the infrastructure is ready, individual developers can configure their personal MCP setup. The system supports integration with tools like Claude Code and Codex through specific plugins and scoped keys. This setup allows coding assistants to receive approved project instructions and reviewer guidance directly through the MCP, API, or CLI.
What you can do with it
- 1Visual bug investigationAn AI agent can examine screenshot pins and annotations to understand exactly what changed on a webpage.
- 2Debugging with session replaysA developer can provide an AI client with a video recording that includes a timeline of network and console activity.
- 3Providing agentic contextYou can give a coding assistant access to approved project instructions and reviewer responsibilities.
- 4Managing development tasksA team can sync their visual feedback directly with GitHub Issues across different repositories.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 12, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packageNot checked
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledNot checked
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesNot checked
README
View on GitHubFeedbacks
Free, Apache-2.0 visual feedback, session replay and debugging context.
Show the problem with a screenshot, exact text suggestion or video + session recording. Keep the discussion, event timeline, browser diagnostics and approved project context together. Your team and coding agent can investigate the evidence, make the agreed change and record verification. The complete product is free to self-host; you provide the infrastructure and any AI tools you use.
Set up a team server first. The order is: server → install and connect the Chrome extension → project context, optional GitHub App and members → each developer's personal MCP setup. One installation serves your team; the extension does not host a server. Follow the complete setup flow, or the separate DevOps installation guide.
Website · Why Feedbacks · Self-hosting · Extension · Coding assistants & plugins · API & MCP · Roadmap · Contributing
What it does
- Show exactly what changed: screenshot pins, annotation, full-page capture and selected-text replacement suggestions.
- Replay the bug: video or session-only recording with one timeline for activity, console, network and performance. Save and annotate frames.
- Take the evidence: complete thread bundles with discussion, media, recordings, diagnostics and checksums; scoped agent reads and recording exports.
- Give agents context: approved project instructions, reviewer guidance and responsibilities through MCP, API and CLI.
- Move the work forward: assignments, categories, tags, saved views and point progress; optional GitHub Issues across repositories and installations, with multiple configured Apps and one owner-selected App per project.
- Review beyond the extension: scoped guest links, PDF/image review, an optional text widget, surveys/NPS, scheduled public-page QA, native mobile clients and signed webhooks.
- Own the whole service: Apache-2.0 server and clients, PostgreSQL and private S3-compatible storage. One installation serves one organization.
Recording guide · Debug bundles · Text suggestions · More review workflows
Feedbacks is an early 0.x release. Each application deployment serves one organization. Public registration, billing, SSO and shared-database customer tenancy are not implemented. See architecture and deployment boundaries.
Try it with Docker
curl -fsSL https://feedbacks.softinator.ai/install.sh | bash
Open http://localhost:3000 with the generated owner login. PostgreSQL and screenshots persist in Docker volumes; no S3 account or source build is required. The installer requires Docker Compose, Bash, curl and OpenSSL, and preserves existing installation directories. See the quickstart and production guide.
Develop from source
Requirements: Node.js 22 or 24, npm, and Docker Compose for PostgreSQL.
git clone https://github.com/Softinator-TechLabs/feedbacks-oss.git
cd feedbacks-oss
npm ci
cp .env.example .env
docker compose -f compose.dev.yaml up -d --wait
npm run bootstrap
npm run build
npm run dev:server
Before bootstrap, add BOOTSTRAP_EMAIL, BOOTSTRAP_NAME and a unique BOOTSTRAP_PASSWORD to your local .env. Bootstrap creates the first owner once. Remove the bootstrap password afterward. Open localhost:3000. The example database password is for the loopback-only development database.
For live client edits, run npm run dev:web in another terminal and set APP_ORIGIN=http://localhost:5173 in .env before restarting the server. Use that origin in the browser. For the standalone public website, use npm run dev:site.
Production requires HTTPS, PostgreSQL and private S3-compatible storage. Follow the deployment guide for configuration, first-owner setup and recovery.
For a registry deployment, use the public Docker Hub image and registry Compose. The illustrated storage guide maps the five prerequisites to their environment fields. Developers can install the bundled Claude Code and Codex plugins in two commands, then connect their own scoped key.
Plugin directory status
Checked 21 October 2026. Direct Claude Code and Codex installation is available from our public marketplace.
| Official directory | Current status |
|---|---|
| Claude Code | Version 0.2.2 passed its security scan. Publication was requested and is waiting for an Anthropic reviewer; it is not live in the official directory. |
| OpenAI | Local command/stdio MCP submission access is pending OpenAI review. Official directory submission and publication are not yet available for this package. |
These reviews have no confirmed publication date. Use the direct installation instructions today; directory status does not change the self-hosted Apache-2.0 product. See agent setup and distribution boundaries.
Browser extension
Build with npm run build:extension. Load the dist/extension/unpacked/ directory from Chrome's Load unpacked, or use the ZIP in dist/extension/. Enter your own Feedbacks server address and approve pairing in the web application. Website-wide permission is a separate optional action. Existing saved server connections remain available.
Repository map
| Path | Responsibility |
|---|---|
src/server/ |
Authentication, project access, business operations, persistence and transports |
src/shared/ |
Typed operation inputs, outputs and descriptions |
src/web/ |
Authenticated React application |
src/cli/ |
Bootstrap, JSON CLI and stdio MCP adapter |
plugins/ |
Codex and Claude Code plugin packages and review skills; MCP bundles generated at build |
extension/ |
Chrome Manifest V3 capture and review extension |
site/ |
Independently deployable public website |
tests/ |
Isolated authorization, transport and database tests |
ops/ |
Generic deployment configuration |
docs/ |
Public contributor and operator documentation |
Agent development
Start with AGENTS.md and the documentation map. Claude Code and Gemini CLI have thin adapters to the same instructions. See supported skills and client setup. For an isolated app with synthetic data and no deployment credentials:
npm ci
npm run harness:dev
The command builds the app and prints its loopback URL and private local access-file path. Each run has a disposable database and independent port.
Development
npm run check
# Optional native PostgreSQL concurrency tests (initdb and pg_ctl on PATH):
npm run test:postgres
check runs formatting, architecture/docs checks, type checking, tests, all builds, an isolated app smoke check and release-content checks. CI also runs the native PostgreSQL tests, dependency audit and secret scanning. A passing build is not evidence of production deployment or capacity.
License and community
The application, extension and website source are Apache-2.0 licensed. Dependencies retain their licenses. Read contribution guidelines, community standards, security reporting and trademark guidance.
Feedbacks MCP questions
How can I use Feedbacks with my coding assistant?
You can provide agents with context through MCP, API, and CLI, including approved project instructions and reviewer guidance.
Is Feedbacks free to use?
Yes, the complete product is free to self-host under the Apache-2.0 license.
What technologies are required to run the server?
The server requires Docker Compose, Bash, curl, and OpenSSL for the installer, and uses PostgreSQL and S3-compatible storage for production.
Can I see exactly what changed on my website?
Yes, the tool supports screenshot pins, annotations, full-page captures, and selected-text replacement suggestions.