Pre-approve an MCP server's write tools for a scheduled action
Scheduled actions that write to a connected server like PostHog now run on their own instead of stopping for approval that nobody is there to give.
If you built a scheduled action that writes to a connected MCP server such as PostHog, it failed with a message saying it was not authorized to call that server, and it never ran. You could pre-approve a server's writes for your own chats, but actions had no way to do the same.
Pre-approval toggle in Edit Action
The Edit Action dialog now lists the MCP servers you have connected in the project, with a toggle to pre-approve each server's write tools. Turn it on, and the action's scheduled runs can call that server's write tools without waiting for you.
Chief shows only the servers you can call in the current project, so you won't pre-approve a server the action can't reach.
Pre-approvals set from chat
You can also ask Chief in chat to create or update an action that pre-approves a server's writes. Chief checks that the server is one you have connected before it proposes the change.
Editing an action that already carries an MCP pre-approval used to drop it without telling you. Chief now keeps it when you update the action, including for a server you have since disconnected.
Chief name on connected servers
When you connect an MCP server, its sign-in screen now names the app as Chief.
Open an action that writes to one of your connected servers, turn on the toggle for that server, and its next scheduled run will go through.