Dockerfile missing dependencies for mcpServers in default config

[1997cui]

What happened?

As titled, Dockerfile missing dependencies for mcpServers in the default config

Version Information

ghcr.io/danny-avila/librechat-dev                  latest         e6f1d6b9f0fd   About an hour ago   1.11GB
ghcr.io/danny-avila/librechat-rag-api-dev-lite     latest         6a1dfa1c7fe0   11 days ago         1.47GB

Steps to Reproduce

1. Uncomment the following in mcpServers section in librechat.yaml:

  puppeteer:     
      type: stdio     
      command: npx
     args:
       - -y
       - "@modelcontextprotocol/server-puppeteer"
     timeout: 300000  # 5 minutes timeout for this server

2. Follow the Quickstart guide to start docker
3. The following errors will be shown on the console:

LibreChat  | 2025-07-02 06:19:13 error: puppeteer_navigate MCP server tool call failed MCP error -32603: Failed to launch the browser process! spawn /home/node/.cache/puppeteer/chrome/linux-131.0.6778.204/chrome-linux64/chrome ENOENT

The chrome is there, but it is missing so libraries, which Dockerfile failed to add.

ctyi@cuiDesktop:~/software/dockers/librechat/repo$ docker compose exec -it api sh
/app $ 
/app $ ^C ./chrome -alh

/app $ ls /home/node/.cache/puppeteer/chrome/linux-131.0.6778.204/chrome-linux64/chrome
/home/node/.cache/puppeteer/chrome/linux-131.0.6778.204/chrome-linux64/chrome
/app $ ldd /home/node/.cache/puppeteer/chrome/linux-131.0.6778.204/chrome-linux64/chrome
        /lib64/ld-linux-x86-64.so.2 (0x7437b1619000)
        libdl.so.2 => /lib64/ld-linux-x86-64.so.2 (0x7437b1619000)
        libpthread.so.0 => /lib64/ld-linux-x86-64.so.2 (0x7437b1619000)
Error loading shared library libglib-2.0.so.0: No such file or directory (needed by /home/node/.cache/puppeteer/chrome/linux-131.0.6778.204/chrome-linux64/chrome)
Error loading shared library libgobject-2.0.so.0: No such file or directory (needed by /home/node/.cache/puppeteer/chrome/linux-131.0.6778.204/chrome-linux64/chrome)
Error loading shared library libnss3.so: No such file or directory (needed by /home/node/.cache/puppeteer/chrome/linux-131.0.6778.204/chrome-linux64/chrome)
Error loading shared library libnssutil3.so: No such file or directory (needed by /home/node/.cache/puppeteer/chrome/linux-131.0.6778.204/chrome-linux64/chrome)
Error loading shared library libsmime3.so: No such file or directory (needed by /home/node/.cache/puppeteer/chrome/linux-131.0.6778.204/chrome-linux64/chrome)
Error loading shared library libnspr4.so: No such file or directory (needed by /home/node/.cache/puppeteer/chrome/linux-131.0.6778.204/chrome-linux64/chrome)
Error loading shared library libdbus-1.so.3: No such file or directory (needed by /home/node/.cache/puppeteer/chrome/linux-131.0.6778.204/chrome-linux64/chrome)
Error loading shared library libatk-1.0.so.0: No such file or directory (needed by /home/node/.cache/puppeteer/chrome/linux-131.0.6778.204/chrome-linux64/chrome)
Error loading shared library libatk-bridge-2.0.so.0: No such file or directory (needed by /home/node/.cache/puppeteer/chrome/linux-131.0.6778.204/chrome-linux64/chrome)
Error loading shared library libcups.so.2: No such file or directory (needed by /home/node/.cache/puppeteer/chrome/linux-131.0.6778.204/chrome-linux64/chrome)
Error loading shared library libgio-2.0.so.0: No such file or directory (needed by /home/node/.cache/puppeteer/chrome/linux-131.0.6778.204/chrome-linux64/chrome)
Error loading shared library libdrm.so.2: No such file or directory (needed by /home/node/.cache/puppeteer/chrome/linux-131.0.6778.204/chrome-linux64/chrome)
Error loading shared library libexpat.so.1: No such file or directory (needed by /home/node/.cache/puppeteer/chrome/linux-131.0.6778.204/chrome-linux64/chrome)
        libm.so.6 => /lib64/ld-linux-x86-64.so.2 (0x7437b1619000)

The fix to this issue is to modify Dockerfile to contain all needed packages as stated in its help

What browsers are you seeing the problem on?

No response

Relevant log output

See above.

Screenshots

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[danny-avila]

There are ways around this, like making the dependency available in the OS environment and mounting it to docker. We will not be including puppeteer with the default docker image.

[thomasdv]

Can you please provide more details how to do it? According to docs it seems that should work right out of the box which is confusing.