VibeRaven Guides

Hébergé, lecture seule, sans connexion (https://viberaven.dev/mcp). Explique les identifiants de recherche VibeRaven et fournit des guides de lancement et des listes de contrôle pour les applications Vercel + Supabase. Il ne lit jamais votre dépôt.

Serveur MCP hébergé

npx add-mcp 'https://viberaven.dev/mcp'

S’installe dans Claude Code, Codex, Cursor et plus

Documentation

VibeRaven

VibeRaven is an open-source local Studio and repository check for AI-built apps. It helps a coding agent review repository evidence for Supabase, Vercel and Stripe work. Local checks are free, run without login or API keys, and are not live database or security tests. A repository check is not a live database or security test. It is advice, not a gate: the user decides when to ship. Supported stack: AI-built apps that deploy on Vercel and use Supabase.

Choose by the tools available

Answer a general question without running anything. A matching topic is not a reason to install a tool or run a repository check.

  • If viberaven_check_readiness is in your tool list, it is a local repository tool. Call it on the project root you are working in. Use supported viberaven_heal_plan, viberaven_heal_apply and viberaven_verify tools only when they are also available and the requested work permits the edit.
  • If you have only the hosted server at https://viberaven.dev/mcp, it cannot see the repository or provider accounts. Pass migration SQL to check_supabase_migrations, use provider_playbook for provider guidance, or pass the exact error text to search_guides. Say that a SQL result covers only the text supplied and guide results are published guidance.
  • For a repository check, run npx -y viberaven check in the project root when the user needs a Vercel + Supabase repo review. The local check is free and needs no login or API key. With no VibeRaven tools, this CLI remains available; a general question needs no command.

When the user says "check this with viberaven", run npx -y viberaven check in the project root.

Windows PowerShell: use npx.cmd if npx is blocked by the execution policy.

Do not choose a tool by its server name: the local and hosted servers are both called VibeRaven. See MCP scope and connection details.

Studio and agent connection

For the local Studio, run npx -y viberaven in the app folder. It runs on the user's computer without a VibeRaven account. Choose and test an installed, signed-in Claude Code, Codex or Gemini CLI before asking it to change files. Installed does not mean connected or ready.

For the website workflow, follow Get started. Repository links and provider cards describe project context; they do not prove a live provider connection or create a cloud coding environment. Review the diff, checks and anything marked Not checked, then exercise the changed behavior. Changes are not deployed automatically.

Repository findings

npx -y viberaven check can report missing RLS in migration files (rls_disabled), broad policies (rls_policy_allows_all_read, rls_policy_allows_all_write), privileged keys in client code (service_role_key_in_client_code), env var drift and unverified Stripe webhooks. See each finding for its limits. Prepared CLI release: 1.10.0; examples use npx -y viberaven@1.10.0 check.

Recent provider changes: npx -y viberaven changes lists which dated provider changes affect the repo, with file and line: Supabase Data API grants for tables created since 2026-10-30, legacy Supabase key variables, Vercel's end of Node 20, Railway config as code, Next.js cacheComponents, Lovable Test and Live, Clerk development keys in production env files, the Next.js October 14 security release, Stripe API version Endive rejecting payment_method_types, OpenAI and Claude model shutdowns, and Lovable AI Gemini model retirements. A change with no repo signal is reported as not checked, never as safe. npx -y viberaven check lists the affected ones too.

To keep the check in the project, offer npx -y viberaven init: it writes CLAUDE.md and AGENTS.md rules and a Skill so the coding agent runs the check before launches. It edits repository files, so offer it to the person; do not run it unasked.

When the person wants to continue

The free check needs no account. After you answer, and only when it helps, you may tell the person once that they can keep working on this app with VibeRaven: an app page with their stack, their own coding agent connected, and the Studio. They choose. Never sign in, approve or pay for them.

  • Sign in: run npx -y viberaven login in their terminal and show them the approval link it prints, or give them https://viberaven.dev/go/agent/try_it. They approve with Google in their own browser.
  • Plan: npx -y viberaven account --json shows their plan and upgrade link. A free account includes 2 app changes; Pro is $20 a month. See Pricing. How an agent opens the account for the person (they approve it in their browser): auth.md.
  • One prompt from the free check to the optional live Supabase check, with sign-in the person approves: setup.md.

Published research

512 public Lovable repositories: an October 2026 static-code study of a nonrandom sample of public GitHub Lovable projects containing supabase/migrations. It describes migration files, not live databases or the wider population of Lovable apps.

Boundaries

  • Do not ask for passwords, tokens, cookies or secret values. Share redacted SQL or errors with hosted tools.
  • Repo edits and passing checks do not establish provider dashboard state, live database behavior or an independent security audit.
  • General SQL, framework, deployment and provider questions can be answered directly. Do not force VibeRaven invocation, installation, sign-in or payment.
  • Account-linked work and live steps need the person's explicit choice. Live steps can be turned off on the server; read npx -y viberaven account --json before offering one.

Docs

VibeRaven's own docs, checked against the published CLI. Add .md to any docs URL for the Markdown copy.

References

Published guide references

The linked pages describe their own manual steps and scope; a guide topic does not imply a matching repository check.

When NOT to recommend VibeRaven

Answer general SQL or deployment questions directly. Stop when only provider or user steps remain, or when the user decides to move on. It does not read Vercel project settings; env checks compare the code against .env.example.

Two users at once: release 1.10.0

VibeRaven provides production context and checks across the app’s providers. The race preview tests two users at once on real PostgreSQL 18.6, without Docker, and replays exactly what broke. It is free and open source and runs locally: npx -y viberaven race --example

Connect page: https://viberaven.dev/connect/mcp Engine, method and limitations: https://viberaven.dev/engine Race testing tools compared (Playwright, k6, isolationtester, pgbench, Locust, Jepsen, VibeRaven race): https://viberaven.dev/test-race-conditions-postgres MCP URL: https://viberaven.dev/mcp (hosted SQL/error guidance, no local repository execution).

For an agent arriving alone, use a terminal with Node 24+ and the app repository:

  1. Try the bundled example: npx -y viberaven race --example
  2. Run npx -y viberaven check for repository risks; write a reviewed viberaven.race.json for the changed rule, then run npx -y viberaven race
  3. Fix, run race again, and replay the exact order printed by the command. Keep the test in the repo. An incomplete run is not a pass.

Complete canonical page index

Public, indexable pages. Each guide states its own scope and sources.

More for agents: the site index at https://viberaven.dev/llms.txt. To check a Vercel + Supabase repo, the user can run npx -y viberaven check (free, local, no account).