You don't use sift9. Your coding agent does.
Right now, when your agent plans a task, it guesses which
tools to use — or you go find them yourself. sift9 closes
that gap. The agent sends its plan, and sift9 returns the
skills, plugins, MCP servers, hooks and rules that make the
job faster and more reliable. 200,000+ curated assets,
always updated, delivered in one call.
No account. No key. Install once, forget it's there.
INSTALL 🚀
npm exec @sift9/setup
Auto-detects Claude Code, Cursor, VS Code, Windsurf, Claude
Desktop, and Codex. Writes the MCP config to the right file.
To set up a specific tool:
npm exec @sift9/setup -- --cursor
npm exec @sift9/setup -- --vs-code
npm exec @sift9/setup -- --windsurf
npm exec @sift9/setup -- --claude-desktop
npm exec @sift9/setup -- --codex
MCP endpoint: https://sift9.xyz/mcp
WITHOUT SIFT9 ❌
😤 Your agent picks the wrong MCP server for the job.
🔁 It writes code from scratch that a skill already solves.
🗑️ It wastes tokens re-discovering tools it should know about.
📚 You collect skills yourself — now the agent's context is
full of assets it doesn't need for this task.
🔍 Even in the age of AI, you still end up searching Google
for the right plugin before you start building.
WITH SIFT9 ✅
Install once. Everything else happens under the hood.
🎯 Your agent plans. sift9 finds the right assets for that
specific plan — ranked, curated, scoped to the task.
📦 Skills, plugins, MCP servers, subagents, hooks, rules,
workflow templates, and permission policies.
🌍 200,000+ assets from across the digital world, always
updated.
🙌 You do nothing. The agent calls sift9, gets back a
manifest, picks what it needs, and continues.
HOW IT WORKS ⚙️
1️⃣ Your agent has a plan.
2️⃣ It calls sift9 with the plan.
3️⃣ sift9 returns a ranked manifest of matching assets.
4️⃣ The agent picks what it needs.
5️⃣ The agent installs and continues building.
🔒 sift9 suggests skills, plug-ins, MCP and other
artifacts. Nothing runs server-side.