Using env var for MCP OAuth Secret

[duypm]

Hi,

I'm configuring GitHub MCP for my team LibreChat instance with OAuth and I want to leave the client_secret to be read from env var instead of being put directly inside librechat.yaml.

I have tried to do it like below, but it doesn't seem to work

github:
  type: streamable-http
  url: https://api.githubcopilot.com/mcp/
  startup: false
  initTimeout: 150000
  oauth:
    authorization_url: https://github.com/login/oauth/authorize
    token_url: https://github.com/login/oauth/access_token
    client_id: "${GITHUB_OAUTH_CLIENT_ID}"
    client_secret: "${GITHUB_OAUTH_CLIENT_SECRET}"

If I replace ${GITHUB_OAUTH_CLIENT_ID} and ${GITHUB_OAUTH_CLIENT_SECRET} with an actual client_id and client_secret value from my GitHub OAuth App, the MCP integration works for my chat.

From the doc It looks to me that LibreChat does support env var extrapolation for librechat.yaml so I'm wondering if I have done anything incorrectly.

Thank you very much for taking a look at my case.

[FINDarkside]

I'm having same kind of issue, although I'm trying to use interpolation inside command arguments and I'm not sure if it's supported. Doesn't seem to work at least

  test:
    type: stdio
    command: npx
    args:
      - mcp-remote
      - "--header"
      - "x-api-key: ${EXAMPLE_API_KEY}"
      - "https://example.com/"

[FINDarkside]

Ok I got this usecase working like this:

mcpServers:
  example:
    type: stdio
    command: npx
    env:
      EXAMPLE_API_KEY: ${EXAMPLE_API_KEY}
    args:
      - mcp-remote
      - "--header"
      - "x-api-key: ${EXAMPLE_API_KEY}"
      - "https://example.com/"

The way I understand it is that LibreChat is not doing interpolation on the args, but mcp-remote is. Librechat is doing interpolation on env variables, so we can pass it forward to mcp-remote.