VibeBasket

Bundle trusted MCP servers, agent skills, and project rules into one shareable install command. Apply across 30 AI IDEs and CLI tools with a single link.
Potencialize seu agente
Instalação do publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
Ainda não há uma versão empacotada no registro. Siga o README do repositório.
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirVibeBasket helps you stop configuring MCP servers, skills, and rules one tool at a time.
Browse a trusted catalog, select what you want, and generate one npx command that applies the bundle across the AI IDEs and CLI tools you actually use.
npx vibebasket apply https://vibebasket.dev/api/bundle/cj2k9x
Start here:
22 supported targets auto-install Skills. 9 supported targets auto-install Rules. All MCP-capable targets auto-install MCP servers.
Catalog scope:
skills.sh corpus plus curated verified overridesapply — Install bundles from URLs or local files (--force, --scope, --dry-run, --no-verify)list — Scan all 30 IDEs for installed MCPs, skills, and rulessearch — Search the catalog from terminaldoctor — Diagnose IDE configurations across all targetsinit — Scaffold a VibeBasket projectrollback — Restore from timestamped backups (run from the target project root for project-scoped configs)mcp serve — Expose a local stdio MCP server so AI IDEs can search catalog items, fetch target-native MCP config snippets, plan installs, apply bundles, inspect backups, and save local stacks without leaving the IDENEXT_PUBLIC_* allowlist enforcementChoose the path that matches what you are trying to do:
npx vibebasket apply ... command, and run it locallynpx vibebasket ... or inspect the package page at npmjs.com/package/vibebasketIf you deploy with Coolify, prefer Dockerfile mode. Build Pack mode is also supported via the repo-level nixpacks.toml.
git clone https://github.com/mhmtayberk/VibeBasket.git
cd VibeBasket
cp .env.example .env
# fill at least AUTH_SECRET and NEXTAUTH_URL before booting production mode
docker compose up -d
After first boot, either wait for the initial catalog bootstrap or run docker compose exec web node scripts/catalog-sync.mjs, then verify /api/catalog/status.
git clone https://github.com/mhmtayberk/VibeBasket.git
cd VibeBasket
cp .env.example .env
pnpm install
pnpm dev
After first boot, either wait for the initial catalog bootstrap or run pnpm catalog:sync, then verify /api/catalog/status.
Open http://localhost:3000.
The official package name is vibebasket.
# Install from bundle URL
npx vibebasket apply https://vibebasket.dev/api/bundle/cj2k9x
# Install from a local bundle file
npx vibebasket apply ./bundle.json
# Options
npx vibebasket apply <url> --scope project --dry-run --force
# List installed configs
npx vibebasket list
# Search catalog
npx vibebasket search postgresql
# Environment check
npx vibebasket doctor
# Scaffold project
npx vibebasket init
# Restore from backup
npx vibebasket rollback
# Run the local MCP server for AI IDE integrations
npx vibebasket mcp serve
Example local bundle file:
{
"schemaVersion": "0.1",
"name": "Local example",
"scope": "user",
"targets": ["cursor"],
"mcps": [],
"skills": [],
"rules": [],
"workflowPacks": []
}
VibeBasket also exposes a local stdio MCP server through the published CLI:
npx vibebasket mcp serve
Current phase-1 MCP capabilities:
The hosted docs hub mirrors this surface with target-selectable native snippet previews so users can inspect representative JSON, YAML, and TOML merge fragments before wiring the local server into an IDE.
Current non-goal in this phase:
When the target adapter detects that the generated MCP config is identical to the current on-disk config, vibebasket apply reports a no-op for that target and does not create a redundant backup snapshot.
Most deployments only need a small subset to get started:
See .env.example for the complete environment surface and backup backend variables.
OAuth note: provider buttons appear only when the provider is both enabled and fully configured.
VibeBasket is currently optimized for single-node deployments: one app instance, one SQLite database, and no Redis or shared cache by default.
Start here:
Operational notes:
/api/health is safe for container and orchestration health checks/api/catalog/status exposes catalog freshness and the latest sync resultpnpm catalog:sync:strict is available as a pre-launch validation commandpnpm verify:ciMain parts of the repo:
packages/core
Shared schemas, SQLite bootstrap, and database accesspackages/adapters
30 IDE and CLI adapters with target-specific install logicpackages/registry
Catalog sync from the official MCP Registry, skills.sh, and curated verified dataapps/web
Next.js web app, APIs, auth flows, saved stacks, and admin surfacesapps/cli
Local installer CLI for apply, list, search, doctor, init, and rollbackcharts/vibebasket
Helm chart for single-replica self-hosted deploymentsKey patterns:
For more detail:
Repository guardrails:
gitleaks.NEXT_PUBLIC_* usage, and only reviewed allowlisted names are accepted.Report vulnerabilities via GitHub Security Advisories. See SECURITY.md for the full threat model.
MIT
Bundle trusted MCP servers, agent skills, and project rules into one shareable install flow across AI IDEs.
Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
VibeBasket roda localmente via stdio.
Última verificação: 2026-10-28. Bundle trusted MCP servers, agent skills, and project rules into one shareable install flow across AI IDEs.