What does Claude Code use instead of plugins or extensions?

Claude Code utilizes "skills" and "MCP connections" in place of traditional plugins or extensions. Skills are essentially markdown instructions that guide Claude on how to perform specific tasks, while MCP connections enable Claude to interact with and utilize external services and tools.

What is the primary function of skills in Claude Code?

Skills serve as the primary method to extend Claude Code's capabilities. They are implemented as SKILL.md files containing markdown instructions that teach Claude how to handle various tasks, such as code review, testing, documentation, and DevOps. These are not executable code but rather expert knowledge presented as instructions for Claude to follow.

Where can users find skills for Claude Code?

Users can find skills for Claude Code in several places. The Agensi marketplace offers a curated selection of security-scanned skills for purchase. Alternatively, open-source skills are available on GitHub, which are typically free but unvetted. Skills are also shared within various community platforms like Reddit, Discord, and blogs.

What is the main difference between skills and MCP connections in Claude Code?

The main difference is in their function: skills teach Claude *how* to do tasks using markdown instructions, while MCP connections give Claude *access* to external services via a server endpoint. Skills do not require hosting, whereas MCP connections do, as they involve an MCP server. They are complementary; for example, a skill might instruct Claude on code review, and an MCP connection to GitHub would allow it to access pull requests for review.

Claude Code Plugins, Extensions & Skills

Q: How do MCP connections enhance Claude Code's functionality?

MCP (Model Context Protocol) connections allow Claude Code to link with external services and use them as tools. An MCP server exposes capabilities that Claude can call upon, such as reading from databases, querying APIs, accessing file systems, or interacting with services like GitHub, Slack, or Jira. These connections are the closest equivalent to what might be called "plugins" in other systems, providing Claude with new functionalities it doesn't possess natively.

People search for "Claude Code plugins" and "Claude Code extensions" but Claude Code doesn't use that terminology. What Claude Code has is skills and MCP connections. Here's what each does and how they relate to what you might call plugins or extensions.

Quick Answer: Claude Code has "skills" and "MCP connections" instead of plugins or extensions. Skills are markdown instructions that teach Claude how to perform tasks, while MCP connections allow Claude to interact with external services and tools.

Skills (SKILL.md)

Skills are the primary way to extend Claude Code. A SKILL.md file teaches Claude how to handle specific tasks — code review, testing, documentation, DevOps, and more.

Skills are not code that runs. They're instructions that Claude reads and follows. Think of them as expert knowledge packaged in a file.

~/.claude/skills/code-reviewer/SKILL.md

Install a skill by putting its folder in your skills directory. Claude Code loads it at session startup.

Find skills: Agensi marketplace or GitHub.

See SKILL.md in action

Doxaflow

by Matthew Ward

$19

finalize

by Alex Shi

Flutter Cross Master

by Pietro Giovanni Vaccarello

Browse all skills

MCP connections

MCP (Model Context Protocol) lets Claude Code connect to external services and use them as tools. An MCP server exposes capabilities that Claude can call — reading from databases, querying APIs, accessing file systems, or interacting with services like GitHub, Slack, or Jira.

MCP connections are the closest thing to what other tools call "plugins" — they give Claude new capabilities it doesn't have natively.

Common MCP connections:

Database access (read and write to your DB)
GitHub integration (create issues, read PRs)
Project management (Jira, Linear, Asana)
Monitoring (read logs, check alerts)
Custom internal tools

Skills vs MCP — when to use each

	Skills (SKILL.md)	MCP Connections
What they do	Teach Claude how to do tasks	Give Claude access to external services
Format	Markdown instructions	Server endpoint
Installation	Drop file in folder	Configure connection URL
Example	"Review code checking for OWASP Top 10"	"Read from our PostgreSQL database"
Requires hosting	No	Yes (MCP server)

They're complementary. A code review skill tells Claude how to review code. An MCP connection to GitHub gives Claude access to PRs that need review. Together: Claude pulls the PR via MCP and reviews it using the skill's standards.

Where to find them

Skills

Agensi — curated marketplace, security-scanned, one-time purchase
GitHub — open source, unvetted, free
Community — shared on Reddit, Discord, blogs

MCP servers

Agensi's one-liner curl install — live access to the full skill catalog via MCP
Official integrations — Anthropic maintains MCP servers for common services
Community servers — open source MCP servers on GitHub
Custom — build your own for internal tools

The "plugin marketplace" for Claude Code

If you're looking for what would be a "plugin marketplace" in other ecosystems, the closest thing is Agensi. It's a curated catalog of skills organized by category (code review, testing, DevOps, frontend, documentation, etc.) that you can browse, purchase, and install in seconds.

With Agensi's one-liner curl install, your agent connects via MCP and pulls skills on demand — no manual browsing or downloading. You describe what you need and the right skill loads automatically.

What's coming

The skill and MCP ecosystem is growing rapidly. Expect:

More MCP integrations with common dev tools
Agent-native discovery (your agent finds and suggests skills automatically)
Skill composition (skills that reference other skills)
Team skill management (centralized skill configuration for organizations)

Browse the skill catalog at Agensi.

Claude Code Plugins, Extensions & Skills — What's Available (2026)