Blueprints

Validate, compile, and assess Agent and Workspace Blueprints with read-only MCP tools

The Blueprint MCP tools expose six deterministic, read-only operations over local files. They use the same Blueprint engine as the CLI.

MCP can validate, compile, and assess. Blueprint mutation and process execution remain CLI-only: use dome blueprint apply, bind, run, or up. MCP does not write lockfiles or bindings.

validate and compile are local file operations. They do not call Dome and do not require a workspace context. assess reads live workspace state and requires an active workspace context, but never mutates it.

Paths are local to the machine running dome mcp serve.

Agent Blueprint tools

dome_blueprint_validate

Strictly validate a local Agent Blueprint and return its deterministic Revision digest. This does not call Dome or write files.

Parameter	Type	Required	Description
`file`	string	No	Agent Blueprint source path. Default: `dome-agent.yaml`.

The response contains valid: true and digest.

dome_blueprint_compile

Compile a local Agent Blueprint into canonical, workspace-independent Revision JSON. The tool returns the artifact and does not write dome-agent.lock.json.

Parameter	Type	Required	Description
`file`	string	No	Agent Blueprint source path. Default: `dome-agent.yaml`.

dome_blueprint_assess

Assess an Agent Blueprint source or compiled Revision against the active workspace. The response contains observed constraints, exact operations, held permissions, checks, resolved resources, and blockers.

Parameter	Type	Required	Description
`file`	string	No	Agent Blueprint source path. Default: `dome-agent.yaml`. Ignored when `revision` is supplied.
`revision`	string	No	Compiled Agent Revision lockfile path.
`bindings`	string	No	Bindings path. Default: `dome-agent.bindings.json` beside `file`.

Requires an active workspace context. The tool reads workspace state and validates projected Rules, but does not apply the returned operations.

Workspace Blueprint tools

dome_blueprint_workspace_validate

Strictly validate a local Workspace Blueprint and return its deterministic Revision digest plus counts for Gateways, tools, models, and model pools. This does not call Dome or write files.

Parameter	Type	Required	Description
`file`	string	No	Workspace Blueprint source path. Default: `dome-workspace.yaml`.

dome_blueprint_workspace_compile

Compile a local Workspace Blueprint into canonical, workspace-independent Revision JSON. The tool returns the artifact and does not write dome-workspace.lock.json.

Parameter	Type	Required	Description
`file`	string	No	Workspace Blueprint source path. Default: `dome-workspace.yaml`.

dome_blueprint_workspace_assess

Assess a Workspace Blueprint source or compiled Revision against the active workspace. The response reports missing declared Gateways, tool connections, model connections, model pools, and attachments; method drift; executable permissions; and blockers. It never creates or changes a resource.

Parameter	Type	Required	Description
`file`	string	No	Workspace Blueprint source path. Default: `dome-workspace.yaml`. Ignored when `revision` is supplied.
`revision`	string	No	Compiled Workspace Revision lockfile path.
`bindings`	string	No	Bindings path. Default: `dome-workspace.bindings.json` beside `file`.

Requires an active workspace context. Unlike the CLI lifecycle, this MCP tool has no env_file parameter. Environment-backed values needed to create a missing resource may therefore be reported as unset; use dome blueprint workspace assess --env-file ... for an explicit env file.

What stays in the CLI

Use the dome blueprint CLI for:

scaffolding and adoption
formatting and writing lockfiles
creating or refreshing bindings
applying Agent or Workspace Blueprint operations
provisioning agent credential envelopes
running a local child process
project fan-out and up

There are no MCP tools for Blueprint mutation or runtime supervision, and there is no public Blueprint API.