MCP.Market

Feedbacks MCP server

by Softinator-TechLabs·io.github.Softinator-TechLabs/feedbacks·v0.2.3·33 stars

Visual website feedback, screenshots and team discussion for coding assistants. Self-hosted.

A90/100grade A
What users say
No reviews yet
Be the first
Safety scan
A90/100

not scanned yet

Adoption
Growing

33 stars

Reviews

Write one

Nobody has reviewed Feedbacks yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Feedbacks tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Feedbacks compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
90/100
higher than 83% of 48,255 servers
GitHub stars
33
more than 92% of 28,688 servers

Release history: 2 versions in the registry since 2026-10-01, latest 2026-10-21, typically one every 19 days.

Install Feedbacks in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the Feedbacks repository's README, as published. We do not edit it. Read it on GitHub

Feedbacks

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.

Run locally

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 BOOTSTRAPEMAIL, BOOTSTRAPNAME 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.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Feedbacks: common questions

Is Feedbacks MCP server safe?
Yes, by our scan: it is graded A (90/100). Read the Feedbacks safety report
Does Feedbacks need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Feedbacks maintained?
The last commit was 34 days ago (2026-10-01). The latest release is v0.2.3.
What can I use instead of Feedbacks?
Servers from other publishers that do the same job: Inspo MCP server.
How does Feedbacks compare with other MCP servers?
safety score 90/100 (higher than 83% of 48,255 servers); github stars 33 (more than 92% of 28,688 servers). Full comparison.

Alternatives to Feedbacks

Same job from other publishers: the closest match first, then the best rated.

  • Inspo
    Real production websites for coding agents: palettes, fonts, fold autopsies and reference JSX.
    A