All servers · Databases · Build & deploy

VibeRaven Guides

io.github.ohad6k/viberaven-guides · v1.0.0

Measured by MCP Station

Description written by the publisher, not verified

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

Connect

claude mcp add --transport http viberaven-guides https://viberaven.dev/mcp

{
  "mcpServers": {
    "viberaven-guides": {
      "url": "https://viberaven.dev/mcp"
    }
  }
}

Tools as reported by the server

• explain_finding
  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
• search_guides
  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
• launch_checklist
  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 advic
• check_supabase_migrations
  Use this when the user wants their Supabase migrations checked for RLS gaps before launch, asks whether the Supabase October 30, 2026 Data API grants change will break their tables, or asks whether a security definer function is callable by anon or by signed-in users. Pass the SQL text: sql for one

Tool changes

• 2026-10-24: explain_finding, search_guides, launch_checklist, check_supabase_migrations
• 2026-10-16: explain_finding, search_guides, launch_checklist

Website · JSON · Text for agents · Registry updated 2026-09-30