Claude Skills vs MCP: Which One Do You Need? (2026)
Use a Claude skill to teach Claude a workflow or convention; use MCP to give Claude live access to an external system like a database or browser. Skills load instructions on demand, MCP holds a running connection. Developers often combine both: the find-skills skill alone has 2,438,642 installs (skills.sh registry, July 2026).
By Skillselion, an Ellelion LLC publication · Updated July 11, 2026 · 4 min read · Stats verified against the live catalog
Use a skill when you want Claude to follow a workflow, convention, or methodology it would not reliably improvise: a skill is a packaged folder of instructions (a SKILL.md plus optional scripts and references) that Claude loads into context on demand. Use MCP (Model Context Protocol) when Claude needs live access to an external system: a database, a browser, a SaaS API. The shortest rule that holds up in practice: skills change how Claude works, MCP changes what Claude can reach.
Key takeaways
- A skill = instructions loaded on demand. An MCP server = a running process exposing callable tools over a protocol.
- Teaching a convention, checklist, or workflow -> skill. Querying or mutating a live external system -> MCP.
- Skills cost almost nothing at rest (name + description only). Every connected MCP server injects its full tool schemas into context on every request.
- The two combine well: a skill can teach Claude how to use an MCP server effectively.
- Install signal is real: find-skills has 2,438,642 installs and Anthropic's own mcp-builder skill has 87,902 installs (skills.sh registry, July 2026).
What is a Claude skill?
A skill is a directory containing a SKILL.md file: YAML frontmatter (name, description) plus markdown instructions, optionally bundled with scripts, templates, and reference docs. Claude reads only the name and description at startup; when your task matches, it pulls the full instructions into context and follows them. Nothing runs in the background. A skill cannot reach a system Claude could not already reach through its normal tools - it makes Claude better at tasks, not capable of new connections. Full breakdown in What are Claude Code skills?
What is MCP?
MCP is an open protocol (introduced by Anthropic in 2024) for connecting AI clients to external systems. An MCP server is a separate process - launched via stdio or reached over HTTP - that advertises tools, resources, and prompts. When Claude calls a tool, the server executes real code against the real system: run a SQL query, drive a browser, hit an internal API. That live connection is the whole point, and it is something no SKILL.md can do. Primer here: What is MCP?
Which should you use? A decision table
| You want Claude to... | Reach for |
|---|---|
| Follow your team's coding conventions | Skill |
| Query or migrate a production database | MCP |
| Run a structured code-review or debugging checklist | Skill |
| Automate a browser (test, scrape, screenshot) | Often both: MCP drives the browser, a skill teaches the workflow |
| Call a third-party SaaS API (Slack, Linear, Stripe) | MCP |
| Scaffold projects with your preferred stack and structure | Skill |
| Pull live, version-accurate library docs | MCP |
| Enforce commit-message or PR standards | Skill |
The pattern: if the job is knowledge and process, it is a skill. If the job is access, it is MCP. If the access needs judgment to use well, it is both.
When should you combine them?
The strongest setups pair a connection with the playbook for using it:
- Browser work. The Chrome DevTools MCP server gives Claude a real browser; the chrome-devtools skill from the same repo (4,923 installs, skills.sh registry, July 2026) teaches Claude when and how to use those tools for debugging and performance work. Microsoft ships the same idea CLI-first: playwright-cli (82,449 installs) is a skill that drives Playwright without holding an MCP connection at all.
- Docs lookup. context7-mcp (3,096 installs) is a skill whose job is to set up and use the Context7 MCP server correctly.
- Configuration itself. Anthropic's mcp integration skill (12,060 installs) exists purely to help Claude configure and bundle MCP servers - a skill about MCP.
- Building servers. When you need a server that does not exist, mcp-builder (87,902 installs) walks Claude through writing a production-quality one.
How do you install each?
Skills: drop the folder into ~/.claude/skills/ (personal) or .claude/skills/ (per project), or let an installer do it - npx skills add <owner>/<repo> handles fetch and placement. No process, no restart, no config file. Step-by-step: How to install a Claude skill.
MCP servers: register the server so Claude can launch or reach it, for example claude mcp add supabase -- npx -y @supabase/mcp-server-supabase, or add an entry to .mcp.json for project scope. You manage credentials (API keys, connection strings), the server runs as a process, and it must be reachable every session.
Install friction is the quiet decider here: a skill is a file copy, an MCP server is infrastructure.
What do they cost in context?
- Skills are lazy. At rest, each costs only its name and description - roughly a sentence of tokens. The full SKILL.md loads only when triggered, then competes for context like any other document.
- MCP is eager. Every connected server's tool schemas are serialized into every request, whether or not you use them. A server exposing 20 tools with JSON Schema parameters can eat thousands of tokens before you type a word, and each server is also a live process to keep healthy.
Practical consequence: accumulate skills freely, but audit your MCP servers. Three servers you actually use beat ten you might.
Which do real developers install more?
Skills currently dominate raw install volume because they are frictionless: find-skills sits at 2,438,642 installs and the supabase skill at 161,567 installs (skills.sh registry, July 2026). But the highest-leverage skill categories are the ones that build or operate MCP servers, which tells you developers treat the two as complements, not rivals. Browse both sides: the skills directory and the MCP server directory, or start from the shortlist in Best MCP server skills for Claude Code.
Install counts come from the skills.sh registry via the Skillselion catalog, snapshot July 2026.
Common questions
Can a Claude skill replace an MCP server?
Only when the target system is already reachable through Claude's built-in tools. A skill that wraps a CLI (like microsoft/playwright-cli, 82,449 installs, skills.sh registry, July 2026) can substitute for an equivalent MCP server because Claude can run shell commands. But if the system needs authenticated, stateful, or protocol-level access that no CLI exposes, a skill cannot conjure the connection - you need MCP.
Can an MCP server replace a Claude skill?
Not well. An MCP server exposes tools, but it does not teach Claude your conventions, review standards, or multi-step workflows. You could stuff instructions into tool descriptions, but they load on every request and bloat context. Process knowledge belongs in a skill, which loads only when relevant.
Do skills and MCP servers work together in the same session?
Yes, and this is the most common production setup. The MCP server provides the connection (browser, database, docs index) and a skill provides the playbook for using it. Examples: the chrome-devtools skill pairs with the Chrome DevTools MCP server, and context7-mcp is a skill whose entire job is configuring and using the Context7 MCP server.
Which is cheaper in context tokens, a skill or an MCP server?
A skill, by a wide margin at rest. An idle skill costs only its name and description; the full SKILL.md loads on demand. Every connected MCP server injects its complete tool schemas into every request, so a 20-tool server consumes thousands of tokens continuously. The gap narrows once a large skill is actually loaded, but skills give you control over when that happens.
Do I need to write code to use either one?
No for consuming either one. Installing a skill is copying a folder or running npx skills add; adding a published MCP server is one claude mcp add command plus credentials. Writing your own is different: a custom skill is markdown you can draft in minutes, while a custom MCP server is a real software project - which is exactly what the mcp-builder skill (87,902 installs, skills.sh registry, July 2026) helps with.
Should I start with skills or MCP as a new Claude Code user?
Start with skills: zero infrastructure, instant payoff, and no credential handling. Install find-skills (2,438,642 installs, skills.sh registry, July 2026) so Claude can discover others on demand. Add your first MCP server when you hit a wall a skill cannot cross - usually the first time you want Claude to query a live database or drive a real browser.
Ranked by Skillselion - an independent directory of AI-coding tools, not affiliated with Anthropic, OpenAI or Cursor. Tool rankings reflect real adoption (installs, then GitHub stars) from the skills.sh registry and GitHub, last updated July 11, 2026.