MCP Server expose via HTTP

[mofaizal]

The ExecuteAutomation MCP server is designed to work with MCP clients (like Claude Desktop, VS Code, etc.) rather than as a standalone HTTP server. It doesn't expose a /health endpoint

we need support MCP server functionality via HTTP endpoints. like standard MCP Server.

[vtanathip]

I'm interested in the same functionality as the Standalone MCP Server mentioned here

https://github.com/microsoft/playwright-mcp?tab=readme-ov-file#standalone-mcp-server

[aakashH242]

Hi @mofaizal @vtanathip

It looks like this repo is no longer maintained and the maintainer seems unresponsive. I also required the server to support streamable HTTP transport so it can be run as a standalone MCP server and be deployed to large orgs behind MCP Gateways.

I have made a fork of this repo and added in the streamable HTTP transport support and will be maintaining it. You can find the fork here - https://github.com/aakashH242/mcp-playwright

• To run it with npx -

npx @executeautomation/playwright-mcp-server --http

• If you prefer running it as a container -

docker run --rm -p 8000:8000 -v /data:/data \
ghcr.io/aakashh242/mcp-playwright:latest \
node dist/index.js --http 

It also support some CLI flags to control the behavior when running in HTTP mode.

For more documentation on how to get it running in streamable HTTP mode, see here -https://aakashh242.github.io/mcp-playwright/docs/category/getting-started

For CLI options, see the document here - https://aakashh242.github.io/mcp-playwright/docs/getting-started/cli-flags

---

Please feel free to test it out and use it for your projects and do file issues for any bugs you discover or new features you'd want implemented.

Don't forget to show some love to the fork and drop a Star if you found the server useful! Thanks!