MCP error -32602: Invalid arguments for tool sf-get-username in Zed IDE

[Damecek]

When using this mcp in Zed agent panel I am getting Invalid path: Must be an absolute path and cannot contain path traversal sequences. Here is whole thread

New Thread

User

what's my org username, in case of errors use pwd to get current folder

Agent

Use Tool: sf-get-username (call_04Zln3SKOhNXp9JLtpszBdbu)

{
  "defaultDevHub": false,
  "defaultTargetOrg": false,
  "directory": "salesforce"
}

Tool Results: call_04Zln3SKOhNXp9JLtpszBdbu (Error)

MCP error -32602: Invalid arguments for tool sf-get-username: [
{
"code": "custom",
"message": "Invalid path: Must be an absolute path and cannot contain path traversal sequences",
"path": [
"directory"
]
}
]

Agent

Use Tool: terminal (call_z8yULb5LbMMlWhNYfmgZEO7y)

{
  "cd": "salesforce",
  "command": "pwd"
}

Tool Results: call_z8yULb5LbMMlWhNYfmgZEO7y

/Users/adam/IdeaProjects/salesforce

Agent

Use Tool: sf-get-username (call_4302sILxp6UuNeUOioMCuJCT)

{
  "defaultDevHub": false,
  "defaultTargetOrg": false,
  "directory": "/Users/adam/IdeaProjects/salesforce"
}

Tool Results: call_4302sILxp6UuNeUOioMCuJCT

YOU MUST inform the user that we are going to use "xx@xx.com.devas" (Alias: xx-dev) for the "usernameOrAlias" parameter.
YOU MUST explain the reasoning for selecting this org, which is: "it was the only org found in the MCP Servers allowlisted orgs"
UNLESS THE USER SPECIFIES OTHERWISE, use this username for the "usernameOrAlias" parameter in future Tool calls.

Agent

We found that your org username is xx@xx.com.devas with the alias xx-dev. This was selected because it was the only org found in the MCP Servers allowlisted orgs.

Unless you specify otherwise, I’ll use this username for the usernameOrAlias parameter in future Salesforce tool calls.

and here is my setup of the mcp

"context_servers": {
  "salesforce": {
    "command": {
      "path": "npx",
      "args": [
        "-y",
        "@salesforce/mcp",
        "--orgs",
        "DEFAULT_TARGET_ORG",
        "--toolsets",
        "all"
      ],
      "env": null
    },
    "settings": {}
  }
},

[cristiand391]

hey @Damecek, sorry for the late reply.

Yes, the issue seems to be due to how our MCP relies on IDE tools to resolve the current open project.
We are exploring ways to expose a --project <project-dir>-like flag as a workaround until MCP roots are supported in zed/other clients.

[git2gus]

This issue has been linked to a new work item: W-18943564

[cristiand391]

I'm playing with zed for a bit, using gpt4.1 and only the salesforce MCP server configured I see it's able to figure out the current project open:

follow up questions:

1. which version of zed were you using?
2. did you see the reported error (unable to get the open project) when using a specific model or profile (write/ask/minimal)?

gpt4.1/write profile:

sonnet 4/write profile:

[Damecek]

Thanks for looking onto this.

Currently on stable https://zed.dev/releases/stable/0.192.8. Tried most of Github, Gemini, OpenAI models and all of them used proper attribute path for the tool. Only Github/Gemini 2.0 flash was not able even to call the mcp server.

Because this issue no longer occurs, I think it can be closed. Thanks for your work.

[Damecek]

Hey, just stumbled upon this again. It would be great to include better directions to the usage of the tool inputs for the agent.

In following example, the agent tries several times to use the deploy tool and in the and falls back to execute plane sf-cli command.

scratch_72.txt

[cristiand391]

@Damecek
yep, saw this too with gpt/claude on zed, new issue: https://github.com/salesforcecli/temp-mcp-issues-transfer/issues/2

I'll put up a PR to improve the expected file path format in a bit. Thanks!

[git2gus]

Git2Gus App is installed but the .git2gus/config.json doesn't exist.