VibeCheck MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_trackA | Fetch and format a VibeCheck bug report. Returns a comprehensive markdown report including console logs, network requests, user actions, and web vitals. For screenshot tracks, also returns the screenshot image. |
| analyze_track_errorsA | Analyze errors in a VibeCheck bug report. Returns a focused view of console errors and failed network requests with stack traces and response bodies. |
| get_track_networkA | Analyze network requests in a VibeCheck bug report. Returns failed requests with response bodies, slow requests sorted by duration, and a summary table of all requests. |
| get_track_performanceB | Analyze performance of a VibeCheck bug report. Returns web vitals with ratings, navigation timing per page, and a performance assessment with optimization suggestions. |
| get_track_actionsB | Get user action timeline from a VibeCheck bug report. Returns a chronological timeline of user interactions, auto-generated steps to reproduce, and an action type breakdown. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct aspect of bug report analysis: errors, full report, actions, network, and performance. There is no overlap in their purposes.
All tools use snake_case and follow a verb_noun pattern (analyze_track_errors, get_track, get_track_actions, etc.), with consistent verb prefixing and resource targeting.
Five tools is an ideal count for the scope of analyzing a single bug report, covering all key dimensions without excess or deficiency.
The set covers the full breadth of analysis needs for a VibeCheck bug report: errors, user actions, network requests, performance metrics, and a comprehensive overview. No obvious gaps.