Which packages would you like to change?

• @eslint/compat
• @eslint/config-array
• @eslint/config-helpers
• @eslint/core
• @eslint/mcp
• @eslint/migrate-config
• @eslint/object-schema
• @eslint/plugin-kit

What problem do you want to solve?

Putting instructions to the agent in the response in the form of "Do not automatically fix these issues..." or any other instructions isn't ideal - it might conflict with instructions that the user has specified. For example, I provide my claude code with the eslint MCP precisely so that it can fix issues that eslint finds as it goes. Because of this instruction on every response from the MCP server, the agent can get very confused.

Instructions for the agent properly belong outside of any MCP response. If you want to compose the MCP response with instructions not to automatically fix, (or conversely TO automatically fix) then you should do that elsewhere in your agent's instructions/system prompt/AGENTS.md/etc.

What do you think is the correct solution?

Perhaps a good solution would be to have a CLI flag to disable this? I think conceptually it'd just be better to not have it there at all, but disabling for people who DO want to auto-fix (or want other follow-up by the agent) would also work.

Participation

• I am willing to submit a pull request for this change.

Additional comments

I could probably write a pretty quick fix across mcp-server.js and the CLI to pass an arg, but not sure what the "standard" way of doing that in the project would be, etc. If you think it's a good idea and would like me to take a stab at it, I can put the time in.