DOCUMENTATION / MCP TOOLS

Use AIPI through your coding agent

AIPI exposes the same closed-loop workflow to Codex and any MCP-capable IDE. The tools return evidence; the editor remains responsible for source changes.

The primary loop

`discover_task_context`

Search indexed workspace files, AST symbols, K Maps, findings, and evidence. Returns a bounded implementation chain.

`prepare_task_handoff`

Compiles and persists a revision-aware context pack for the coding agent.

`review_and_run_task_verification`

Executes the task plan, records proof, and reports drift or failed checks.

Useful supporting tools

trace_route locates callers, handlers, schemas, and models.
diff_contract compares frontend and backend shapes.
run_correction_workflow prepares and closes a fix loop.
generate_regression_test produces a native test after evidence exists.
check_blast_radius evaluates known downstream consumers.

Editor configuration

The initializer writes project-local configuration. A minimal MCP entry looks like:

{
  "mcpServers": {
    "aipi": {
      "command": "npx",
      "args": ["-y", "@vmise/aipi-companion", "mcp", "--root", "/path/to/project"]
    }
  }
}

Safety model

State-changing requests remain blocked until explicitly authorized. Fixture and test generation returns content to the editor rather than silently writing repository files.