I kept running into the same problem with Claude Code plugins: discovery is scattered across GitHub, Discord threads, blog posts, and random repos.
Even when I found something useful, it was hard to answer the questions I actually cared about:
Is this maintained?
What does it install?
Does it use hooks or MCP servers?
Are people actually using it?
Is there a quick way to install it?
So I built
https://claudepluginhub.com/
It auto-discovers plugins from GitHub every few hours. If a repo has a valid .claude-plugin/plugin.json, it can show up automatically. No manual submissions or approval queue.
A few things I wanted the site to do beyond being a basic directory:
Show trust signals like GitHub stars, maintenance score, install counts, and public repo usage
Warn clearly when a plugin includes hooks or MCP servers
Index all Claude Code component types, including commands, agents, skills, hooks, MCP servers, LSP servers, output styles, themes, and monitors
Support semantic search, so you can search by what you want the plugin to do instead of needing the exact keyword
Generate install commands / marketplace endpoints that can be pasted into Claude Code
Give plugin authors a way to claim listings, get verified, view analytics, and create custom marketplaces
Browsing and basic search are free. There is a small premium tier for power search, advanced analytics, and some extra author tools, but the core directory is open.
If you maintain a Claude Code plugin, it may already be listed. You can search for it and claim the listing from the plugin page.
I’d be interested in feedback from people using Claude Code plugins: what trust/safety signals would actually help you decide whether to install something?
submitted by
/u/Heiberik
Originally posted by u/Heiberik on r/ClaudeCode
You must log in or # to comment.