Log inSubmit server
Plugin Hub logo

Plugin Hub

Catalogs 500+ developer plugins for Claude Code through one local stdio MCP server.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Plugin Hub

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "barnburner121-plugin-hub-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@barnburner121/plugin-hub-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Plugin Hub MCP server bundles a catalog of 500+ Claude Code developer plugins behind one local stdio MCP server. The catalog covers testing, security, code quality, documentation, frontend and backend development, databases, and other engineering tasks. Reach for it when you want to browse or install multiple marketplace plugins without setting up each plugin separately.

Use cases

  • Install testing plugins for a Claude Code project
  • Scan infrastructure and application code for security issues
  • Generate documentation from an existing codebase
  • Plan refactoring using code-quality analysis plugins
  • Register one local MCP server for multiple developer tasks

Key features

  • 500+ developer plugins
  • Local stdio MCP server
  • Claude Code marketplace installation
  • Security and compliance analysis
  • Testing and documentation generation
  • Frontend, backend, and database tooling

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · @barnburner121/plugin-hub-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
npm downloads1.4kPackage downloads in the last 30 days.
Last commit7mo agoMost recent push to the default branch.

How Plugin Hub works

What Plugin Hub does

Plugin Hub MCP server packages a large collection of developer-focused Claude Code plugins into one marketplace and MCP entry point. The repository describes more than 500 tools spanning testing, DevOps, databases, security, compliance, code quality, refactoring, documentation, frontend work, backend and API design, and data tasks.

The marketplace is intended for Claude Code and Claude Cowork. Individual plugins cover focused activities such as generating unit or integration tests, finding code duplication, scanning infrastructure manifests, creating OpenAPI specifications, auditing accessibility, designing APIs, and analyzing SQL queries. The available catalog is organized by engineering domain rather than presented as one undifferentiated tool list.

How it works

Plugin Hub MCP server runs locally over stdio. A single MCP server process provides access to the plugin collection, avoiding the need to configure a separate MCP process for every listed plugin. The repository provides an npm-based launch command using npx and the package @barnburner121/plugin-hub-mcp.

Claude Code can also use the repository as a plugin marketplace. After adding the marketplace, a plugin can be installed by name with the marketplace identifier. This provides two related usage paths: install selected plugins through Claude Code’s marketplace commands, or register the MCP server directly in an MCP-compatible client.

Setup and configuration

For Claude Code, add the marketplace with:

text
/plugin marketplace add barnburner121/claude-plugin-marketplace

Then install a selected plugin using its name and the marketplace namespace:

text
/plugin install <plugin-name>@barnburner121-plugins

For direct MCP use, add a server entry whose command is npx and whose arguments request the package without prompting for installation:

config.json
{
  "mcpServers": {
    "plugin-hub": {
      "command": "npx",
      "args": ["-y", "@barnburner121/plugin-hub-mcp"]
    }
  }
}

The provided setup uses no environment variables or additional configuration values.

Tools and capabilities

The Plugin Hub MCP server’s catalog includes tools for:

  • Generating unit, integration, end-to-end, snapshot, accessibility, regression, and contract tests
  • Scanning code, containers, infrastructure manifests, templates, and APIs for security issues
  • Finding dead code, duplication, complexity, naming problems, and technical debt
  • Producing READMEs, API documentation, changelogs, runbooks, architecture documents, and diagrams
  • Generating frontend components, forms, themes, routes, metadata, and internationalization setup
  • Designing REST, GraphQL, gRPC, WebSocket, queue, caching, webhook, and validation systems
  • Analyzing schemas, migrations, SQL queries, test coverage, bundles, and web performance

Limitations and notes

The source describes the catalog and setup, but does not provide a complete implementation reference for every plugin or a full list of MCP method names. Plugin behavior therefore depends on the selected plugin. The project is presented as a local stdio server, so it is not described as a hosted or remote service.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Plugin Hub

Plugin Hub is an MCP server that connects Claude Code and Claude Cowork to a catalog of more than 500 developer plugins. Its main tools cover testing, security, code quality, documentation, frontend and backend development, databases, and related engineering tasks, with access provided through one local stdio process.

Install it by registering `npx -y @barnburner121/plugin-hub-mcp` as a local MCP server command. The README also supports adding the marketplace in Claude Code with `/plugin marketplace add barnburner121/claude-plugin-marketplace`, then installing individual plugins by name.

Install a plugin with `/plugin install <plugin-name>@barnburner121-plugins` after adding the marketplace. Replace `<plugin-name>` with the selected catalog entry, such as a testing, security, documentation, or code-quality plugin.

It describes direct MCP configuration through a local stdio command, but does not make a client-specific compatibility claim for Cursor.

Related MCP servers

All in Aggregators All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPlugin Hub AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/barnburner121-plugin-hub-mcp?style=directory)](https://allmcps.com/mcp/barnburner121-plugin-hub-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/barnburner121-plugin-hub-mcp"><img src="https://allmcps.com/api/badge/barnburner121-plugin-hub-mcp?style=directory" alt="Plugin Hub on AllMCPs" /></a>