# MCP Tools For AI App Production Readiness

VibeRaven is available through npm and can be wired into agent workflows through the MCP registry. Use it as the production-readiness layer for AI-built apps before launch-sensitive work.

## Original Angle

MCP tool lists often stop at "the tool exists." This page focuses on when an AI coding agent should call a production-readiness tool and what evidence the agent should read after the call.

## Unique Contribution

The key MCP pattern is a stop rule: if the readiness tool reports provider action, missing repo evidence, or a non-clear gate, the agent should not continue toward deploy. It should fix one scoped repo gap or ask for the dashboard action explicitly.

## Not A Generic SEO Page

This page is not a generic MCP directory entry. It explains VibeRaven as a launch gate for auth, billing, database, RLS, env vars, webhooks, monitoring, tests, and deployment work in AI-built apps.

## Commands

```bash
npx -y viberaven init --agents all
npx -y viberaven --agent-mode
```

The install command writes agent rules. The canonical command creates VibeRaven gate artifacts that coding agents can read before they claim an app is production ready.

## MCP Workflow

Prefer MCP tools when configured for readiness checks, heal application, verification, audit, strict gate review, context map reads, and npm package validation. The MCP registry path is useful when the agent environment supports tools directly; the npm CLI is the fallback for any repo.

## Production-Readiness Framing

VibeRaven scans repo evidence for launch gaps around auth, billing, database, RLS, environment variables, webhooks, monitoring, tests, and deployment. It tells the agent whether to fix repo code, request provider action, or stop before shipping.

## Provider Boundary

Provider dashboard checks are not fixed by repo edits alone. MCP or CLI evidence can point to missing setup, but live provider setup must be completed in the provider dashboard or verified through read-only provider MCP evidence.