MCP.so
Sign In
Servers

VibeCheck

@joeerario

Feedback MCP Server

Overview

What is VibeCheck?

VibeCheck is a simple feedback collection tool for Claude Code that automatically captures cost data and git change information. It runs as a local MCP server and allows users to submit helpfulness ratings, time saved, and experience summaries directly from the Claude Code terminal.

How to use VibeCheck?

Install Node.js ≥18, Git ≥2.23, and the Claude Code CLI globally. Clone the repository, run npm install, optionally configure .env with your ANTHROPIC_API_KEY, and execute npm run preflight to verify the environment. In Claude Code, use the command /project:feedback to submit feedback, which automatically includes git changes and cost data from the /cost command.

Key features of VibeCheck

  • Collects helpfulness ratings (1–5) and time saved (in minutes)
  • Automatically analyzes git changes and generates summaries
  • Integrates cost data from Claude Code’s /cost command
  • Stores all feedback locally in .VibeCheck/feedback.ndjson
  • Runs as a local MCP server on http://127.0.0.1:6111

Use cases of VibeCheck

  • Gathering structured feedback on Claude Code interactions during development
  • Tracking time saved and cost incurred per session to measure productivity
  • Associating code changes with user experience for retrospective analysis
  • Keeping all feedback data on‑premise for privacy and audit purposes

FAQ from VibeCheck

What are the prerequisites for using VibeCheck?

You need Node.js ≥18, Git ≥2.23, and the Claude Code CLI (claude-code) installed globally.

How do I submit feedback with Claude Code?

Run /project:feedback in the Claude Code terminal. You can provide a helpfulness rating (1–5), time saved (in minutes), and a brief summary. The tool automatically analyses git changes and includes cost data if available.

How is cost data integrated into feedback?

First run /cost in Claude Code to view usage statistics, then run /project:feedback. VibeCheck scans terminal history for cost data or uses cached information and includes it in the submission.

Where are feedback entries stored?

All feedback entries are saved locally in the .VibeCheck/feedback.ndjson file, containing rating, time saved, summary, git changes, and cost data.

How does the server run and is it secure?

The server starts automatically when needed, or you can manage it manually with npm run server. It runs locally at http://127.0.0.1:6111 and all data remains on your machine.

More from Other