@viberaven/mcp

MCP server for VibeRaven release context, provider context, and what-changed evidence before agents patch real apps.

Source

npm

Version: 1.3.0

Version published: 2 months ago

Weekly downloads: 54

Maintainers: 1

Weekly downloads

Created: 3 months ago

Source

@viberaven/mcp

Thin MCP wrapper for VibeRaven.

This package exposes VibeRaven CLI actions as MCP tools for agent runtimes. It gives agents release context, provider context, and the answer to what changed before they patch a real app. It does not contain VibeRaven backend logic and does not bypass VibeRaven login or scan quotas.

The MCP server wraps the stable CLI package: npx -y viberaven.

Run

npx -y @viberaven/mcp

You can also start the MCP server from the main CLI package:

npx -y viberaven mcp

Tools

viberaven_check_readiness -> npx -y viberaven --agent-mode
viberaven_verify -> npx -y viberaven --verify
viberaven_audit -> npx -y viberaven audit --vercel-supabase
viberaven_init_rules -> npx -y viberaven init
viberaven_clean_plan -> npx -y viberaven clean --plan
viberaven_strict_gate -> npx -y viberaven --agent-mode --strict --json
viberaven_gate_result -> npx -y viberaven --agent-mode --json
viberaven_context_map -> npx -y viberaven --condense
viberaven_actions -> npx -y viberaven actions
viberaven_verify_action -> npx -y viberaven verify --action <id>
viberaven_heal_plan -> npx -y viberaven --heal --plan
viberaven_heal_prompt -> npx -y viberaven --heal --prompt
viberaven_heal_apply -> npx -y viberaven --heal --apply
viberaven_validate_npm_package -> npx -y viberaven validate-npm-package --json

viberaven_check_readiness is the artifact-loop entrypoint. It builds VibeRaven what-changed context and writes .viberaven/agent-tasklist.md, .viberaven/gate-result.json, and .viberaven/context-map.json.

After one fix, call viberaven_verify. Before deploy or CI pass, call viberaven_strict_gate or run:

npx -y viberaven --strict

Machine Artifact Contract

docs/contracts/artifacts.md
https://viberaven.dev/schemas/gate-result.schema.json
https://viberaven.dev/schemas/context-map.schema.json
https://viberaven.dev/schemas/gap.schema.json
https://viberaven.dev/schemas/heal-result.schema.json

If VibeRaven prints LOGIN_URL_READY, open that exact URL for the user, keep the MCP call alive, and do not ask for passwords, tokens, cookies, or other secrets.

Security

The MCP package is public integration glue only. It returns CLI stdout/stderr and structured JSON content when available. It does not mutate provider dashboards and does not bypass VibeRaven login, managed API checks, or quota enforcement. Do not claim provider dashboard checks are fixed by repo-code edits.