cc-plugin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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:
|
| 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:
Responses:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
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.
Both tool names follow the consistent verb_noun pattern in snake_case (list_plugins, load_elements), making them predictable and readable.
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.
The tool set covers only read operations (list and load). Missing create, update, delete, or search functionality, which are significant gaps for managing plugins.