Skip to main content
Glama
Sign In
cc-plugin-mcp

cc-plugin-mcp

by ppspps824
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cc-plugin-mcp

MCP (Model Context Protocol) server for accessing Claude Code plugins.

Overview

This MCP server provides an interface to Claude Code's plugin system via the Model Context Protocol, enabling you to retrieve plugin lists and detailed information. It can be used from MCP clients such as Claude Desktop, Cursor, etc.

Related MCP server: claudecode-mcp

Key Features

  • MCP Protocol Support: Compliant with Model Context Protocol

  • Plugin Management: Retrieve plugin lists and load elements from Claude Code plugins

  • Security: Path traversal protection, input validation, error handling

  • Performance: LRU cache for fast access

  • Operability: Comprehensive logging, 29 test cases

MCP Tools

  • list_plugins - Get a list of available plugins

  • load_elements - Load elements (skills, agents, commands) from specified plugins

Configuration

Add the following to your MCP client configuration file (e.g., claude_desktop_config.json for Claude Desktop):

{
  "mcpServers": {
    "cc-plugin-mcp": {
      "command": "uvx",
      "args": ["cc-plugin-mcp"]
    }
  }
}

Installation

# Run directly with uvx (recommended)
uvx cc-plugin-mcp

# Or install from PyPI
pip install cc-plugin-mcp

# For development
git clone https://github.com/ppspps824/cc-plugin-mcp.git
cd cc-plugin-mcp
uv sync --all-extras

Usage

This runs as an MCP server and is called directly by MCP clients. For manual testing:

# Start MCP server with uvx (recommended)
uvx cc-plugin-mcp

# Or for development
uv run python -m cc_plugin_mcp.main

MCP Integration with AI Tools

For optimal use of this MCP server with AI tools like Cursor, Claude Desktop, or other MCP-compatible clients:

With Cursor

  1. Add the MCP server to your Cursor settings (.cursor/settings.json or similar)

  2. Include the configuration shown in the Configuration section above

  3. Important: Make sure to load the MCP server tools in your system prompt or initial message. Tell the AI to use the available MCP tools by instructing it to first call the MCP tools list to discover what's available.

With Claude Desktop

  1. Add the configuration to claude_desktop_config.json as shown in the Configuration section

  2. Restart Claude Desktop to enable the MCP server

  3. The MCP tools will be automatically available for Claude to use

Best Practices for Using MCP Tools

  • Load the tools first: Always instruct the AI to first call the available MCP tools to discover what's available

  • Check the system prompt: Ensure your system prompt or initial instructions include guidance to use MCP tools

  • Discover capabilities: Use the tools to explore available plugins and their elements before requesting specific functionality

Testing

# Run tests
uv run pytest

# With coverage
uv run pytest --cov=cc_plugin_mcp

Troubleshooting

Plugins not found

  1. Check if ~/.claude/plugins/ directory exists

  2. Verify marketplace.json exists in ~/.claude/plugins/marketplaces/

MCP client doesn't recognize the server

  1. Verify MCP client configuration file is set up correctly

  2. Check if uvx command is available (uvx --version)

  3. Check MCP client logs for error messages

Tests failing

uv sync --all-extras --refresh
uv run pytest -v

License

MIT

Repository

https://github.com/ppspps824/cc-plugin-mcp

Available Tools

2 tools
list_pluginsA

Get list of all available plugins from marketplaces.

Returns: List of plugins with name, description, and categorized elements (agents, commands, skills).

Raises: HTTPException: If plugins cannot be read.

Responses:

  • 200 (Success): Successful Response

    • Content-Type: application/json

    • Example:

[
  "unknown_type"
]

Inputs: no named parameters. Returns: result

load_elementsC

Load plugin elements (skills, agents, commands) with their content.

Args: plugin_name: Name of the plugin. request: Request body with elements to load.

Returns: Response with loaded element contents.

Raises: HTTPException: If plugin is not found or elements cannot be read.

Path Parameters:

  • plugin_name (Required): No description.

Responses:

  • 200 (Success): Successful Response

    • Content-Type: application/json

    • Response Properties:

      • plugin_name: プラグイン名

      • elements: 読み込まれた要素のリスト

    • Example:

{
  "plugin_name": "string",
  "elements": [
    "unknown_type"
  ]
}

  • 422: Validation Error

    • Content-Type: application/json

    • Response Properties:

    • Example:

{
  "detail": [
    "unknown_type"
  ]
}

Inputs: plugin_name (required), elements (required). Returns: Response containing loaded plugin elements.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    B3.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    list_plugins and load_elements have clearly distinct purposes: one for browsing all plugins, the other for retrieving detailed elements of a specific plugin. No overlap or confusion possible.

    Naming Consistency5/5

    Both tool names follow the consistent verb_noun pattern in snake_case (list_plugins, load_elements), making them predictable and readable.

    Tool Count3/5

    With only 2 tools, the server feels thin for a plugin management system. However, the tools are well-scoped to listing and loading, so it is borderline acceptable.

    Completeness2/5

    The tool set covers only read operations (list and load). Missing create, update, delete, or search functionality, which are significant gaps for managing plugins.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers