Is your feature request related to a problem? Please describe.
Our organization uses VS Code + GitHub Copilot in a security-hardened environment where our MCP policy is strictly set to registryOnly. This means our tools can only discover and initialize servers explicitly listed in the Official MCP Registry: https://registry.modelcontextprotocol.io/.
Currently, microsoft/playwright-mcp is not indexed in this registry. Because our setup blocks manual stdio definitions and local command-line execution, we are entirely unable to use Playwright's browsing capabilities. We require the central registry to act as the single source of truth for metadata verification.
Describe the solution you'd like
We request that the maintainers publish the @playwright/mcp server to the Official MCP Registry (https://registry.modelcontextprotocol.io/).
See: https://github.com/modelcontextprotocol/registry
Describe alternatives you've considered
We have attempted to side-load the server via manual JSON/command definitions in our local environment, but these are flagged and blocked by our org-level security policy to ensure supply chain integrity.
Additional context
We noticed that @pavelfeldman recently merged a commit adding the mcpName field to package.json. Since the technical infrastructure for registry ownership is now in place, we hope you can complete the final step of the Official Publishing Guide by running the mcp-publisher tool. This would solve a major blocker for enterprise teams relying on VS Code and GitHub Copilot.
Mahalo (thanks),
Joshua Fontany
Automation Engineer - Consumer Cellular
Is your feature request related to a problem? Please describe.
Our organization uses VS Code + GitHub Copilot in a security-hardened environment where our MCP policy is strictly set to registryOnly. This means our tools can only discover and initialize servers explicitly listed in the Official MCP Registry: https://registry.modelcontextprotocol.io/.
Currently, microsoft/playwright-mcp is not indexed in this registry. Because our setup blocks manual stdio definitions and local command-line execution, we are entirely unable to use Playwright's browsing capabilities. We require the central registry to act as the single source of truth for metadata verification.
Describe the solution you'd like
We request that the maintainers publish the @playwright/mcp server to the Official MCP Registry (https://registry.modelcontextprotocol.io/).
See: https://github.com/modelcontextprotocol/registry
Describe alternatives you've considered
We have attempted to side-load the server via manual JSON/command definitions in our local environment, but these are flagged and blocked by our org-level security policy to ensure supply chain integrity.
Additional context
We noticed that @pavelfeldman recently merged a commit adding the mcpName field to package.json. Since the technical infrastructure for registry ownership is now in place, we hope you can complete the final step of the Official Publishing Guide by running the mcp-publisher tool. This would solve a major blocker for enterprise teams relying on VS Code and GitHub Copilot.
Mahalo (thanks),
Joshua Fontany
Automation Engineer - Consumer Cellular