allow ~ to be used in config

[EthBerryAdmin]

following config throws error

    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "~"
      ]
    },

Error accessing directory ~: Error: ENOENT: no such file or directory, stat '~'
    at async Object.stat (node:internal/fs/promises:1032:18)
    at async file:///Users/USER_NAME/.npm/_npx/a3241bba59c344f5/node_modules/@modelcontextprotocol/server-filesystem/dist/index.js:33:23━━━━━━━━━━━━━━━━━
    at async Promise.all (index 0)
    at async file:///Users/USER_NAME/.npm/_npx/a3241bba59c344f5/node_modules/@modelcontextprotocol/server-filesystem/dist/index.js:31:1 {
  errno: -2,
  code: 'ENOENT',
  syscall: 'stat',
  path: '~'
}

this commit fixes error and allows to set ~ as allowed directory

Description

Server Details

• Server:
• Changes to:

Motivation and Context

How Has This Been Tested?

Breaking Changes

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Protocol Documentation
• My changes follows MCP security best practices
• I have updated the server's README accordingly
• I have tested this with an LLM client
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have documented all environment variables and configuration options

Additional context

[EthBerryAdmin]

Hey guys! Any chance to get this merged?

[olaservo]

Looks good to me, can you get the latest from main and then I can merge? Edit: nm looks like it can be merged but I'm checking out some failing checks in the CI.

[olaservo]

Going to merge this one since the CI failure is unrelated and its a fairly urgent issue.

[EthBerryAdmin]

thanks