Config file for playwright docker image

[kedar-1]

Hi,

can please provide a config file for -playwright docker image?

Thanks

[ptbsare]

hi @kedar-1 Sorry, I don't quite understand what you mean. Are you asking me to provide a sample file for Playwright mcp server? What kind of config are you referring to? This image already integrates the Playwright command-line tool, so you can use it directly inside the container.

[kedar-1]

Yes, I mean the config file for playwright image.

Here is the command for my deployment:
docker run -d -p 3663:3663 -e PORT=3663 -e ENABLE_ADMIN_UI=true -e ADMIN_USERNAME=admin -e ADMIN_PASSWORD=xxxxx --name mcp-proxy-server ghcr.io/ptbsare/mcp-proxy-server/mcp-proxy-server:latest-bundled-mcpservers-playwright

After logging into the web admin I don't see any info about mcp servers.
My expectation is that I will se a list of npm or pip servers and have the possibility to manage.

[ptbsare]

hi @kedar-1
Okay, I understand.

The original intention behind the Playwright version was to facilitate the pre-installation of certain packages (including browsers) to simplify the installation process for MCP servers. Playwright is essentially a command-line tool for running browsers, and many MCP servers that rely on browser operations depend on it.

Given that there are thousands of MCP servers on the market, I'm unable to list all the ones you can install and run directly on the web page. However, if you are using the Playwright version, it does come with some pre-installed MCP servers. I can provide you with a config file that includes all these built-in MCP servers. You can import it using the "Parse Config" button in the web interface or directly replace your mcp_server.json file.

Please note that some MCP servers require a valid API key to function. You can install other MCP servers on top of these. This program is merely a one-stop tool to conveniently manage and install MCP servers. You are free to install and manage any MCP server you desire, not just those built into the Docker image. You can search for servers that interest you on GitHub and install them accordingly.

mcp_server.json

{
  "mcpServers": {
    "edgeone-pages-mcp": {
      "active": true,
      "type": "stdio",
      "command": "edgeone-pages-mcp",
      "args": [],
      "env": {},
      "installDirectory": "/tools/edgeone-pages-mcp",
      "installCommands": []
    },
    "g-search-mcp": {
      "active": true,
      "type": "stdio",
      "command": "g-search-mcp",
      "args": [],
      "env": {},
      "installDirectory": "/tools/g-search-mcp",
      "installCommands": []
    },
    "markitdown-mcp": {
      "active": true,
      "type": "stdio",
      "command": "markitdown-mcp",
      "args": [],
      "env": {},
      "installDirectory": "/tools/markitdown-mcp",
      "installCommands": []
    },
    "mcp-google-search": {
      "active": true,
      "type": "stdio",
      "command": "mcp-google-search",
      "args": [],
      "env": {
        "GOOGLE_API_KEY": "your_google_api_key",
        "GOOGLE_SEARCH_ENGINE_ID": "your_google_engine_id"
      },
      "installDirectory": "/tools/mcp-google-search",
      "installCommands": []
    },
    "mcp-server-baidu-map": {
      "active": true,
      "type": "stdio",
      "command": "mcp-server-baidu-map",
      "args": [],
      "env": {
        "BAIDU_MAP_API_KEY": "your_api_key"
      },
      "installDirectory": "/tools/mcp-server-baidu-map",
      "installCommands": []
    },
    "mcp-server-filesystem": {
      "active": true,
      "type": "stdio",
      "command": "mcp-server-filesystem",
      "args": [
        "/tools/"
      ],
      "env": {},
      "installDirectory": "/tools/mcp-server-filesystem",
      "installCommands": []
    },
    "mcp-server-weibo": {
      "active": true,
      "type": "stdio",
      "command": "mcp-server-weibo",
      "args": [],
      "env": {},
      "installDirectory": "/tools/mcp-server-weibo",
      "installCommands": []
    },
    "mcp-trends-hub": {
      "active": true,
      "type": "stdio",
      "command": "mcp-trends-hub",
      "args": [],
      "env": {},
      "installDirectory": "/tools/mcp-trends-hub",
      "installCommands": []
    },
    "time-mcp": {
      "active": true,
      "type": "stdio",
      "command": "time-mcp",
      "args": [],
      "env": {},
      "installDirectory": "/tools/time-mcp",
      "installCommands": []
    },
    "variflight-mcp": {
      "active": true,
      "type": "stdio",
      "command": "variflight-mcp",
      "args": [],
      "env": {
        "VARIFLIGHT_API_KEY": "your_api_key"
      },
      "installDirectory": "/tools/variflight-mcp",
      "installCommands": []
    },
    "fetcher-mcp": {
      "active": true,
      "type": "stdio",
      "command": "fetcher-mcp",
      "args": [],
      "env": {},
      "installDirectory": "/tools/fetcher-mcp",
      "installCommands": []
    }
  }
}

[kedar-1]

OK, thanks, that's exactly I was looking for.

Unfortunately a definition for npm @modelcontextprotocol/inspector is missing.

Can you pls add this mcp server and put the file to the "config" repo folder?

Thanks

[ptbsare]

hi @kedar-1
@modelcontextprotocol/inspector is not a mcp server, it is a inspector/debug/test tool for mcp server, you can run.

docker exec mcp-proxy-server mcp-inspector

and open http://docker_ip:6274 to test whether your stdio/sse/http mcp server is working in the web page.