triggerdotdev
bug: AI keeps trying to deploy new versions with MCP
Provide environment information
Sometimes when you ask it to fix an issue from logs in trigger, it tries to deploy the solution.
This is a big no-no for me, however I appreciate all the other features of the MCP, they are incredibly helpful.
So I've added some options to make the MCP server feel a bit more in control as to what it can do. See here #2539
Specifically it's the option to add a read only mode, so it can review whatever it wnats but NEVER makes changes to my account (or triggers tasks).
Then, if that's too restrictive (e.g. you want a closed loop of it triggering a task to fix an issue then checking the results), I've added --disable-deployment which ONLY disables deployment specific commands. So it can do everything else except deploy a new version.
Perhaps in future it might be good to have a --enabled-tools which simply can list what tools are presented, but that's not necessary for me as I've only observed issues with deployments.
Describe the bug
AI goes beyond the scope of what I want with the MCP.
Reproduction repo
NA
To reproduce
Just ask AI to do stuff with the MCP and fix things - it will try to deploy at some point
Additional information
No response
I've added a PR add this feature: https://github.com/triggerdotdev/trigger.dev/pull/2539