Feedbacks

What Feedbacks MCP server does

Feedbacks MCP server gives coding assistants access to selected evidence from a Feedbacks team server. The surrounding application collects website feedback through screenshots, annotations, full-page captures, selected-text suggestions, video, and session-only recordings. It also stores discussion threads, event timelines, console data, network information, performance details, checksums, and verification checks.

The MCP connection is intended to add project and review context to agent work. Approved project instructions, reviewer guidance, and responsibilities can be provided through MCP, the API, and the CLI. Agent access is scoped rather than being an unrestricted view of the whole installation. Recording exports are also supported.

How it works

An administrator first deploys one Feedbacks installation for an organization. The team then connects the Chrome extension to that server and configures project context, members, and any optional GitHub App integration. Each developer configures a personal MCP connection using a scoped key. The extension captures browser evidence; it does not run the server.

Feedbacks MCP server works alongside the web application and its storage layer. Production deployments require HTTPS, PostgreSQL, and private S3-compatible storage. The repository also includes a CLI with a stdio MCP adapter, so an MCP-compatible coding assistant can connect through a local process after the application is available.

Setup and configuration

For local development, the documented sequence uses Node.js 22 or 24, npm, and Docker Compose for PostgreSQL:

• Clone the repository and run npm ci.
• Copy .env.example to .env.
• Start the development database with docker compose -f compose.dev.yaml up -d --wait.
• Set BOOTSTRAP_EMAIL, BOOTSTRAP_NAME, and a unique BOOTSTRAP_PASSWORD before running bootstrap.
• Run npm run bootstrap, npm run build, and npm run dev:server.

The bootstrap password should be removed after the first owner is created. A registry deployment is also documented through the public Docker Hub image and registry Compose configuration. Follow the project’s deployment documentation for production configuration, recovery, and storage fields.

Tools and capabilities

The available MCP-related capabilities described by the project include:

• Reading approved project instructions and reviewer guidance within scope.
• Providing agent responsibilities and project context.
• Reading scoped feedback and evidence bundles.
• Exporting recordings for investigation or review.
• Using the same operational context through the API and JSON CLI.

The broader Feedbacks workflow supports assignments, categories, tags, saved views, point progress, and optional GitHub Issues. These application features are not necessarily separate MCP tools.

Limitations and notes

Feedbacks MCP server is part of an early 0.x release. One application deployment serves one organization. Public registration, billing, SSO, and shared-database multi-tenant customer support are not implemented. The team must provide and operate the infrastructure, including production storage and PostgreSQL.

The README names Claude Code, Codex, and Gemini CLI integrations. The repository includes bundled Claude Code and Codex plugins, while Gemini CLI uses a thin adapter to the same instructions. Access depends on the configured server, project scope, and developer credentials.