Maintainer activity check — planning to maintain a fork (starting with #168)

[aakashH242]

Hi @executeautomation , I hope you're doing well.

I’m opening this issue to check on the current maintenance status of this project. Over the past month there have been no responses on issues or pull requests, and some MCP-critical items (such as #168 regarding HTTP/streamable MCP server support) are blocking downstream usage.

Since my team needs a reliable and actively maintained MCP Playwright server for production and organizational deployments, I’m planning to maintain a fork of this project. The fork will begin by addressing #168 and adding:

• Full Streamable HTTP MCP server mode
• Proper upload handling (resource-scoped URIs, session isolation)
• Updated MCP spec compatibility
• A maintained container image on GHCR

This is not meant as a takeover - just a continuation so the community and org users have a working, up-to-date version.

If you're still actively maintaining this repository or would prefer collaboration instead of a fork, please let me know. I’m happy to contribute upstream if there’s an active maintainer presence.

Thank you for the original work on this project - it’s a great foundation, and I want to ensure the MCP community keeps benefiting from it.