Edit an existing project through a scoped filesystem connection
At a glance
A developer gives Claude Desktop relevant file paths, then feeds build errors back until the generated changes compile. This workflow is listed under Existing Codebases, MCP, Build Feedback.
- Agents / tools
- Claude Desktop, Filesystem MCP Server
SourceBuilding a tool for these workflows? See weekly rates.
What they did
1) Have Claude Desktop, Node 24+, and the project's build tools. In claude_desktop_config.json, configure the official filesystem server as {"mcpServers":{"filesystem":{"command":"npx","args":["-y","@modelcontextprotocol/server-filesystem","/absolute/project/path"]}}}, replacing the final path with the project directory and merging with existing server entries. Restart Desktop and enable its filesystem tools for the conversation. 2) Give Claude the absolute paths of a few existing files showing where the change belongs and describe the concrete task. Let it inspect those files and edit or add the relevant code. 3) Run the project's build yourself, paste any errors into the conversation, and ask Claude to correct them. Repeat until the build succeeds. 4) Read the resulting changes to check the requested behavior and existing style. A reply describes extending this into phases: save a plan in the project, implement one phase per new chat, then review that phase before continuing.
How it went
The commenter reports using this with TypeScript and C#, usually returning a couple of build errors for correction.
Worth knowing
The filesystem connection needs an allowed directory. A reply warns that an agent can claim completion while the code still fails; verification remains necessary.
