Vibe Engineering MCP

project_initialize

Initialize or connect a Vibe Engineering project, creating SQLite operational state and a .vibe/ directory for managed requirements, tasks, and checkpoints.

Instructions

Initializes or connects to a Vibe Engineering Project with SQLite operational state and .vibe/ directory

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "description": "<description>"
    },
    "name": "project_initialize"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Project name
`rootPath`	No	Project root directory path (defaults to current working directory)
`description`	Yes	Detailed project description and purpose
`initialPhase`	No	Initial development phase (e.g. V0_FOUNDATION)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 4, 2026

TDQS

B3.1/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Without annotations, the description carries the full disclosure burden. It mentions creation of SQLite state and a .vibe/ directory, which hints at a write operation, but doesn't state whether it requires permissions, is idempotent, what happens if the project already exists, or what it returns. This is a significant gap for a mutation tool with no annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence that is front-loaded and wastes no words. It could be more informative, but conciseness itself is good.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is a setup/mutation operation with no annotations, no output schema, and four parameters. The description is too thin to guide an agent on when and how to use it, missing details like idempotency, required permissions, or effects on existing projects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all four parameters. The description only names the tool and mentions SQLite/.vibe, adding no parameter semantics. Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Initializes or connects to a Vibe Engineering Project') and mentions side effects (SQLite operational state, .vibe/ directory). It doesn't differentiate from siblings like project_resume or project_inspect, but the core purpose is clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. With siblings like project_resume, project_inspect, and workspace_create, an agent needs to know which one to pick. The description omits any when-to-use or prerequisite information.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.