Skip to content

Spaces in parameters #26

@mscinar

Description

@mscinar

I'm trying to configure the Chrome-Dev-Tools on my mac with MetaMCP involving a path parameter containing space characters.

For the dev-tools mcp I need a parameter "--executablePath" that points to my chrome installation at "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome".

I've tried plenty of ways to get that path with white-spaces to work with MetaMCP and had no luck.
It always destroys the path to multiple parameters, which then lead to a "Browser was not found at the configured executablePath ('/Applications/Google)" error.

I tried to escape the whitespaces with a backslash as it is done in the terminal. No success.
I tried to use "-quotes around the path. No success.
I tried to use '-quotes around the path. No success.
I tried to import the server as correct json. No success:
Input json:

{
  "mcpServers": {
    "chrome-devtools": {
      "type": "STDIO",
      "command": "npx",
      "args": [
        "-y",
        "chrome-devtools-mcp@latest",
        "--executablePath",
        "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome"
      ]
    }
  }
}

What Metamcp makes of it:

{
  "mcpServers": {
    "chrome-devtools": {
      "type": "STDIO",
      "command": "npx",
      "args": [
        "-y",
        "chrome-devtools-mcp@latest",
        "--executablePath",
        "/Applications/Google",
        "Chrome.app/Contents/MacOS/Google",
        "Chrome"
      ]
    }
  }
}

I'd expect at least the last way to work properly.
Is there any way to get parameters with spaces in it into the parameters?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions