The Claude Code Resource Bible: 46 Tools Worth Knowing in 2026

TL;DR: 46 tools across the Claude Code ecosystem, organized by category (official, directories, MCP servers, skills, multiplexers, agent frameworks, automation), with picks for what's actually worth your time and what to skip. If you read one section, read the Recommended Starter Stack at the bottom.

Claude Code went from a CLI wrapper to a real ecosystem in under a year. The reference MCP server repo has eighty-five thousand stars. There are at least five different "awesome Claude skills" lists, and the smallest one has more entries than I can remember. Half a dozen terminal multiplexers exist purely to manage parallel Claude sessions. The ecosystem is real, and most of what's in it is noise.

This post is a curated map. I've installed, broken, and uninstalled most of these tools myself over the last several months. The goal is to save you the half-day of comparison-shopping that I already spent. Where I have an opinion, I'll give it. Where a tool is famous but mid, I'll say so. Where something genuinely changed how I work, it gets a Sublime pick.

What this post is not: a sponsored list, a roundup of every GitHub repo with "claude" in the name, or a vibes-based ranking. If a tool isn't here, it's either because the URL didn't verify, the project looked abandoned, or I couldn't articulate why anyone should install it. There are also a handful of tools you'd expect to see based on aggregated infographics floating around X (you know the ones) that turned out to be either misnamed or non-existent. I dropped them rather than dressing up a 404.

A note on count. The earlier draft of this list had fifty-five entries. After verification, ten of them either pointed at the wrong repo, didn't exist, or duplicated something now bundled into Claude Code itself. I'm not going to round up. The honest number is forty-six.

How to use this list

If you're new to Claude Code, start at the Official Anthropic section and don't skip ahead until your CLI is set up. If you've been running Claude Code for a few weeks and want integrations, jump to MCP Servers. If you're already managing multiple agents and the bottleneck is coordination, Agent Frameworks is where you'll spend your time.

A quick taxonomy, because the ecosystem invents new words for old things. MCP servers are network-accessible tool providers. They expose a database, an API, or a service over a standard protocol so Claude can call them. Skills are scoped instruction packs that ride alongside the system prompt. They're roughly "how to do X well, with the right files and commands." Plugins are bundles that may include skills, slash commands, hooks, and MCP wiring at once. Marketplaces are install registries for any of the above.

That's the whole conceptual model. If a tool description seems wordier than that, it's marketing.

One more rule of thumb: prefer fewer, sharper integrations over a kitchen-sink install. Each MCP server costs context window and adds another thing to debug when an agent goes sideways. The temptation, especially when reading a list like this, is to install everything that looks interesting. Don't. Pick the three or four that map to systems you actually use today. You can always add more later.

Official Anthropic

Start here. If you're new, the Anthropic docs and reference servers will save you a week of misinformation collected from screenshots on X.

Claude Code Docs. code.claude.com/docs is the source of truth for the CLI, slash commands, hooks, settings.json, and the plugin system. When a third-party tutorial contradicts the docs, trust the docs.

Anthropic Partner Network. Announced via the Partner Network post, this is Anthropic's formal program for systems integrators and consultancies. Useful if you're trying to land enterprise work on top of Claude. Less useful day-to-day.

Claude Certified Architect. Delivered through the Partner Portal under "Claude Certified Architect, Foundations." There's no standalone public page, so don't expect to enroll like it's AWS Cloud Practitioner. Your company has to be in the partner network.

Official MCP Servers Repo. github.com/modelcontextprotocol/servers hosts the seven actively-maintained reference servers (Everything, Fetch, Filesystem, Git, Memory, Sequential Thinking, Time). Older reference servers (Postgres, Slack, GitHub) have been moved to servers-archived and superseded by vendor-maintained versions. Always check the official org first before pulling a fork.

Sublime pick: The Official MCP Servers Repo. When you're putting MCPs in front of production code, "trustworthy provenance" is the only feature that matters.

Directories and mega lists

These are bookmark-worthy, not install-worthy. Use them to discover, then go install from the source.

Everything Claude Code (ecc.tools). ecc.tools is the product face of affaan-m/everything-claude-code, a community library of skills, agents, and slash commands. The site indexes 181 skills, 47 agents, and 79 commands at the time of writing. Good for browsing; quality varies.

awesome-claude-code (hesreallyhim). github.com/hesreallyhim/awesome-claude-code is the de-facto mega list, with 42.8k stars. It's currently mid-reorganization, so the structure may shift, but the link surface is the broadest you'll find.

Awesome MCP Servers (punkpeye). github.com/punkpeye/awesome-mcp-servers sits at 86.4k stars and is the canonical MCP discovery list. Categorized, well-maintained, and updated weekly.

50+ Best MCP Addons (claudefa.st). claudefa.st/blog/tools/mcp-extensions/best-addons is a more editorial take, last updated yesterday relative to publication. Useful when you want a human to have already culled the duds.

Sublime pick: Awesome MCP Servers (punkpeye). It's the only list I open more than once a month. Bookmark it; don't try to install everything in it.

MCP servers, the integration layer

This is where Claude Code stops being a chat that writes code and starts being an agent that touches your real systems. Pick servers based on the systems you actually use, not the ones that look cool in a demo.

Playwright MCP. github.com/microsoft/playwright-mcp is Microsoft's official browser automation server. 32.1k stars. If you want Claude to open a browser, click around, and verify the result, this is the one. The accessibility-tree mode is faster than screenshot mode for most testing.

claude mcp add playwright npx @playwright/mcp@latest

Firecrawl MCP. github.com/firecrawl/firecrawl-mcp-server is the official Firecrawl scraping and search server. If you've ever asked Claude to "go read this URL" and watched it hallucinate the contents, Firecrawl fixes that. You'll need a Firecrawl API key.

Supabase MCP. github.com/supabase-community/supabase-mcp is the community-maintained server (note the supabase-community/ namespace, not supabase/). Apache 2.0, actively released. Frame this in your head as a community project that Supabase blesses, not a first-party product.

crystaldba/postgres-mcp. The original modelcontextprotocol/servers Postgres reference is archived. github.com/crystaldba/postgres-mcp is the maintained replacement I'd grab today. It exposes schema introspection plus query tools without you having to write a custom server.

GitHub MCP. github.com/github/github-mcp-server is the official GitHub server, currently at v1.0.3. PRs, issues, code search, and file operations all in one place. If you're using Claude Code in a real repo, install this immediately.

Context7. github.com/upstash/context7 is Upstash's live-docs server. 54.7k stars, dozens of releases, and the only sane answer to "Claude is using a deprecated API from 2023." It pulls current library docs at request time. The single biggest unforced-error eliminator I've installed this year.

Sentry MCP. github.com/getsentry/sentry-mcp is the official Sentry server, also hosted at mcp.sentry.dev. Wire this up and Claude can pull live errors, trace events, and triage issues. For production debugging it's a step-change.

Dokploy MCP. github.com/Dokploy/mcp is Dokploy's official package. If you self-host with Dokploy, this gives Claude direct access to your deployment surface.

Slack MCP. The official reference at npmjs.com/package/@modelcontextprotocol/server-slack was archived from the main MCP repo. Slack also runs an official remote server documented at docs.slack.dev/ai/slack-mcp-server. For new projects, use the remote.

Notion MCP. github.com/makenotion/notion-mcp-server is the official local server, currently v2.0.0. Notion is migrating users to a remote MCP, and the local server may eventually sunset. If you're starting fresh, plan for the remote.

Figma MCP. Setup instructions live at help.figma.com. The recommended path is the remote at mcp.figma.com, not a local install. For implementing a designer's mockup in code, this is the cleanest handoff I've seen.

Linear MCP. linear.app/docs/mcp documents the official remote MCP at https://mcp.linear.app/mcp, OAuth 2.1. There's no public source repo; it's a hosted service. Pair it with the GitHub MCP and "ship the linear ticket" becomes one prompt. Add it like this:

claude mcp add --transport http linear https://mcp.linear.app/mcp

A practical note on layering MCPs: I keep my most-used four (GitHub, Context7, Sentry, Linear) in user-scope ~/.claude.json, and project-specific ones (Playwright for a frontend repo, Postgres for a service repo) in the project's .mcp.json. That way I don't pay the context cost of Playwright on a Go service that has nothing to render.

Sublime pick: Context7. It kills the stale-docs problem instantly and you don't have to remember to mention it. Once it's installed, Claude reaches for it automatically when a library version matters.

Honorable mention: Sentry MCP. The first time Claude pulled a live trace and proposed the fix without me copy-pasting an error, I knew this category was going to swallow my error-investigation workflow.

Articles and blog posts worth reading

Quick annotations, not deep dives.

10 CLI Tools for AI Coding (Starmorph) by Dylan Boudro. Solid intro to the broader CLI agent space if you're trying to compare Claude Code to Codex, Aider, and friends. Useful if you're picking a primary CLI rather than committing to Claude Code, or if you need to argue with a teammate who's already committed to a different one.

Best MCP Servers for Devs (Firecrawl). The 2026 edition. Short, opinionated, sensible picks. Some overlap with this post; their angle is more "what does Firecrawl recommend pairing with Firecrawl." Worth a read for a second opinion on the same canon.

Claude Code MCP Servers: How to Connect, Configure, and Use Them (Builder.io). The actual config walkthrough I'd hand a teammate who's never wired up an MCP. Covers .mcp.json, scope, transports, and OAuth flows. March 2026, still accurate.

Agentmaxxing (Vibecoding). Provocative essay on running many agents in parallel. Read it for the framing, not the prescriptions. The author leans further into autonomy than I do, but the piece is the cleanest articulation I've seen of why the next bottleneck for solo devs is coordination, not capability.

Skills and extensions

Skills are the muscle memory of Claude Code. A good skill is the difference between Claude flailing and Claude executing a workflow you'd recognize as "how a senior would do it."

Superpowers (obra). github.com/obra/superpowers by Jesse Vincent. v5.1.0, very large following. Brainstorm, plan, and execute slash commands plus twenty-plus battle-tested skills covering TDD, debugging, code review, and more. It works across Claude Code, Codex, Gemini CLI, and OpenCode. If you install nothing else from this section, install this.

Taste Skill. tasteskill.dev (source: github.com/Leonxlnx/taste-skill). An anti-slop frontend skill. The pitch: Claude generates UI that doesn't immediately read as AI-generated. Mileage varies by stack, but the underlying instructions are worth reading even if you don't install the skill verbatim.

Chrome CDP. github.com/pasky/chrome-cdp-skill wires Claude into a Chrome DevTools Protocol session. Lighter-weight than Playwright when you just need to inspect a running page. Alternatives exist (pengelbrecht's variant, the obra/superpowers-chrome bundle), but pasky's is the one I've reached for.

Delivery Lifecycle. github.com/levnikolaevich/claude-code-skills is a full Agile-pipeline plugin suite. Backlog grooming, sprint planning, release notes, the whole choreography. If your team genuinely runs Agile, this maps to that ritual cleanly.

Codex Settings. github.com/fcakyon/claude-codex-settings is a personal Claude Code plus Codex setup pack. Worth a read even if you don't adopt it: it shows what a thoughtful settings.json plus skills layout looks like.

CLUI. github.com/lcoutodemos/clui-cc is a macOS-only TUI overlay for Claude Code. Niche but lovely if you live in the terminal and want a slightly nicer surface than the raw CLI.

Clawd Cursor. clawdcursor.com, v0.8.8. Desktop-control via MCP. It lets Claude move your mouse and read your screen. Powerful and slightly unsettling. Worth experimenting with on a sandbox machine before pointing it at your real one. (Note: don't confuse this with rullerzhou-afk/clawd-on-desk, which is an unrelated pixel-art desktop pet.)

Sublime pick: Superpowers. Install it today, thank me later. The brainstorm/plan/execute trio alone is worth the install. Once you have the muscle memory of /brainstorm before any non-trivial change, you won't go back.

A note on installation hygiene for skills: read the SKILL.md before you install. A skill is essentially "extra system prompt the agent will follow." Treat it with the same scrutiny you'd give a dependency in production code. If the description is vague or the maintainer doesn't explain the intent, that's a signal to skip.

Terminal multiplexers

When one Claude session isn't enough. The whole category exists because git worktrees plus tmux is awkward, and several teams independently decided to fix it.

cmux. cmux.com is a native macOS app, Swift/AppKit, launched February 2026. It manages parallel Claude sessions with a real GUI. If you're on a Mac and don't want to live in tmux, this is the most polished option I've used.

claude-squad. github.com/smtg-ai/claude-squad, v1.0.17. Tmux plus git worktrees, but the rough edges are sanded down. Spin up N agents on N branches, watch them run, merge what you like. I've been running it for several months and it's the tool I open first when I want to fan out work.

dmux. github.com/standardagents/dmux (also at dmux.ai). Cross-agent: it manages sessions for Claude Code, Codex, OpenCode, Cline, Gemini CLI, and more. Pick this if you intentionally use multiple agent CLIs and want one harness over all of them.

mux (coder/mux). github.com/coder/mux, v0.24.0. From the Coder team, so it leans toward remote dev environments. Active, well-maintained, but unless you're already a Coder shop, the others are easier starts.

Multiplexer comparison

	cmux	claude-squad	tmux (raw)
Setup time	60 seconds (download .dmg, open)	5 minutes (brew install, plus tmux + git worktrees)	0 (already installed)
Platform	macOS only	macOS, Linux	macOS, Linux, BSD, anywhere
Best for	Mac devs who want a GUI for parallel agents	Terminal-native devs running 3-10 parallel sessions on branches	Engineers who already have a tmux config they love
Skip if	You're on Linux or you actually like the terminal	You don't use git worktrees or you hate tmux	You don't already know tmux; the learning curve isn't worth it just for this

Sublime pick: claude-squad if you live in the terminal, cmux if you're on a Mac and want a real window manager. Don't bother with raw tmux unless you already love tmux.

A workflow tip that pays off across all three: pair the multiplexer with git worktrees, not branches. Each agent gets its own checkout, no git stash dance, no fighting over uncommitted changes. claude-squad does this automatically. cmux makes it a one-click affair. Raw tmux requires you to wire it up yourself, which is most of why the dedicated tools exist.

Agent frameworks

When you're past one agent and need real coordination. Several of these projects use the word "swarm." Some of them mean it; most don't.

ClawTeam. github.com/HKUDS/ClawTeam is HKUDS's multi-agent swarm coordinator. Academic provenance, which means the code is more interesting to read than to deploy, but the patterns are educational.

CLI-Anything. github.com/HKUDS/CLI-Anything, also HKUDS. The pitch: generate a CLI for any app. As an experiment in agent-as-codegen it's fun. As a daily driver, treat it as alpha.

Autoresearch. github.com/uditgoenka/autoresearch implements Karpathy's autonomous-loop pattern as a skill. If you want Claude to grind on an open-ended research task without a human in the loop, this is the cleanest minimal version I've seen.

Hermes Agent. github.com/NousResearch/hermes-agent by Nous Research. Integrates with Claude Code via a /cc command. If you're already in the Nous ecosystem (or want to be), this is the bridge.

CopilotKit. github.com/CopilotKit/CopilotKit, v1.57.0, 30.9k stars. Less of a Claude-Code-specific tool and more an agent UI framework. Useful if you're shipping agent features inside a product, not just driving Claude from your terminal.

Ruflo. github.com/ruvnet/ruflo (formerly Claude Flow, rebranded around January 2026). This is the multi-agent orchestration layer I actually reach for. Persistent memory, swarm coordination, and a deep MCP surface that exposes everything from observability to security audits. I dispatched a Ruflo swarm earlier today through MCP and the agents coordinated cleanly without the prompt-engineering pep talk I'd usually need. It deserves more than a paragraph, which is why we wrote the Ruflo deep dive as a companion to this post.

Sublime pick: Ruflo. It's the only framework in this list I'd commit to before shipping a project. Read our Ruflo breakdown for the install, the tradeoffs, and the failure modes.

Automation and infra

Shipping agents to production. The tools here are less glamorous than the framework section but more important if you're running anything past a hobby project.

n8n-as-code. github.com/EtienneLescot/n8n-as-code brings n8n's 537 nodes and seven thousand templates under Claude Code as code. If you've been writing automation glue by hand and feel the urge to graduate, this is the bridge.

Cloak Browser. github.com/CloakHQ/CloakBrowser is a stealth Chromium project (not Claude-Code-specific). It integrates with Claude Code via the separate overtimepog/CloakMCP server. Worth knowing about if your agent work runs into bot-detection walls; not worth installing speculatively.

OpenLogs. github.com/charlietlamb/openlogs. I'm including this with a caveat: it's a small, single-contributor project. The shape is right (open observability for AI agents), but evaluate for yourself before betting infrastructure on it. Treat it as a starting point, not a finished platform.

Vercel Chat SDK. github.com/vercel/ai-chatbot, 20.3k stars. The Next.js AI Chatbot template, commonly called the "Chat SDK." Best path I know for shipping a chat-driven AI feature in a real product without writing the harness yourself.

Self-hosted infra (Happy Engineering). happy.engineering plus github.com/slopus/happy. Mobile and web client for Claude Code with a self-hostable relay. If you want to drive Claude Code from your phone without sending traffic through someone else's server, this is the path.

Sublime pick: Vercel Chat SDK if you're shipping AI features fast. For observability, OpenLogs is promising but I'd run it side-by-side with whatever you already use until you've stress-tested it.

The under-discussed move in this section is Happy Engineering's self-hosted relay. Most agent infrastructure assumes you're driving from a laptop and never need to step away. If you want to dispatch work from your phone (kick off a long task at the gym, check on a stuck agent at dinner), the relay model is the only realistic way to do that without piping all your traffic through someone else's hosted control plane. Whether you self-host Happy or roll your own, it's worth thinking about the architecture before you need it.

Sublime's recommended starter stack

If you only install five things, install these. They cover the highest-leverage ground for a working developer who's already past "hello world" with Claude Code.

1. Superpowers (skill bundle). Brainstorm, plan, execute, plus the canonical TDD and debugging skills.

claude plugin install obra/superpowers

2. claude-squad (parallel sessions). Fan out across worktrees without rebuilding tmux from scratch.

brew install smtg-ai/tap/claude-squad

3. Context7 (live docs MCP). Stop watching Claude write code against last year's API.

claude mcp add context7 -- npx -y @upstash/context7-mcp

4. Sentry MCP (production debugging). Wire your error feed into the model that's writing the fix.

claude mcp add --transport http sentry https://mcp.sentry.dev/mcp

5. Ruflo (when you're ready to scale). When one agent isn't enough and you want orchestration with persistent memory rather than a manual claude-squad round-robin. The full install and configuration walkthrough is in the Ruflo deep dive.

npm install -g ruflo

These five cover the long tail. Skills give you workflow muscle memory, claude-squad gives you parallelism, Context7 stops the hallucination of stale APIs, Sentry MCP gives you a feedback loop with production, and Ruflo is what you reach for when the workflow itself needs to become an agent.

What we left off and why

Honest cuts, in case you saw a tool elsewhere and wondered why it's not here:

The original outline included a generic "PostgreSQL MCP" entry. The original reference server is archived. I swapped in crystaldba/postgres-mcp instead because at least one Postgres entry deserves to be in the bible, and that's the maintained one I'd actually point a friend at.

A handful of "awesome" lists got cut because they share a name with four or five other repos. If a list isn't unambiguously the canonical thing, including it just creates more discovery work for you.

A few agent frameworks were dropped for not having a verifiable canonical URL. If I can't link to the project root with confidence, I can't recommend installing it.

"Loop" appeared in the original outline as a third-party skill. The /loop command is now bundled in Claude Code itself, documented at code.claude.com/docs/en/scheduled-tasks. You already have it.

A bundle of nicholasoxford/* MCP servers were referenced in source material I was working from. They don't exist. The actual Anthropic-maintained reference servers are at modelcontextprotocol/servers. When you see an MCP install command from a screenshot, check the org before you run it.

What's coming next

This is Post 1. Post 2 is the long-form companion: the Ruflo deep dive, where we go past the recommendation and into the install, the architecture, the orchestration model, and the specific failure modes I've hit running it on real work.

Sublime Coding is freshly pivoted toward practical, opinionated coverage of AI coding tools and developer workflows. If that's the kind of thing you want in your inbox without filler, the newsletter signup is below. We don't run sponsored picks.

If a tool I've missed deserves a spot in the next revision of this list, drop it in the comments with a one-sentence pitch for why. Especially interested in things you've actually run for more than a week.