Log inSubmit server
Vibe Monitor logo

Vibe Monitor

Local architecture monitoring for AI coding sessions, with checkpoints, findings, historical signals, and explicit outcome tracking.

InstallRepositoryWebsite
Get support Full README Compare alternatives Embed widget

Install Vibe Monitor

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "vibe-monitor": {
      "command": "npx",
      "args": [
        "-y",
        "--registry=https://registry.npmjs.org",
        "@vibe-monitor/setup@latest",
        "mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 17 tools correctly (2d ago).

Overview

Vibe Monitor gives AI coding agents local, read-only architecture analysis during development sessions. It tracks structural evolution through session starts, checkpoints, project status, staged findings, and historical outcome records, while keeping source files, diffs, prompts, paths, and secrets off Vibe Monitor servers. Reach for it when a growing project needs evidence-based guidance on coupling, module responsibilities, tests, and architectural pressure. The client requires Node.js 22+ and supports Cursor, Claude Code, Codex, and other agent integrations.

Use cases

  • Review architecture pressure after a feature batch
  • Track structural changes across coding sessions
  • Explain a staged finding before refactoring
  • Submit bounded semantic architecture reviews
  • Record explicit recommendation outcomes and feedback

Key features

  • Read-only local source analysis
  • Session checkpoints and historical signals
  • Stage-aware findings with pressure scores
  • Product-intent and finding intelligence
  • Bounded semantic architecture reviews
  • Explicit outcome and feedback tracking

Tools17

What Vibe Monitor lets your agent do. Expand a tool for its parameters.

Verified live~3.2k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

What it can do

From the 17 tools this server returned when we ran it.

Makes network requests · 4Read-only tools · 17
Network at startup3 connections
Files written at startup3
Install scriptsNone
npm provenanceSigned build
Package age19 days
Maintainers1

Observed 2026-10-26 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · @vibe-monitor/setup@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars4Stargazers on the source repository.
Last commit4d agoMost recent push to the default branch.
MaintenanceActively maintainedStatus declared by the project or listing owner.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed17Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Vibe Monitor works

What Vibe Monitor does

Vibe Monitor acts as a local architecture advisor for AI-assisted coding workflows. It examines accessible project code without modifying it, then helps an agent identify accumulating architectural pressure, coupling, module-responsibility issues, and testing signals. Recommendations are organized around timing: what to do now, what to prepare for, what not to address yet, and which future change should trigger another review.

The system is session-oriented rather than an always-running daemon. A session can be started or resumed before work, skipped at the user's request, and checkpointed after a meaningful implementation batch. Historical snapshots make it possible to compare how architectural signals change across coding sessions.

How it works

Structural scans run locally and do not call an LLM. Optional agent-assisted interpretation can use model tokens, while the local client retains the full review text for semantic architecture reviews. Vibe Monitor does not upload source files, diffs, prompts, project paths, or secrets to its servers. Derived metrics and product-operation events may be sent through pseudonymous telemetry, and free architecture analysis uses a cloud policy service.

Findings expose an evolution stage and pressure score. Agents can request an explanation for an individual finding, including its evidence, standards mapping, heuristic disclosure, staged action, and an over-engineering guard. Product-intent context can distinguish advisory inferences from facts explicitly stated by the user. Explicit intent is stored locally when the user has clearly provided it.

For findings that recommend semantic review, the client can create a bounded ARP v1 request containing normalized architecture evidence rather than raw source code or a project path. A submitted review sends bounded structured metadata for comparison and outcome learning; full model-generated review text remains local. Different agents may return different verdicts.

Setup and configuration

Install the unified open-source client with Node.js 22 or newer:

Terminal
npx -y --registry=https://registry.npmjs.org @vibe-monitor/setup@latest install

The installer registers supported agent MCP or rules configuration and may create local history or backups. No activation code is required, and no separate monitoring daemon needs to be installed. The same client is used across Free, Pro, and Team plans.

New installations enable bounded pseudonymous product telemetry by default with notice. Use install --no-telemetry or run vibe-monitor telemetry off to disable collection. Disabling telemetry pauses Free architecture analysis, and an existing opt-out remains in effect after reinstall. Account linking is available through the MCP interface when the user explicitly requests it; the account-connect operation itself makes no network request.

Tools and capabilities

The MCP tool set covers the complete review lifecycle:

  • vibe_session_start starts or resumes a bounded assessment, while vibe_skip_current cancels an in-progress start without stopping coding or future monitoring.
  • vibe_checkpoint stores a snapshot after an implementation batch. vibe_project_status reads current architecture-evolution status without creating a snapshot.
  • vibe_findings returns stage-ordered findings and pressure scores. vibe_explain_finding provides evidence and a staged explanation, while vibe_finding_intelligence reports risk trends and review status.
  • vibe_product_intent reads intent context, and vibe_set_product_intent stores facts the user has explicitly stated.
  • vibe_get_architecture_review_request prepares bounded semantic-review input, and vibe_submit_architecture_review submits one review.
  • vibe_outcome_record_action, vibe_outcome_verify, and vibe_outcome_status track explicitly reported actions, verification, comparable follow-up, and recurrence. They do not infer that code changed or that a recommendation caused an improvement.
  • vibe_feedback records clear user feedback when a finding was useful, wrong, premature, late, or confusing.
  • vibe_version reports the running process version, installed versions, staged update, and update state. vibe_account_connect explains how to link an installation when requested.

The public client is Apache-2.0 licensed and auditable. Cloud policy and scoring configuration is a separate proprietary service; its delivery does not authorize raw-source uploads or arbitrary remote-code execution.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Vibe Monitor

Vibe Monitor is an MCP server that analyzes accessible project source locally for AI coding workflows and connects to supported agent integrations such as Cursor, Claude Code, and Codex. Its main tools start sessions, create checkpoints, inspect status and findings, explain recommendations, and record explicit outcomes and feedback.

Install it with Node.js 22 or newer by running `npx -y --registry=https://registry.npmjs.org @vibe-monitor/setup@latest install`. The installer configures supported agent MCP or rules settings and may create local history or backups.

Yes, Vibe Monitor supports Cursor. Its installer registers the required supported-agent configuration, allowing Cursor to use the MCP tools for session starts, checkpoints, findings, architecture explanations, and related workflow tracking.

No, Vibe Monitor keeps source files, diffs, prompts, project paths, and secrets off its servers. Local scans produce derived metrics, while disclosed pseudonymous telemetry and bounded review metadata may be sent separately.

Disable telemetry during installation with `install --no-telemetry`, or run `vibe-monitor telemetry off` afterward. Disabling collection pauses Free architecture analysis, and an existing opt-out persists through reinstall.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewVibe Monitor AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/vibe-monitor?style=directory)](https://allmcps.com/mcp/vibe-monitor)
HTML Embed
<a href="https://allmcps.com/mcp/vibe-monitor"><img src="https://allmcps.com/api/badge/vibe-monitor?style=directory" alt="Vibe Monitor on AllMCPs" /></a>