VG

VibeRaven Guides

io.github.ohad6k/viberaven-guides

Read-only VibeRaven guides: explain a finding, search launch guides, get a Supabase checklist.

Yes, your AI can use this right now.Answered a live MCP handshake in 592 ms with no sign-in needed and exposes 3 tools.

Connect it

Settings → Connectors → Add custom connector
URL: https://viberaven.dev/mcp

3 tools, verified live

Pulled straight from the server with tools/list on 2026-10-17.
explain_findingread-only

Use this when the user asks what a VibeRaven finding id means, for example rls_disabled or env_var_drift, or pastes a finding from a VibeRaven 1.6.12 report. Returns what the rule detects in repository files, why it matters, how to fix it and what it does not check, quoted from viberaven.dev with a source link for each part. It does not read the user's repository, database or Vercel project. Known

search_guidesread-only

Use this when the user has a launch question about an AI-built app on Vercel + Supabase, such as Supabase RLS, env vars on Vercel, a Stripe webhook after deploy or a client handoff. Searches the launch guides published on viberaven.dev by keyword and returns up to 5 matches, each with its title, URL and the short answer from the page. It only searches those published pages: it does not browse the

launch_checklistread-only

Use this when the user wants a manual pre-launch checklist for a Lovable + Supabase app or a Next.js + Supabase app on Vercel. Returns the checklist published on viberaven.dev for that stack with its sources, and the one optional local VibeRaven step (`npx -y viberaven@1.6.12 check`), which is advice, not a gate. The items are manual checks the user does in their dashboards and code; this tool doe

Alternatives in Search & Research

Compare →
Try “Notion”, “Stripe”, “create invoice”, “browser”