One command, every editor.
Stop copy-pasting MCP configs across Cursor, Windsurf, and VS Code. Build a bundle once and apply it everywhere with a single npx command.
Open source · 24 IDE targets
Bundle your AI dev setup. Share it with one link.Bundle your AI
dev setup.
Share it with
one link.
Curate trusted MCP servers, reusable skills, and project rules. Generate one install command that travels cleanly across Cursor, Windsurf, VS Code, and the rest of your AI coding stack.
Antigravity
Claude Code
Cline CLI
CodeBuddy
Codex CLI
Cursor
DeepSeek-TUI
GitHub Copilot
Goose
Hermes
Kiro
OpenClaw
Roo Code
Windsurf
Antigravity
Claude Code
Cline CLI
CodeBuddy
Codex CLI
Cursor
DeepSeek-TUI
GitHub Copilot
Goose
Hermes
Kiro
OpenClaw
Roo Code
Windsurf
Live preview
github-mcp
repository context
typescript-strict
coding rules
$ npx vibebasket apply cj2k9xcopied
> Fetching trusted basket configuration...
> Writing MCP config for your selected targets...
> Context ready in Cursor, Windsurf, and VS Code.
Trusted discovery
Official registries and curated records, deduped into one catalog.
Local secrets
Sensitive values stay on your machine during apply.
Safe re-runs
Idempotent writes with backups so setup changes stay reversible.
Who is this for
Built for teams that move fast.
Whether you work solo or run a team, VibeBasket eliminates the friction of setting up AI coding tools one machine at a time.
Onboard in minutes, not hours.
Share a bundle URL with new hires. They run one command and get the exact same MCPs, skills, and rules as the rest of the team — no manual setup.
Curate trusted defaults.
Publish verified MCP servers and project rules your users can install with zero configuration. Control what goes into every environment without shipping config files.
How it works
Three steps from zero to configured.
No config files to copy. No IDE settings to hunt down. Just browse, bundle, and apply.
01
Browse trusted components
Catalog entries are pulled from curated data and trusted upstream sources, then normalized and deduplicated.
02
Assemble your basket
Select MCPs, skills, and rules directly from the builder. The UI keeps the basket state visible and reversible.
03
Apply with one command
Generate a single install command and apply the same setup across multiple editors without manual reconfiguration.
The Builder
Build your stack without reconfiguring everything by hand.
Browse trusted components, assemble your basket, and generate a single install command for the editors your team actually uses.
Trusted sourcesTrust-aware discovery24 items per page
Stop reconfiguring.
Start coding.
$ npx vibebasket apply <bundle-url>
Open source. Low ceremony. Built for teams that move fast.
FAQ
The questions that usually come up first.
Short answers for the trust, install, and self-hosting details people usually want before they standardize a workflow around VibeBasket.
Does VibeBasket ever receive my runtime API keys?
No. Bundle manifests do not carry end-user runtime secrets. When a selected MCP needs credentials, the CLI resolves that value locally during apply and writes it into the target tool's own config surface on your machine.
What happens if my IDE already has MCPs, skills, or rules configured?
VibeBasket merges into the target's supported config surface instead of pretending every file is blank. Existing blocks stay in place, VibeBasket-managed blocks remain idempotent, and unchanged MCP state is skipped so repeated applies do not keep rewriting the same target.
What do Verified, Official, and Community mean?
Verified means the item was curated by VibeBasket. Official means the upstream source exposed an explicit owner- or vendor-certified signal. Community is everything else that still passes the catalog normalization and deduplication pipeline.
Can I self-host VibeBasket for my team?
Yes. The web app, CLI, catalog sync, auth, admin tools, and backup flows all live in this repo. The default self-hosting shape is one VPS, one app instance, and one SQLite database with persistent storage and external backups.
Is re-running npx vibebasket apply safe?
That is the default expectation. The CLI is backup-aware, skips no-op MCP writes, and keeps target-specific install behavior idempotent so the same basket can be re-applied without turning every run into a destructive rewrite.
Can I use a bundle again later after I create it?
Yes. If you sign in, saved stacks and your account-level basket history let you come back to the same setup later. Even outside that flow, a generated bundle URL can still be re-used or shared as long as that bundle remains available on the hosted or self-hosted instance.