# VibeRaven MCP

VibeRaven MCP is the structured interface for the VibeRaven Production Protocol and Agent Context + Production Gate.

## CLI MCP entrypoint

```bash
npx -y viberaven --mcp
```

## Production tools and resources

- `viberaven_check_readiness`
- `viberaven_heal_apply`
- `viberaven_verify`
- `viberaven_strict_gate`
- `viberaven_gate_result`
- `viberaven_context_map`
- `viberaven_prp_current`
- `viberaven_prp_findings`
- `viberaven_prp_next_action`
- `viberaven_verify_url`
- `viberaven_mark_manual_evidence`
- `prp://current`
- `prp://findings`
- `prp://next-actions`
- `prp://mission-map`
- `prp://context-map`

Prefer `viberaven_prp_current` when the client handles MCP tools well. Prefer `prp://current` when the client consumes MCP resources more naturally than tool calls. Use `viberaven_mark_manual_evidence` for dashboard-bound proof that repo edits cannot clear on their own.

## CLI fallback

```bash
npx -y viberaven --agent-mode
```

Agents should read `.viberaven/prp.json` first, then `.viberaven/gate-result.json` and `.viberaven/context-map.json`. Follow `nextActions`, apply safe repo-code fixes directly when VibeRaven provides a supported MCP/heal action, respect `batchSize`, and verify once per batch. Do not stop while `decision.status` is `blocked` or `gate.status` is not `clear`.

```bash
npx -y viberaven --verify
npx -y viberaven --strict
```

## Before npm install

Call `viberaven_validate_npm_package`, then run:

```bash
npx -y viberaven --agent-mode
```

## Boundaries

Do not use MCP to ask for secrets or claim provider dashboard work is complete from repo edits.