cc-recommender
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub personal access token (increases API rate limit from 60 to 5000 req/hour) | |
| SKIP_SECURITY_SCAN | No | Skip security scanning during data fetch (for developers) | false |
| CC_RECOMMENDER_OFFLINE_MODE | No | Disable auto-updates and use only bundled data | false |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| recommend_skillsA | プロジェクトを分析し、適切なツールを推薦します。デフォルトではプラグイン、MCPサーバー、スキル、ワークフロー、フック、コマンド、エージェントすべてのタイプを推薦します。ユーザーが特定のタイプ（例：「スキルだけ教えて」）を要求した場合のみ types パラメータで絞り込んでください。 |
| search_skillsA | キーワードですべてのタイプ（プラグイン、MCPサーバー、スキル、ワークフロー、フック、コマンド、エージェント）を検索します。デフォルトではすべてのタイプを検索します。ユーザーが特定のタイプのみを要求した場合のみ types パラメータで絞り込んでください。 |
| get_skill_detailsB | 特定のツール（プラグイン、MCPサーバー、スキル、ワークフロー、フック、コマンド、エージェント）の詳細情報を取得します |
| list_categoriesB | 利用可能なカテゴリ一覧を取得します |
| get_statsC | データベースの統計情報を取得します |
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 5 tools
Each tool has a recognizable role: keyword lookup (search_skills), project-based suggestion (recommend_skills), single-item detail (get_skill_details), enumeration (list_categories), and metadata (get_stats). The main risk is confusion between search_skills and recommend_skills, since both return tool candidates, but the descriptions distinguish keyword search from project analysis.
All five names follow a consistent verb_noun snake_case pattern (get_*, list_*, recommend_*, search_*). Minor semantic mismatch: get_skill_details actually covers plugins, MCP servers, workflows, hooks, commands, and agents, not just skills, which makes the noun misleading relative to the surface.
Five tools is a tight, well-scoped set for a recommendation/Discovery server, with no filler. Each tool corresponds to a distinct step in the discover-search-recommend-inspect workflow.
The discover → search → recommend → inspect lifecycle is covered, plus categories and stats for context. Minor gaps: no explicit 'list all tools' enumeration independent of keywords, and no pagination or filtering-by-metadata operation beyond the types parameter.