modelcontextprotocol / modelcontextprotocol/servers

Whitespace issues in filesystem server

Open
#1,590 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug server-filesystem
Dominant language
TypeScript
Stars
90.5k
Forks
11.7k
Avg merge
2d 2h
Merged PRs (30d)
5

Description

Describe the bug

Working with the filesystem server - the assistant constantly creates trailing whitespace

Many linting tools and repos do not allow this - so then the assistant tries to clean up, often taking many iterations, and sometimes creating more issues in the process

To Reproduce
Steps to reproduce the behavior:

  1. edit/write files

Expected behavior
A clear and concise description of what you expected to happen.

clean edits, or at least the option to enforce that

Logs
If applicable, add logs to help explain your problem.

Additional context
Add any other context about the problem here.

it looks like this functionality was previously there and then was removed in https://github.com/modelcontextprotocol/servers/commit/b477af5c0404bf53d6643f73fda1e126dd27a935 - i really struggle to understand why

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Compare the filesystem server behavior with commit b477af5c0404bf53d6643f73fda1e126dd27a935, which the issue identifies as the point where this functionality was removed. Trace the edit/write path and determine whether trailing whitespace should be cleaned automatically or controlled by an option; done means edits meet the repository's whitespace expectations without repeated cleanup.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.