aivibes
Model Context Protocol (MCP)

The AI
Amplifier.

Not a code generator. An intelligence multiplier for your IDE AI. Strategic context that fits in ~2,000 tokens instead of 50,000.

The AI-to-AI Loop

Strategic Brain.

The MCP advises; your IDE AI executes. Compressed context, maximum efficiency.

🚀
vibe::turbocharge_prompt

Expands raw ideas into high-density product specifications.

When to use

"Use this at the very beginning. Now auto-saves to PRODUCT_SPECIFICATION.md if targetPath is provided."

Raw Prompt → LLM Expansion → PRODUCT_SPECIFICATION.md
📐
vibe::consult_architect

Generates JSON blueprints, tech stacks, and roadmaps with auto-expansion.

When to use

"Generates PROJECT_BLUEPRINT.json. Includes 300s timeout for deep architectural simulation."

Idea → Architecture Engine → PROJECT_BLUEPRINT.json
🏗️
vibe::scaffold_project

Physically writes the directory and context packet to your disk.

When to use

"v2.10-complete: Supports API_SERVICE, CLI_TOOL, BROWSER_EXTENSION, and MOBILE_APP."

Blueprint → Specialized Templates → Architecture Audit → File System
🛡️
vibe::vibe_check

Audits local code against the nearest localized strategy. Now with v2.10 Heuristic Scoring.

When to use

"Intelligent Downward Search. Returns project score (~60 max) and breakdown."

Path → Project Discovery → CONTEXT.md Audit → Score + Breakdown
🎯
vibe::vibe_next

Suggests the most important strategic next step with a detailed feature brief.

When to use

"Analyzes implemented files and roadmap. Returns ai_instructions for IDE AI handoff."

CONTEXT.md + Code → Strategic Analysis → Feature Brief + AI Instructions
🔮
vibe::oracle_audit

The Time Machine. Predicts bottlenecks and roadmap conflicts.

When to use

"Now with Architecture Defense heuristics and verbose path scoring feedback."

Local Code + Roadmap → Oracle Simulation → BLOCKER_WARNING.md
📊
vibe::vibe_status

Returns current server version, capabilities, and environment info.

When to use

"Use for debugging or verifying the MCP server is running correctly."

System Query → Version + Platform + Capabilities
Installation Matrix

Setup the
Engine.

01

Initialize Engine

Download and run the Vibe Engine in your project directory.

Mac / Linux

curl -L https://aivibes.be/mcp-server.js -o mcp-server.js && node mcp-server.js

Windows (PowerShell)

curl.exe -L https://aivibes.be/mcp-server.js -o mcp-server.js; node mcp-server.js
✓

Verify: You should see "vibe-mcp" version info and a message saying the server is listening on stdio. Keep this terminal open!

Ready to ship?

Start ArchitectingContext Engineering →