 runs an Agent (Charm) completion automatically against a document. A time-triggered Action fires on a schedule — a recurring calendar rule or a fixed interval — and each firing is recorded as a 

. Use Actions to keep a document fresh on a cadence: a daily summary, an hourly digest, a weekly report.

The Action server lets an external application create, configure, and operate Actions, and inspect their run history.

 triggers; folder triggers (run when an entry lands in a folder) are planned and will arrive as a 

 tool — the read, run, and run-history tools above already work for any Action regardless of trigger.

 (epoch milliseconds) optionally bound when scheduling begins and ends.

: the chosen Agent produces output into a document. 

Each firing — scheduled or manual — creates a run that moves through 

 report status, timing, any error, and the document the run produced or edited. Run and schedule times in responses are rendered in your profile timezone (UTC if you haven't set one).

 — Read and edit the documents Actions produce.

Run Charms on a schedule — create time-triggered Actions, run them on demand, and inspect every run.

Tool	What It Does
`list_actions`	List the user's Actions
`get_action`	One Action's full configuration and schedule state
`create_time_action`	Create a time-triggered Action
`update_time_action`	Change an Action's name, agent, schedule, or document action
`pause_action`	Stop automatic runs
`resume_action`	Re-enable automatic runs
`delete_action`	Delete the Action and its run history
`run_action`	Run the Action now (manually)
`list_action_runs`	The Action's execution history, most recent first
`get_action_run`	One run's detail
`cancel_action_run`	Cancel an open run
`delete_action_run`	Delete a run from history

Action MCP Server

Tools

Triggers

The Document Action

Runs

Lifecycle Rules

Patterns

Next Steps