mirror of
https://github.com/RooVetGit/Roo-Code.git
synced 2026-10-30 06:43:13 +00:00
| .. | ||
| mcp-servers/test-server | ||
| metadata.en.yml | ||
| README.md | ||
Minimal Package Manager Repository
This is a minimal example of a package manager repository structure that meets the basic requirements. The structure is intentionally kept as simple as possible to help diagnose any validation issues.
Structure
/
├── metadata.en.yml # Required: Repository metadata (must be exactly this name)
└── mcp-servers/ # Optional: Directory for MCP servers
└── test-server/ # Must be a directory
└── metadata.en.yml # Must match pattern metadata.[locale].yml
metadata.en.yml
name: Test Repository
description: A minimal test repository
version: 1.0.0
mcp-servers/test-server/metadata.en.yml
name: Test Server
description: A minimal test server
type: mcp server
version: 1.0.0
Key Points
- File names must be exactly:
- metadata.en.yml (not metadata.yml or any other variation)
- Components must be in directories
- No empty lines in YAML files
- No quotes around values
- No extra fields
- No special characters
- No complex YAML features (arrays, nested objects, etc.)
Try copying this exact structure to your GitHub repository to test. The validation should pass with this minimal setup.
Validation Process
- First, it checks for metadata.en.yml in the root
- Then it scans for component directories
- For each directory, it looks for metadata.en.yml files
- Each metadata file is validated for required fields
- Component metadata must have a valid type ("mcp server", "mode", "prompt", or "package")