MCP vs Plugins in Claude Code: Which Should You Use?
MCP servers and plugins solve overlapping problems in Claude Code. When to add a raw MCP server, when a plugin makes sense, and how to keep your context lean.
9 guides
MCP servers and plugins solve overlapping problems in Claude Code. When to add a raw MCP server, when a plugin makes sense, and how to keep your context lean.
Step-by-step guide to building a custom Claude Code subagent: write the frontmatter, a focused system prompt, scope tools tightly, test delegation, and iterate.
Plugins, skills, and MCP servers sit at different layers in Claude Code. What each is, how they nest, and a clear guide to which one you actually need.
Build your own Claude Code slash commands — markdown prompt files in .claude/commands, arguments, namespacing, and when a command beats a skill. With examples.
The built-in and custom Claude Code slash commands worth knowing in 2026 — context, cost, model switching, clear, plus custom commands you should build.
The Claude Code plugins actually worth checking in 2026, with install commands, source links, and why GitHub, Playwright, LSP, security, review, docs, and workflow plugins make the cut.
The most useful Claude Code subagent patterns for 2026: code reviewer, test writer, debugger, security auditor, docs writer, refactorer, and explorer — with tools and models.
OpenClaw and Claude Code both write code with AI, but they're built for different jobs. What each is best at, where they overlap, and how to choose — or use both.
Skills, MCP servers, and subagents solve different Claude Code problems. What each does, what it costs, and a clear decision guide for picking the right one.