Dest server.json file support env var?

[inevity]

found API_TOKEN use env var.
But i cannot use env var.

how troubleshoot it?

[ravitemer]

@inevity You can use ${} placeholder for any env vars. MCP Hub will replace ${VAR} with actual variable. For e.g:

{
  "github": {
    "headers": {
      "Authorization": "Bearer ${GITHUB_ACCESS_TOKEN}"
    },
    "url": "https://api.githubcopilot.com/mcp/",
  }
}

In case you store secret in some vault, you can also use ${cmd:} placeholders:

{
  "github": {
    "headers": {
      "Authorization": "Bearer ${cmd:  echo 'mysecret'}"
    },
    "url": "https://api.githubcopilot.com/mcp/",
  }
}

Refer to https://ravitemer.github.io/mcphub.nvim/mcp/servers_json.html#universal-placeholder-syntax

[inevity]

I'm already using this PWD variable, but it doesn't seem to work.
For example, cd in dir A: open nvim, open mcphub, enter filesystem mcp server, run list directory ls ., which show all A content, It is ok.
now cd into dir B: open nvim, open mcphub, enter filesystem mcp server, ls ., which show all A content, which should be B content.

the json config:

    "filesystem-current": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "${PWD}"
      ],
      "name": "Filesystem (Current Dir)",
      "description": "File operations for current working directory"
    },

[ravitemer]

The Environment variables are not dynamic, they are only evaluated when the server starts. In order for it to take the new enviroment you need to press R to restart the hub so that the underlying filesystem program gets the latest process.env

I suggest you have two separate servers with different filesystem argument for such cases.

[inevity]

Yes, should restart the mcphub binary. To avoid the manual restart, We should get env var from nvim, not from mcphub ? or exit nvim should close mcphub?
I suggest you have two separate servers with different filesystem argument for such cases ------------------You mean not use PWD env and specify the concrete path to avoid the restart?