VibeRaven

Connect the VibeRaven MCP server

By Ohad Krispin, founder of VibeRaven · LinkedIn

The hosted server at `https://viberaven.dev/mcp` gives any agent seven read-only tools, such as checking the Supabase migrations of a public GitHub repo, with no account and no key. It cannot see your local files; for repository tools, run the local `@viberaven/mcp` server.

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

That is Claude Code. Other clients are below. Or ask your coding agent to "add the viberaven MCP server".

Add the hosted server

The URL is the same in every client. It needs no authentication; pick none if the client asks.

Claude Code

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

Codex

codex mcp add viberaven --url https://viberaven.dev/mcp

Cursor

Add it to .cursor/mcp.json in the project, or ~/.cursor/mcp.json for every project.

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

ChatGPT

With developer mode on, create a custom app (a connector) with the URL https://viberaven.dev/mcp and no authentication. Claude custom connectors take the same URL.

Gemini CLI

gemini mcp add --transport http viberaven https://viberaven.dev/mcp

Hosted tools

All seven are read-only. They answer from the guides on viberaven.dev, from dated provider notes with official sources, or from the SQL you point them at.

check_github_repo
Takes a public GitHub repo, https://github.com/owner/name or owner/name, and an optional ref. Reads its supabase/migrations/*.sql at one commit, up to 50 files and 200 KB, and runs the same SQL rules. Each finding links to its line on GitHub, and the result links a report page. Public repos only; nothing is stored.
check_supabase_migrations
Runs the CLI's SQL rules on migration text you pass in: tables without RLS, using (true) policies, security definer functions and Data API grants. The text is not stored.
explain_finding
Explains a finding id such as rls_disabled: what it detects, how to fix it and what it does not check.
search_guides
Searches the guides by keyword or by exact error text.
recent_provider_changes
Dated changes for Supabase, Vercel, Next.js, Clerk, Lovable and Railway, with the error each one causes.
provider_playbook
The setup steps, gotchas and checks for a provider before you build on it. Today: supabase.
launch_checklist
The manual pre-launch checklist for a Lovable + Supabase or a Next.js + Supabase app.

No terminal and no agent? Open viberaven.dev/check and paste a public GitHub repo: it runs check_github_repo in the browser and shows the report.

Run the local server

The local server runs on your computer and reads the project it is started in. Version 1.7.8 lists 29 tools, among them viberaven_check_readiness, viberaven_heal_plan and viberaven_heal_apply.

{
  "mcpServers": {
    "viberaven-local": { "command": "npx", "args": ["-y", "@viberaven/mcp@1.7.8"] }
  }
}

Both servers call themselves VibeRaven. Give them different names in your config, so you and your agent know which one can see the repository.

Limits

  • The hosted server sees only what you pass it, or the migration files of a public repo you name. A SQL result covers that text, not your live database.
  • It logs the method, tool name, client name and version and success or error. No arguments, results, prompts or IP addresses.
  • Do not paste secrets into a tool call. Redact keys and connection strings first.

Next

Checked

Checked on November 3, 2026: a live tools/list on https://viberaven.dev/mcp returned seven read-only tools, and @viberaven/mcp@1.7.8 returned 29 tools over stdio.

All VibeRaven docs