What is vibealive?
vibealive is a MCP server by skullzarmy that find unused files and APIs in Next.js projects, with project analysis tools exposed over MCP. It is listed under Developer tools and has 8 GitHub stars.
| Type | Mcp server |
|---|---|
| Author | skullzarmy |
| Repository | skullzarmy/vibealive |
| Popularity | 8 GitHub stars |
| Category | Developer tools |
| Security | Low risk (96/100) |
| Rank | #1,873 of 4,418 MCP servers; #428 in Developer tools |
| License | MIT |
| Last commit | 2025-10-16 |
| Runs | Locally |
| Language | TypeScript |
| Platforms | macOS, Windows, Linux |
Is vibealive safe to install?
vibealive scores 96/100 on the MCPMods security check: Low risk. No checks raised a concern. It passed 5 of 6 checks.
MCP server results come from listing signals: who publishes it, where your data goes and what it can do. The code itself is not scanned yet.
| Check | Result |
|---|---|
| Community-built server | Note |
| Runs on your machine only | Pass |
| No credentials mentioned | Pass |
| Read-only by description | Pass |
| No code execution | Pass |
| Source on GitHub | Pass |
How do I install vibealive?
- Find the launch command. The README says how the server starts (npx, uvx, docker or a remote URL) and which API keys it needs.
https://github.com/skullzarmy/vibealive
- Add it to Claude Code. Replace the part after -- with the command from the README. Remote servers use --transport http with a URL.
claude mcp add vibealive -- <command from README> claude mcp add --transport http vibealive <server-url>
- Check it connected. This lists your MCP servers and their status.
claude mcp list
Or ask Claude to set it up
Paste this into Claude Code and it installs vibealive for you:
Add the "vibealive" MCP server from https://github.com/skullzarmy/vibealive to Claude Code. Read its README for the launch command and any API keys I need, run claude mcp add, then check that it connects.