MCPMarketDocs
Plugins

What are plugins

Install a toolkit's skills and MCP tools into Claude Code, Claude Cowork, or Codex with one bundle that auto-syncs.

A plugin packages everything in one toolkit — its MCP tools and its skills — for a specific AI client. Install the plugin once, and the client stays in sync with the toolkit as you add, remove, or update its contents.

Why use a plugin?

Plugins are the install vector for toolkits. They're useful when you want:

  • One install command that brings both MCP tools and skills into a client. A direct MCP connection only exposes tools — skills don't ride along.
  • Updates to flow automatically. As you change the toolkit on MCP Market, the client picks up the new state on its next session.
  • A clean way to scope what an agent sees. The plugin only includes what's in the toolkit — no more, no less.

How plugins work

Each plugin is tied to one toolkit and one client (Claude Code, Claude Cowork, or Codex). When you install the plugin into the client, it registers the toolkit's MCP endpoint and writes the toolkit's skills to disk. Every session, the plugin checks back with MCP Market for the current toolkit contents and updates the local copy.

Adding or removing items from the toolkit on the web is enough — there's nothing to reinstall on the client side.

Ready to install one? See Install a plugin.

On this page