Reported issues for io.github.PV-Bhat/vibe-check-mcp-server
Pod holds 15 of 15 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.
Back to io.github.PV-Bhat/vibe-check-mcp-server.
Most discussed
npx @pv-bhat/vibe-check-mcp quickstart fails install and produces no response
Trying to run any of the npx @pv-bhat/vibe-check-mcp commands immediately starts and stops the server with no response. This started when trying to install the server into VS Code via:
"vibe-check-mcp": {
"command": "npx",
"args": ["-y", "@pv-bhat/vibe-check-mcp", "start", "--stdio"]
}
Which produced this log output:
2025-10-31 12:02:52.870 [info] Starting server vibe-check-mcp
2025-10-31 12:02:52.871 [info] Connection state: Starting
2025-10-31 12:02:52.875 [info] Starting
[Read the thread](https://github.com/PV-Bhat/vibe-check-mcp-server/issues/74) · 2025-10-31 · closed · external user · 4 comments
### Running npx @pv-bhat/vibe-check-mcp install --client claude
Running sudo npx @pv-bhat/vibe-check-mcp install --client claude nor npx @pv-bhat/vibe-check-mcp install --client claude seem to result in anything be installed in my local claude code agent. Am I missing something?
[Read the thread](https://github.com/PV-Bhat/vibe-check-mcp-server/issues/50) · 2025-10-15 · closed · external user · 3 comments
### [Feature Request] Support Claude Code (Max subscription) integration in Cline without external API key
## Background & Motivation
I've __tested vibe-check-mcp via API__ and I'm genuinely __excited about the results__! The metacognitive feedback it provides is wonderfull, and make sonnet 4.5 very close to opus 4.1 result, without the cost / session lock.
## Current Situation
I'm using __Cline__ (Claude Code extension) in VS Code with a __Claude Code Max subscription__, which gives me access to Claude models directly through the extension.
I've successfully configured vibe-check-mcp in Cline's
[Read the thread](https://github.com/PV-Bhat/vibe-check-mcp-server/issues/47) · 2025-10-11 · closed · external user · 5 comments
### Provide a one-liner installer/runner (first-party npx command) for zero-friction setup
**Problem / Motivation**
Vibe Check MCP is great, but the current quickstart asks users to clone and build locally:
```bash
git clone https://github.com/PV-Bhat/vibe-check-mcp-server.git
cd vibe-check-mcp-server
npm install
npm run build
This adds friction for new users and for scenarios where a fast, disposable trial is preferred (labs, workshops, CI). Smithery offers a convenient path, but it’s a third-party dependency. Many MCP tools now expose a first-party npx command (e.g., `np
Read the thread · 2025-10-08 · closed · external user · 2 comments
Q: Can Vibe Check be compatible with "PM" MCPs?
There are some examples of project planners and architectural design tooling available. Do you think Vibe Check will be compatible?
- Task Master https://github.com/eyaltoledano/claude-task-master/discussions/487
- BMAD's set of tooling https://github.com/bmadcode/BMAD-METHOD
- CursorRIPER https://github.com/johnpeterman72/CursorRIPER
- SuperClaude https://github.com/SuperClaude-Org/SuperClaude_Framework
- ConPort (previously RooFlow) https://github.com/GreatScottyMac/context-portal
Read the thread · 2025-07-29 · closed · external user · 3 comments
Q: Does VibeCheck read documentation/guides?
This might come as a surprise, but documentation and user guides are often useful to deal with common issues, and it is good to have them "on tap" (locating the related URLs). But it leads to a few different problems:
- How do we update documentation URLs if the page starts to move? Or do we use InternetArchive (and local caching) appropriately?
- What if the user guides in Medium or Reddit are incorrect or outdated? How can we be sure, beyond checking the post date?
- How would the search en
Read the thread · 2025-07-28 · closed · external user · 3 comments
Q: How do you handle dependency issues?
Recently I saw this tool out in the wild and wonder how it can be integrated or mimicked when it comes to high-complexity codebases https://github.com/FSoft-AI4Code/DP-parser
Read the thread · 2025-07-28 · closed · external user · 3 comments
Selecting alternative models from OpenRouter
Coming from the side of DeepSeek and Qwen, would it be possible to use other LLMs?
Bonus: Ollama for portable models and faster sanity checks
Read the thread · 2025-06-30 · closed · external user · 3 comments
Most recent
vibe_learn can replace the entire log with one entry and return added: true (2.7.6)
Summary
In build/utils/storage.js, a single unreadable/torn read of ~/.vibe-check/vibe-log.json causes the
entire history to be replaced by one entry, while the tool reports success. With more than one MCP
process writing, the torn state is reachable in normal use.
Reproduction — one call, no race required
The race only has to have happened once, leaving a file some later call reads. Simulate that state directly:
# 2.7.6, sandboxed HOME so the real store is untouche
[Read the thread](https://github.com/PV-Bhat/vibe-check-mcp-server/issues/107) · 2026-08-21 · open · external user · 0 comments
### Idea: Quantitative reliability metrics alongside qualitative feedback?
Hey — love the concept of "vibe check" for AI agents. Mentor-like qualitative feedback is something the ecosystem really lacks.
It made me think about the quantitative side of the same problem:
Your server tells agents *how well they're doing* (qualitative).
But there's no standard way to tell agents *how reliable their tools are* (quantitative).
For example: an agent calls 5 different MCP tools. 4 work great. 1 fails silently 15% of the time. The agent has no signal about this.
I've been bu
[Read the thread](https://github.com/PV-Bhat/vibe-check-mcp-server/issues/93) · 2026-03-31 · closed · external user · 1 comment
### check_constitution tool returns invalid MCP content type
## Bug Description
The `check_constitution` tool returns an invalid content type that causes a Zod validation error in MCP clients (tested with Claude Code).
## Environment
- MCP Client: Claude Code
- vibe-check-mcp-server: latest
## Error
When calling `check_constitution`, the following Zod validation error is returned:
Invalid literal value, expected "text" received: "json" path: ["content", 0, "type"]
The MCP protocol expects content types to be one of: `text`, `image`, `audio`
[Read the thread](https://github.com/PV-Bhat/vibe-check-mcp-server/issues/84) · 2025-11-30 · closed · external user · 1 comment
### Claude Code Skills instead of MCP?
I would love to have this as Claud Code Skills instead of an MCP.
When coding with Claude Code it would be a better experience and Skills might be more efficient with context tokens.
What do you think?
[Read the thread](https://github.com/PV-Bhat/vibe-check-mcp-server/issues/72) · 2025-10-29 · closed · external user · 2 comments
### Windsurf: MCP tools/call produces no output — initialization OK, tools/list works
Hi,
I’ve been trying to get the `@pv-bhat/vibe-check-mcp` server (v2.7.1) working with Windsurf and have run into a consistent issue where tool calls never return any output over stdio. Here’s everything I’ve done:
1. Installed Node 20.19.3 and the package globally: `npm install -g @pv-bhat/vibe-check-mcp@2.7.1`.
2. Added the server to both Windsurf config locations:
- `~/.codeium/mcp_config.json`
- `~/.codeium/windsurf/mcp_config.json`
Both now point to the direct CL
[Read the thread](https://github.com/PV-Bhat/vibe-check-mcp-server/issues/61) · 2025-10-22 · closed · external user · 1 comment
### Support changing API endpoint (to implicitly support z.ai)
As per [z.ai documentation](https://docs.z.ai/scenario-example/develop-tools/claude), the two env vars are already set:
"ANTHROPIC_AUTH_TOKEN": "your_zai_api_key",
"ANTHROPIC_BASE_URL": "https://api.z.ai/api/anthropic",
It would be valuable to support these out of the box.
[Read the thread](https://github.com/PV-Bhat/vibe-check-mcp-server/issues/59) · 2025-10-19 · closed · external user · 1 comment
### How do i use the auto start but with openai key in claude code ?
How do i use it with claude code, when using the auto start on a mac ?
i added this to claude.json but it aint working it wont connect
"vibe-check": {
"command": "node",
"args": [
"/Users/tg/Downloads/MCP/vibe-check-mcp-server/build/index.js"
],
"env": {
"OPENAI_API_KEY": "my key"
}
[Read the thread](https://github.com/PV-Bhat/vibe-check-mcp-server/issues/38) · 2025-10-09 · closed · external user · 1 comment
The remaining reports are on [the project's issue tracker](https://github.com/PV-Bhat/vibe-check-mcp-server/issues).