Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallUse a Claude Code plugin to package and share a reusable setup; use an MCP server when Claude Code needs to connect to an external tool, database, or API. They are not mutually exclusive: a plugin can bundle MCP servers alongside skills, agents, and hooks.
What is the difference between a plugin and an MCP server?
A Claude Code plugin is an installable package of Claude Code components, usually organized around a manifest. It can include skills (instructions Claude can load when relevant), agent definitions, hooks (commands triggered by lifecycle events), and MCP servers. Anthropic’s Plugins overview recommends a plugin when you want several skills, subagents, hooks, or MCP servers packaged as one unit.
An MCP server connects Claude Code to external tools, databases, or APIs using the Model Context Protocol. Anthropic describes MCP as “an open protocol that standardizes how applications provide context to LLMs” in its MCP overview. The server provides the connection; it does not, by itself, package a broader Claude Code workflow for distribution.
When should you use each?
Choose a plugin for a reusable workflow
Use a plugin when the useful unit is a collection of Claude Code behaviors—for example, a team setup combining instructions, specialized agents, hooks, and an integration. Plugins are also suited to installing someone else’s prepared bundle or sharing a versioned setup across projects.
#1 Best Overall
Choose a standalone MCP server for an external connection
Configure an MCP server directly when the main need is for Claude Code to read from or act on another system, and there is no need to distribute additional components with it. Anthropic suggests connecting a server when you find yourself copying information from another tool into chat. Its documentation examples include issue trackers, monitoring systems, databases, design systems, and workflow tools; capabilities and permissions vary by integration.
Use both when packaging helps
A plugin can bundle one or more MCP servers with other Claude Code components. That makes the plugin the packaging and distribution layer, while MCP supplies the connection to the external service.
Use neither for a one-off task that needs no extension
If the existing session, tools, or project instructions are enough, there is no need to add a plugin or configure a server just to complete that task. This is a practical choice, not a specific Anthropic rule.
Compare the practical trade-offs
| Question | Plugin | MCP server |
|---|---|---|
| Primary purpose | Package Claude Code behavior such as skills, agents, hooks, and possibly MCP servers. | Connect Claude Code to an external tool, database, or API. |
| Reuse and sharing | Can be installed as a unit and shared as a versioned project or team setup. | Can be configured directly at local, project, or user scope. |
| Can it include the other? | Yes. A plugin can include MCP servers. | An MCP server is the connection; it does not package a plugin’s broader component bundle. |
| Runtime considerations | Enabled plugins participate in every session; names and descriptions for skills, agents, and commands can use context. Plugin MCP processes run alongside sessions where enabled, and hooks run at configured events. | Runs as a local process or connects remotely, depending on transport and server setup. |
| Security consideration | Plugins run with the user’s privileges, so inspect the source and behavior before installing. | Verify the server and its access. External content can carry prompt-injection risks; project-scoped servers require approval before use. |
How sharing and configuration scopes work
Plugin and MCP scopes are separate configuration systems. A plugin’s scope determines where it is available; it does not automatically commit every MCP credential or authorize collaborators to use a server.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Plugin user scope: available across projects on that computer.
- Plugin project scope: can be enabled for repository collaborators through committed Claude settings, but each collaborator installs the plugin locally.
- Plugin local scope: applies only to the current user in that repository.
- MCP local scope: configuration is local to the current project/user context.
- MCP project scope: configuration is written to
.mcp.jsonfor sharing. Claude Code asks for user approval before using a server from this file. - MCP user scope: configuration is available to the user across projects.
For a team integration, decide separately how to distribute the plugin, share MCP configuration, handle credentials, and obtain each user’s approval. A shared configuration should not be treated as shared authentication or blanket permission.
Choose an MCP transport that fits the server
Anthropic’s current MCP reference recommends remote HTTP where available. Local stdio servers run as processes on the machine and suit tools that need direct system access or custom scripts. The same reference marks Server-Sent Events (SSE) as deprecated in favor of HTTP where available; confirm the current guidance for your Claude Code version when configuring a server.
Review trust, permissions, and session impact
- For plugins: review what the package does before installing. An enabled plugin is part of every session, even when you do not invoke every component; its component names and descriptions may use context, hooks run at configured events, and bundled MCP processes run alongside enabled sessions.
- For MCP servers: verify the operator, authentication method, permissions, data access, and behavior. MCP itself does not certify a server as safe. Be especially cautious with servers that fetch external content, since that content may include prompt-injection attempts.
- For shared projects: treat approval as a per-user step, not as proof that the server is safe or that other collaborators have the same access.
Keep the marketplace terms distinct
A Claude Code plugin marketplace is a catalog and source listing for Claude Code plugins. It is not the same thing as the Claude Marketplace website.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Free tools Windows power users keep installed
One-click scans. No signup required.
