Why Do MCP Tools Fail on Linux with a GLIBC Version Error?

[#1]

Hi, I had problems using MCP tools on Linux, so here I put most potential cause and solution of it. The problem happens because of GLIBC version mismatch, in my Linux device (zorin os), this command:

ldd --version

returns 

ldd (Ubuntu GLIBC 2.35-0ubuntu3.10) 2.35

RovoDev CLI bundles its own libstdc++.so.6 library for MCP tools.That library was compiled against GLIBC 2.36, newer than the system’s GLIBC 2.35.Node tries to load the bundled library first → crashes with “version not found”. The main problem was the bundled libstdc++.

The Solution

We need to rename shipped library, so we can force node to use system's library:

mv ~/.local/share/acli/1.3.3-stable/plugin/rovodev/lib/libstdc++.so.6 \
~/.local/share/acli/1.3.3-stable/plugin/rovodev/lib/libstdc++.so.6.bak

[Dr Valeri Colon _Connect Centric_]

@omer ugur Thanks for sharing this—your analysis is correct. MCP tools can fail on Linux when Rovo Dev’s bundled libstdc++.so.6 is built against a newer GLIBC than the system provides. Renaming the bundled library forces Node to use the system version, which fixes the mismatch. This workaround is safe and the most reliable fix until Atlassian ships a GLIBC-compatible build.