Skip to content

Conversation

@roomote
Copy link
Contributor

@roomote roomote bot commented Sep 3, 2025

Description

This PR attempts to address Issue #7613 by providing a reference configuration for adding windows-mcp to the MCP Marketplace.

Context

After investigating the codebase, I discovered that MCP servers are fetched from a remote API endpoint rather than being stored in this repository. The marketplace items are managed externally through the backend API.

Changes

  • Created directory for MCP server submission examples
  • Added with complete configuration following the marketplace schema
  • Included multiple installation methods (uvx, pip, development)
  • Added comprehensive documentation explaining the marketplace submission process

Purpose

This example configuration can be used by maintainers to:

  1. Add windows-mcp to the marketplace backend API
  2. Serve as a reference for future MCP server submissions
  3. Document the expected format for marketplace items

Related Issue

Closes #7613

Notes

  • The actual addition to the marketplace requires backend updates by the Roo Code team
  • This PR provides the necessary configuration that can be used for that backend update
  • Feedback and guidance are welcome!

Important

Adds Windows MCP example configuration to marketplace-examples with documentation for marketplace submissions.

  • New Configuration:
    • Adds marketplace-examples/mcp-servers/windows-mcp.yaml with a complete configuration for Windows MCP.
    • Includes multiple installation methods: uvx, pip, and development.
    • Provides optional parameters for configuration.
  • Documentation:
    • Adds marketplace-examples/README.md to document the marketplace submission process and configuration format.
    • Explains the structure and purpose of the marketplace-examples directory.
  • Purpose:
    • Serves as a reference for adding Windows MCP to the marketplace backend API.
    • Documents the expected format for future MCP server submissions.

This description was created by Ellipsis for b94a85f. You can customize this summary. It will automatically update as commits are pushed.

- 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.
@roomote roomote bot requested review from cte, jr and mrubens as code owners September 3, 2025 06:05
@dosubot dosubot bot added size:L This PR changes 100-499 lines, ignoring generated files. documentation Improvements or additions to documentation labels Sep 3, 2025

## Purpose

Since the Roo Code Marketplace items are managed through an external API (`https://api.roocode.com/api/marketplace/`), this directory serves as:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider clarifying API endpoint URLs: The README mentions https://api.roocode.com/api/marketplace/ while later it refers to https://api.roocode.com/api/marketplace/mcps. Ensure consistency if they are intended to be the same.

Suggested change
Since the Roo Code Marketplace items are managed through an external API (`https://api.roocode.com/api/marketplace/`), this directory serves as:
Since the Roo Code Marketplace items are managed through an external API (`https://api.roocode.com/api/marketplace/mcps`), this directory serves as:

Copy link
Contributor Author

@roomote roomote bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewing my own code is like debugging in a mirror - everything looks backwards but the bugs are still mine.

- pip package manager

# Installation methods for different scenarios
content:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The structure here doesn't quite match the schema defined in packages/types/src/marketplace.ts. According to the schema, when using multiple installation methods, each method's content field should be a string containing the JSON configuration. However, I see prerequisites nested under each installation method, which should actually be at the root level for the entire MCP server.

Could we restructure this to match the expected format? The prerequisites at line 18-21 are correct for the root level, but lines 32-33, 42-43, and 54-56 should be removed since prerequisites per installation method aren't supported by the schema.

content: |
{
"command": "uvx",
"args": ["--from", "windows-mcp", "windows-mcp"],
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this intentional that we're using windows-mcp as the package name for uvx? The actual package might not exist on PyPI yet. Consider adding a comment clarifying this is an example configuration and the actual package availability should be verified.


## MCP Server Configuration Format

MCP server configurations follow the schema defined in `packages/types/src/marketplace.ts`. Each configuration should include:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we add a note here mentioning that the type field would be added programmatically when these configurations are processed? According to the schema, the type discriminator is added during processing, not in the YAML files themselves.


1. Follow the existing format and structure
2. Ensure all required fields are present
3. Test the installation instructions
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider adding a section about validation here. It would be helpful to document how contributors can validate their example configurations against the TypeScript schema before submission. Perhaps we could add a simple validation script or at least point to the schema location?

@roomote roomote bot mentioned this pull request Sep 3, 2025
1 task
@hannesrudolph hannesrudolph added the Issue/PR - Triage New issue. Needs quick review to confirm validity and assign labels. label Sep 3, 2025
@daniel-lxs daniel-lxs closed this Sep 4, 2025
@github-project-automation github-project-automation bot moved this from Triage to Done in Roo Code Roadmap Sep 4, 2025
@github-project-automation github-project-automation bot moved this from New to Done in Roo Code Roadmap Sep 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation Issue/PR - Triage New issue. Needs quick review to confirm validity and assign labels. size:L This PR changes 100-499 lines, ignoring generated files.

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

[MCP] windows-mcp

4 participants