Agents & automations

Creating and managing workspace agents, and scheduling recurring automation runs.

These tools require member level. A connected agent can create native Sila agents and schedule recurring work, always on behalf of the authorizing user.

Managing agents

• sila_create_agent creates a workspace agent: a name, standing instructions in description, the channels it works in, integration apps (registry slugs like “gmail” or “linear”), skillIds from the workspace library, and attachedFiles as its knowledge base. Set isExternal: true for a locked-down agent that only works in external channels.
• sila_update_agent edits an existing agent. The authorizing user must be its creator, a workspace admin, or share a channel with it. Array fields (channels, apps, skillIds, attachedFiles) replace the full set rather than appending.
• sila_toggle_agent enables or disables an agent without deleting it. There is no delete via MCP; that stays with humans in the app.

Automations

Automations are scheduled runs owned by the authorizing user. Three kinds, in increasing weight:

Kind	What runs
script	Python in a sandbox, printing a JSON result
conditional_agent	Python gate that decides whether to fire an agent run
full_agent	A full LLM agent run from your agentPrompt

• sila_write_automation creates or updates one. Required on create: kind, name, and targetChannelIds, the smallest set of channels the automation needs to post to (prefer exactly one). That set also scopes each run’s read and post access, so keep it minimal. Schedule with 5-field cron in cron plus a timezone; leave cron null for a draft. Minimum cadence is every 5 minutes.
• sila_test_automation runs automation Python once in a sandbox right now, without scheduling anything. Test before you schedule.
• sila_list_automations (read level) shows your automations with status, last error, and next run time.
• Deleting an automation is not available over MCP. Disable it with enabled: false, or ask the user to delete it in the app.

Create a workspace: sila_create_workspace

Creates a brand-new Sila workspace owned by the authorizing user, with default channels set up. Useful when you’re helping someone start from nothing. Note that your current grant stays bound to the workspace picked at consent; the user reconnects to work in the new one.

For channel structure and invites, see Workspace admin.