modelcontextprotocol / modelcontextprotocol/servers
Support read-only paths in filesystem MCP with npx
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 90.5k
- Forks
- 11.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 5
Description
Is your feature request related to a problem? Please describe.
Read-only paths only seem supported when running via docker.
Describe the solution you'd like
Allow read-only of certain paths when running with npx.
Describe alternatives you've considered
Docker, which works but I'd like the npx option, if possible.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare how read-only paths are configured and enforced for the Docker and npx filesystem MCP launch modes. Start with the filesystem server's npx entry point and related configuration; done means selected paths are read-only when launched with npx, with behavior matching the Docker mode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100