Mcp servers: Conflict Between Cursor's `edit_file` and Filesystem MCP Server in Composer Agent Mode

Hey everyone, just wanted to share something I ran into while using the Cursor editor in Composer’s agent mode. It seems like there’s a bit of a conflict between Cursor’s edit_file function and the file operations provided by the Filesystem MCP Server. What I’ve noticed is that when you’re in agent mode, Cursor tends to prioritize the Filesystem MCP Server for file writing, rather than using its own edit_file functionality. Has anyone else experienced this or found a workaround?

Thanks for bringing this up! While I agree that MCP servers should not be able to override the build in tools, this probably isn’t something we limit in the code.

I’ll flag this to the team to fix in a future update!

can you share a request id where this happens?