Skip to content

fix: mcp scan path default - #229

Merged
sairenchristianbuerano merged 2 commits into
mainfrom
fix/mcp-scan-path-default
Sep 25, 2026
Merged

sairenchristianbuerano merged 2 commits into
mainfrom
fix/mcp-scan-path-default

Conversation

@sairenchristianbuerano

Copy link
Copy Markdown
Collaborator

No description provided.

…L scanning

The scan tool required a path described only as a local directory. Run from
the published container that combination fails: the client sends a path from
its own machine, which does not exist inside the container, so the first scan
a new user attempts errors out.

Make path optional, defaulting to the server's working directory, which the
container image already sets to the mounted repository. Also name the GitHub
URL form in the description - ingestion has always resolved remotes, but the
schema never said so, leaving the capability undiscoverable to a model.
The first version of this change defaulted an omitted path to the process
working directory. That is wrong outside a container: MCP clients choose the
working directory, and Cursor launches servers from the user's home, so an
omitted path would have walked everything they own.

Default only where the directory is known to be right. The image sets
WORKDIR and TRUSTABL_MCP_DEFAULT_PATH to the mount point; nothing else sets
it, and without it the server asks for a path instead of guessing. The error
names the GitHub URL form, which ingestion has always accepted but the schema
never advertised.

Drops -w from the install config, since WORKDIR now carries it.
@sairenchristianbuerano
sairenchristianbuerano merged commit 1f90791 into main Sep 25, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants