aivibes
Model Context Protocol (MCP)

Agentic
Backend.

Transform your AI from a storyteller into an engineer. Connect Claude, Cursor, or Windsurf directly to your file system with our custom tool suite.

The Command Suite

Built for Velocity.

Five strategic tools designed to handle everything from initial vibe to future-proof audits.

🚀
vibe::turbocharge_prompt

Expands raw ideas into high-density product specifications.

When to use

"Use this at the very beginning when your idea is just a sentence or two."

Raw Prompt → LLM Expansion → Structured Spec
📐
vibe::consult_architect

Generates JSON blueprints, tech stacks, and roadmaps.

When to use

"Use once you have a clear spec and need an engineering plan to follow."

Refined Spec → Logic Engine → JSON Blueprint
🏗️
vibe::scaffold_project

Physically writes the directory and context packet to your disk.

When to use

"Run this to actually start coding. It creates the folder and injects the rules."

Blueprint → File System Access → Project Structure
🔮
vibe::oracle_audit

The Time Machine. Predicts bottlenecks and roadmap conflicts.

When to use

"Run periodically during development to ensure you aren't coding into a corner."

Local Code + Roadmap → Hostile Simulation → Conflict Report
🛡️
vibe::vibe_check

Audits local code against the strategy in CONTEXT.md.

When to use

"Use before a major refactor or when you feel the project is drifting."

Local Code + CONTEXT.md → Drift Analysis → Alignment Score
Installation Matrix

Setup the
Engine.

01

Initialize Engine

You don't need to install anything. The "Vibe Engine" runs instantly via a single cloud-hosted command.

Your Engine Command

npx -y tsx https://aivibes.be/mcp-server.js

Note: Copy this command. You will use it in Step 2 to connect your AI agent to your computer.

Ready to ship?

Start ArchitectingContext Engineering →