Install ModCrew
Mod the web with your own Claude Code. Free forever — you bring the AI.
Install the Chrome extension
- Download .zip and unzip it.
-
Open
chrome://extensions - Top-right: enable Developer mode
- Top-left: click Load unpacked → pick the unzipped folder
The ModCrew icon should appear in your Chrome toolbar. If it's hidden, click the puzzle-piece icon and pin ModCrew.
Click the ModCrew icon → Copy the command
The popup shows your personal MCP URL. Click Copy:
claude mcp add modcrew --transport http https://api.modcrew.dev/mcp/<your-token>
Your token is generated locally by the extension on first run — never by this website. The URL in the popup is always the source of truth.
Paste into Claude Code
In any terminal where Claude Code runs, paste the command and hit Enter.
What makes ModCrew different
Transfer style between tabs
"Make github.com look like the Vercel dashboard I have open in my other tab."
Tweeks generates from a single page. ModCrew's Claude can snapshot one tab, generate CSS, apply to another.
Use your design system
"Match the colors in ~/myproject/tailwind.config.js for this site."
Claude Code already reads your filesystem. Browser-only AI extensions can't.
Style from a screenshot
Drag a PNG into your terminal: "make this page look like the screenshot."
Claude Opus is multimodal. ModCrew passes the styling through.
Self-checking loop
Claude injects CSS, screenshots, sees if it worked, adjusts — all without you having to say "try again."
One-shot AI generators can't iterate. Agent-loop tools can.
You already pay for the AI
You bring your Claude Code subscription. ModCrew doesn't add a tier or charge for LLM tokens. Ever.
Other AI extensions sell tiers because they pay for tokens. ModCrew can't burn a cent of your money on AI.
Compose with other MCPs
GitHub PR diff → modcrew applies the design ask live. Figma export → modcrew uses the tokens. Linear ticket → modcrew implements the UI.
Closed AI extensions can't pull from your other tools. MCP can.