Connection string is not retained when LLM tries to reconnect

[GaurabAryal]

If I pass connection string in the launch command or define it in an env var, when Cursor calls the Connect tool the second time (with some amount of delay between the first successful connection attempt), sometimes MCP doesn't appear to know what the connection string is.

[nirinchev]

We recently resolved #80, which appears to be somewhat related here. Do you think you can test with latest main and confirm you're still seeing this problem?

[GaurabAryal]

@nirinchev – Pulled main and tested again - it does appear to be better for sure!

Though I'm wondering why the LLM cannot fetch this from the launch command on the first attempt to connect?

[nirinchev]

This is not the correct syntax for providing a connection string. Right now we don't take in positional arguments, so you'll need to pass in the arg name like --connectionString mongodb://localhost:58321

[gagik]

By the way the npx -y /..../dist/index.js seems incorrect and not sure how that works out but you're probably looking for this
in Cursor:

 "MongoDB": {
      "command": "< your full path >/dist/index.js --connectionString mongodb://localhost:58321",
    }

and in VSCode:

 "MongoDB": {
      "type": "stdio",
      "command": "< your full path >/dist/index.js",
      "args": ["--connectionString", "mongodb://localhost:58321"]
    }

[nirinchev]

I think the args in vscode should be separate, no? Like "args": [ "--connectionString", "mongodb://localhost:58321" ]