I ran into a snag setting up an automation using the Slack MCP. The issue is that t*he Bot token added in as MCP data isn't available to automations*. The workaround is to add

SLACK_BOT_TOKEN

as a secret with the bot token but that isn't as easy as it could be. If the MCP data can't be made available to automations then I suggest a small UI/UX fix to pre-select checkboxes to "Save as secret" for Slack (maybe Github token as well). I think it would improve the MCP -> Setting up automation flow a lot. https://github.com/OpenHands/agent-canvas/issues/926

@fierce-account-55183 thoughts on how best to fix this? Adding the token as a secret is a bit of an anti-pattern--the whole point of MCP is that it's hiding your secrets from the agent. But that might be the hack for now