Main
A useful way to consume directories like this:
- Create a “team baseline” file listing your chosen servers/skills and the exact configs you use.
- Prefer entries with concrete install commands and environment variable documentation.
- When you adopt a server, write a short internal runbook: what tools it exposes and what data it touches.
README excerpt (verbatim)
An awesome Claude directory for agents, MCP servers, skills, hooks, commands, tools, and AI workflows. 384+ file-backed entries covering agents, MCP servers, tools, skills, hooks, rules, commands, guides, collections, and statuslines.
Website • Browse • Jobs • Submit • API • MCP • Discussions
Feeds • RSS • Atom • LLM export • Raycast • MCP endpoint • Claim/update
What is HeyClaude?
HeyClaude is an unofficial, community-built awesome Claude directory and browsable registry.
- No paid database required for the public site
- Content lives in-repo as files
- Community submissions can flow through GitHub
- Jobs are reviewed and published by maintainers
- The site doubles as an awesome-list and a browsable directory
At a Glance
| Section | Entries | Scope |
|---|---|---|
| Agents | 39 | Specialized Claude agents and expert roles. |
| MCP Servers | 48 | Model Context Protocol servers and integrations. |
| Tools | 52 | Apps, developer tools, services, and products for Claude-native builders. |
| Skills | 68 | Installable skill packs and reusable capabilities. |
| Rules | 29 | Prompt guardrails, project rules, and operating constraints. |
| Commands | 27 | Slash commands and reusable command prompts. |
| Hooks | 66 | Claude Code hook configs and automation helpers. |
FAQ
Q: Is everything here official? A: No—it's a community directory; validate each linked repo's license and safety posture.
Q: How do I avoid duplicates? A: Use your own baseline list and keep only one server per capability until you have evidence to add more.
Q: How do I keep it updated? A: Track upstream with git and periodically review new entries via PRs.