MCP Resources

Dagu exposes MCP resources for DAG specs, Markdown Wiki pages, DAG-run details, scheduler and step logs, and built-in references.

Resource URIs

URI	MIME type	Description
dagu://reference/authoring	text/markdown	Guidance for writing and editing Dagu DAG YAML through MCP.
dagu://reference/tools	text/markdown	Compact tool reference for dagu_read, dagu_change, and dagu_execute.
dagu://reference/notifications	text/markdown	How run-completion notifications work over MCP resources.
dagu://dags/{name}/spec	application/yaml	Current YAML spec for a DAG.
dagu://wiki	application/json	Wiki page tree across accessible workspaces.
dagu://wiki/{workspace}	application/json	Wiki page tree for default or one named workspace.
dagu://wiki/{workspace}/{path}	text/markdown	Current Markdown content for one Wiki page.
dagu://runs/{name}/{dagRunId}	application/json	Current DAG-run details.
dagu://runs/{name}/{dagRunId}/logs	application/json	Scheduler log and step log metadata.
dagu://runs/{name}/{dagRunId}/steps/{stepName}/logs	application/json	Standard output and standard error for one step.

Use dagu_read with a uri to read any resource directly:

{ "uri": "dagu://reference/tools" }

{ "uri": "dagu://dags/nightly-report/spec" }

Wiki page resources use an explicit workspace so an identical path in two workspaces is unambiguous. Encode a nested Wiki page path as one URI segment:

dagu://wiki/operations/runbooks%2Frestart

The dagu_read list and search targets return these canonical URIs. dagu://wiki and workspace collection resources accept the same page, perPage, flat, sort, order, and prefix query parameters as target=wiki. Wiki page lists accept up to 200 entries per page.

The dagu://docs collection and page URIs remain available as deprecated exact aliases for existing MCP clients.

In tree mode, pagination selects direct children of the workspace or prefix; a returned directory still contains its descendants. In flat mode, pagination selects individual Wiki pages.

For example, this resource lists the newest individual Wiki pages below runbooks in the operations workspace:

dagu://wiki/operations?prefix=runbooks&flat=true&sort=mtime&order=desc&perPage=20

Log resources accept query parameters supported by Dagu's log readers, such as tail=100:

dagu://runs/nightly-report/20260522T010000/logs?tail=100

Run Subscriptions

dagu_execute returns run and log resource links when a run can be identified.

Clients that support MCP resource subscriptions can subscribe to:

dagu://runs/{name}/{dagRunId}

Dagu sends a resource update notification when the run reaches a terminal state:

• success
• failed
• aborted
• partial success
• rejected

Clients without resource subscription support should poll dagu_read with target=run and the same name and dagRunId.

MCP App Run Inspector

Hosts that support MCP Apps can render run-related dagu_read and dagu_execute results in an interactive inspector. It provides run and step status, scheduler and per-step logs, refresh, stop, and retry.

Built-in Prompts

Dagu also exposes MCP prompts for common workflows:

Prompt	Arguments	Purpose
dagu_create_dag	goal	Draft, validate, and apply a new DAG using Dagu's compact MCP tool surface.
dagu_edit_dag	name, change	Read an existing DAG spec, make a scoped edit, preview validation, then apply.
dagu_create_wiki_page	workspace, path, goal	Draft, preview, and create a Markdown Wiki page.
dagu_edit_wiki_page	workspace, path, change	Read a Markdown Wiki page, make a scoped edit, preview, then apply.
dagu_debug_failed_run	name, dagRunId	Read a run and logs, explain the likely failure, then offer retry or stop when appropriate.

The deprecated dagu_create_doc and dagu_edit_doc prompts forward to their Wiki equivalents.