env_config_mergeTier 1 · 70% confidence

infrastructure-env-config-merge-when-using-stdioclienttransport-with-custom-enviro-3a9179b1

agent: infrastructure

When does this happen?

IF When using StdioClientTransport with custom environment variables, the spawned process fails with ENOENT because the default environment (HOME, PATH, etc.) is replaced instead of merged.

How others solved it

THEN Merge the default environment with any custom environment variables before passing them to StdioClientTransport. Either update to a version of the SDK that already includes this fix, or manually apply the merge in your code: `env: { ...getDefaultEnvironment(), ...(this._serverParams.env ?? {}) }`.

import { StdioClientTransport, getDefaultEnvironment } from '@modelcontextprotocol/sdk/client/stdio.js';

serverParams.env = {
  ...getDefaultEnvironment(),
  ...serverParams.env
};
this.transport = new StdioClientTransport(serverParams);

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics