Vibe Monitor
# Vibe Monitor
[](https://allmcps.com/mcp/vibe-monitor?verify=28ea83f4-389c-4670-a934-3f0202997d1a)
**A local architecture advisor for AI coding workflows.** AI agents ship features fast; Vibe Monitor helps you see when architectural complexity is accumulating and what actually needs attention.
## The open-source MCP server
This repository contains an **actual local MCP server** (stdio transport), not only an npm installer or a cloud dashboard. The MCP server runs on your own computer and exposes read-only architecture checks and change-history snapshots to an MCP-capable coding agent. It does not rewrite your project source.
Example MCP tools implemented in [`src/mcp.js`](src/mcp.js):
| MCP tool | What it does locally |
| --- | --- |
| `vibe_session_start` | Start or resume a bounded assessment of one coding project |
| `vibe_project_status` | Read the current project's architecture signals without creating a snapshot |
| `vibe_checkpoint` | Record a post-change snapshot to compare structural evolution |
| `vibe_findings` | Show prioritized findings and concrete next steps |
| `vibe_evolution_audit` | Inspect architecture evolution across recorded checkpoints |
| `vibe_version` | Inspect the actual running/installed version |
**Install and register the local MCP server with supported agents:**
```sh
npx -y --registry=https://registry.npmjs.org @vibe-monitor/setup@latest install
```
**Direct stdio MCP command** (for clients that configure `command` / `args` themselves; Node.js 22+):
```sh
npx -y --registry=https://registry.npmjs.org @vibe-monitor/setup@latest mcp
```
The npm package implements both the installer and MCP server. The server's official name is `io.github.tubban1/vibe-monitor`; its [registry manifest](server.json) declares the local `mcp` argument. Some analysis features depend on the signed Cloud scoring policy; installing does not grant cloud access to your source code. See the telemetry details below.
## Get started — official stable release
The official open-source MCP server and installer are distributed through npm as **`@vibe-monitor/setup@latest`**. This source tree targets the reviewed stable package **`@vibe-monitor/setup@1.0.15`**. Verify publication with `npm view @vibe-monitor/setup dist-tags.latest` (a source version alone does not establish npm availability); the previous verified npm release was 1.0.14 (2026-11-03).
```bash
npx -y --registry=https://registry.npmjs.org @vibe-monitor/setup@latest install
```
On a new install, bounded **pseudonymous** product telemetry defaults **ON**, with notice. Use `install --no-telemetry` or `vibe-monitor telemetry off` to disable collection; this pauses Free architecture analysis. An existing opt-out survives reinstall. No activation code is required.
**Not sure whether your projects need it?** Give your coding Agent this one canonical instruction:
**[Analyze accessible code projects and return a direct recommendation →](docs/AGENT_EVALUATION.md)**
The Agent must inspect code projects already accessible in its current workspaces, decide which would benefit (if any), and report the results **to you in the chat**. No installation or external report submission occurs during the assessment.
## Your source code is not uploaded
**Vibe Monitor analyzes source locally. It never uploads source files, diffs, prompts, project paths or secrets to Vibe Monitor servers.** Bounded derived metrics and product-operation events can be sent through disclosed pseudonymous telemetry, not the code itself. You can **audit the open-source implementation** instead of relying on a marketing promise:
- [Local telemetry event projection and strict wire fields](src/telemetry.js)
- [Allowed telemetry field checks](src/telemetry-quality.js)
- [Outbound telemetry transport](src/cloud.js)
- [Detailed security boundaries](SECURITY.md) and [current telemetry/privacy contract](docs/governance/TELEMETRY_PRIVACY_V1.md)
The *coding Agent itself* (Codex, Claude Code, Cursor, etc.) may process code under **its own provider's terms**. That is separate from Vibe Monitor's own upload behavior.
## What you gain
- **Evidence before alerts:** architecture pressure, coupling, module responsibilities and tests.
- **Practical priorities:** what to improve now, what to leave alone and when to reassess.
- **Historical perspective:** how architectural signals evolve across coding sessions.
- **Low overhead:** local structural scans do not call an LLM; optional Agent-assisted interpretation may use tokens.
Vibe Monitor scans project code read-only. **Installation** registers supported Agent MCP/rules configuration and may create local history/backups. No separately installed always-on monitoring daemon is required.
## Documentation
[Official installation and verification](docs/INSTALL.md) · [Agent evaluation/report protocol](docs/AGENT_EVALUATION.md) · [Illustrative architectural scenarios](docs/EXAMPLES.md) · [Security](SECURITY.md) · [Telemetry/privacy](docs/governance/TELEMETRY_PRIVACY_V1.md) · [Website](https://vibe.fde.fan)
### Open source
The unified client is Apache-2.0 licensed and publicly auditable here. Signed Cloud policy/scoring configuration is a separate proprietary service; policy delivery does not grant permission to upload raw source or execute arbitrary remote code. Official release provenance: [GitHub Releases](https://github.com/tubban1/vibe-monitor/releases) and [npm `@vibe-monitor/setup`](https://www.npmjs.com/package/@vibe-monitor/setup).TDQS
Scored across 19 tools
Several tools have overlapping read-oriented purposes: vibe_project_status, vibe_findings, vibe_finding_intelligence and vibe_evolution_audit all surface status/risk information, and vibe_explain_finding vs vibe_finding_intelligence both target a single finding. The verbose descriptions do help differentiate (intelligence = trend/evidence, explain = evidence/standards/action), and the vibe_outcome_* trio is cleanly separated, but the boundaries still require careful reading.
The vibe_ prefix and snake_case are used consistently throughout, which is good. However, the ordering convention is mixed: some names are verb_noun (vibe_explain_finding, vibe_set_product_intent, vibe_skip_current) while others are noun-first (vibe_session_start, vibe_project_status, vibe_outcome_record_action, vibe_checkpoint, vibe_findings). Readable but not predictable.
At 19 tools this sits in the heavy-but-arguably-justified band for a monitoring/audit product with distinct lifecycle phases (session, audit, findings, feedback, outcome, architecture review). Each tool does map to a real concept, but the surface is large enough that several near-synonymous read tools could likely be consolidated.
The recommendation lifecycle is unusually well covered end-to-end: findings, explanation, feedback, reported action, verification, and outcome status, plus session start/skip, checkpoint, version, and architecture review request/submit. Minor gaps exist (no tool to suppress/dismiss or list findings history/sessions, no account unlink), but agents can work around these.