- Created marketplace-examples directory for MCP server submissions - Added windows-mcp.yaml with complete configuration following marketplace schema - Included multiple installation methods (uvx, pip, development) - Added comprehensive documentation explaining marketplace submission process - Addresses #7613 by providing reference configuration for windows-mcp This example can be used by maintainers to add windows-mcp to the marketplace backend API. |
||
|---|---|---|
| .. | ||
| mcp-servers | ||
| README.md | ||
Marketplace Examples
This directory contains example configurations for items that could be added to the Roo Code Marketplace.
Purpose
Since the Roo Code Marketplace items are managed through an external API (https://api.roocode.com/api/marketplace/), this directory serves as:
- Reference examples for new marketplace submissions
- Documentation of the expected format for MCP servers and modes
- Testing ground for validating configurations before they're added to the marketplace backend
Structure
marketplace-examples/
├── mcp-servers/ # Example MCP server configurations
│ └── windows-mcp.yaml
└── modes/ # Example custom mode configurations (future)
MCP Server Configuration Format
MCP server configurations follow the schema defined in packages/types/src/marketplace.ts. Each configuration should include:
Required Fields
id: Unique identifier for the MCP servername: Display namedescription: Clear description of what the server doesurl: GitHub repository or project URLcontent: Installation configuration(s)
Optional Fields
author: Creator's nameauthorUrl: Link to author's profiletags: Array of relevant tags for discoveryprerequisites: System requirements or dependenciesparameters: Configurable options for the server
Example: Windows MCP
The mcp-servers/windows-mcp.yaml file demonstrates a complete configuration for the Windows MCP server, which allows AI agents to control Windows desktop applications, browsers, and file operations.
Key Features Highlighted:
- Multiple installation methods (uvx, pip, development)
- Clear prerequisites for each installation method
- Optional configuration parameters
- Comprehensive tagging for discoverability
How to Submit to Marketplace
Currently, marketplace items are managed through the Roo Code backend API. To submit a new MCP server:
- Create a configuration file following the examples in this directory
- Test the configuration locally to ensure it works
- Submit an issue using the Marketplace Feedback template
- Include your configuration file in the issue
- The Roo Code team will review and add it to the marketplace backend
Testing Locally
While these configurations cannot be directly used in the extension (as it fetches from the API), you can manually test MCP servers by:
- Installing them according to their documentation
- Adding them to your
.roo/mcp.json(project-level) or global MCP settings - Verifying they work correctly with Roo Code
Contributing
If you'd like to add more example configurations:
- Follow the existing format and structure
- Ensure all required fields are present
- Test the installation instructions
- Submit a PR with your example configuration
Notes
- These examples are for reference only and don't automatically appear in the marketplace
- The actual marketplace data is served from
https://api.roocode.com/api/marketplace/mcps - Changes to the marketplace require backend updates by the Roo Code team