On this page

MCP Tools

The MCP tools are the operations an agent can call through MCP access, each gated by the token's scope.

Note

We recommend the workspace plugin for anything that changes your workspace, and a Read token wherever the plugin isn't in use.

How to read the tables

Column	Meaning
Scope	Read: every token gets it. Read + write: only a token with that scope
Discard undoes it	Whether discarding the token's working copy reverses what the tool changed. No means the change is permanent

Important

Changed 30 September 2026: no tool publishes a board. Publish from Publish.

delete_nodes reads Mostly: a discard restores the nodes and their edges. Child nodes stay moved out of a deleted node, and a layer board it owned stays a standalone board.

update_nodes and update_edges change only the fields you send. A node you rename keeps its archetype, parent, tags and the layer board it drills into; pass null to clear a field on purpose.

Boards and layers

Tool	What it does	Scope	Discard undoes it
`get_board_tree`	One level of layer boards under a board, with their drill paths	Read	—
`get_child_boards`	The layer boards a board's nodes drill into	Read	—
`get_parent_board`	The board whose node drills into this one	Read	—
`get_workboard_details`	A board with all its elements and styles	Read	—
`get_nodes`	A board's nodes, all or under one parent	Read	—
`get_edges`	A board's edges, filtered by node	Read	—
`find_elements`	Layers, nodes, edges and aspect rows under a root, by name	Read	—
`get_archetypes`	The organization's node and edge archetypes	Read	—
`get_system_view`	A view folded across the apps on a board, from each app's aspects	Read	—
`trace_impact`	Everything that depends on an element, across layers and apps	Read	—
`trace_dependencies`	Everything an element depends on, across layers and apps	Read	—
`find_path`	The shortest dependency route from one element to another	Read	—
`plan_grouping`	A review of a board's containment against how its elements connect	Read	—
`create_nodes`	Add nodes to a board	Read + write	Yes
`update_nodes`	Rename, describe, re-parent, retag or resize nodes	Read + write	Yes
`create_edges`	Connect nodes	Read + write	Yes
`update_edges`	Rename, describe or retag edges	Read + write	Yes
`apply_diagram_info`	Set a board's title, summary and notes	Read + write	Yes
`create_board`	Add a layer board under a node	Read + write	Yes
`delete_nodes`	Delete nodes and the edges wired to them	Read + write	Mostly (see above)
`delete_edges`	Delete edges	Read + write	Yes
`create_context_board`	Draw a standalone context board that answers a question	Read + write	No
`delete_context_board`	Delete a context board and everything on it	Read + write	No
`create_decision_board`	Add a decision board, born with its record as a draft `ADR-n`; names what it supersedes	Read + write	No
`get_decision`	A decision board's record: number, status, owner, what it supersedes	Read	—
`propose_decision`	Put a draft decision forward as proposed; only a person accepts it	Read + write	No
`propose_archetypes`	Propose new or changed archetypes for an admin to review	Read + write	No

Important

Changed 6 October 2026: get_board_tree returns the board you name and its direct layer boards, not the whole tree.

get_board_tree returns up to 100 layer boards per call. Each one carries childCount, the number of layer boards directly beneath it. To go deeper, call it again with a child's slug, or pass depth: 2 for two levels at once. When more is above 0, pass offset to read the next page.

Styling and layout

Tool	What it does	Scope	Discard undoes it
`style_signals`	The facts a styling pass plans from	Read	—
`match_icons`	Icons that match plain names	Read	—
`apply_semantic_styles`	Style nodes, edges and containers by role	Read + write	Yes
`apply_icon_shape_styles`	Set node icons and shapes	Read + write	Yes
`apply_composition`	Set a board's arrangement, reading direction and spacing	Read + write	Yes

Aspects

Tool	What it does	Scope	Discard undoes it
`list_aspects`	A board's aspect rows, across every kind or one	Read	—
`get_aspect`	One aspect row in detail	Read	—
`get_node_aspects`	The aspect rows a node owns or is referenced by	Read	—
`author_tables`	Add or change the intended database tables of an app board	Read + write	Yes
`author_endpoints`	Add or change the intended API endpoints of an app board	Read + write	Yes
`author_pages`	Add or change the intended pages of an app board	Read + write	Yes
`author_channels`	Add or change the intended event channels of an app board	Read + write	Yes
`author_boundary_rules`	Add or change the boundary rules over a board's nodes	Read + write	Yes

Insights

Tool	What it does	Scope	Discard undoes it
`list_insight_skills`	The insight templates in your organization	Read	—
`get_insight_skill`	One template's full method	Read	—
`list_insights`	A board's batches of insights	Read	—
`get_insight`	One insight with its evidence and trail	Read	—
`create_insight`	Record a batch of insights on a board	Read + write	No
`promote_insights`	Turn reviewed insights into draft work items	Read + write	No

An insight whose trail came from trace_impact, trace_dependencies or find_path can carry that trace. Pass it as the insight's traceAsk, and the insight offers Ask this again in Dependencies.

Work items and epics

Tool	What it does	Scope	Discard undoes it
`list_work_items`	A board's work items	Read	—
`get_work_item`	One work item in full	Read	—
`list_epics`	The workspace's epics	Read	—
`create_work_item`	Draft a work item on a code-bound board	Read + write	No
`update_work_item`	Revise a draft or needs-clarification work item	Read + write	No
`transition_work_item`	Move a work item through its lifecycle	Read + write	No
`assign_work_item`	Assign a work item, or clear its assignees	Read + write	No
`set_work_item_epic`	File a work item under an epic, or take it out	Read + write	No
`delete_work_item`	Delete a work item	Read + write	No
`create_epic`	Create an epic	Read + write	No

Apps, sources and skills

Tool	What it does	Scope	Discard undoes it
`list_source_bindings`	The repos and documents that feed a board	Read	—
`get_source_content`	Read a bound source document	Read	—
`get_skill_profile`	An app board's type and active skill modules	Read	—
`list_skill_library`	The skill modules an app board can activate	Read	—
`convert_node_to_app`	Make a landscape node a repo-bound app	Read + write	No
`bind_reference_source`	Attach a document to a board as reference context	Read + write	No
`configure_skills`	Turn an app board's skill modules on or off	Read + write	No

Connected documents

Tool	What it does	Scope	Discard undoes it
`search_connected_documents`	Find a Google Docs, Confluence or Notion page, or a Jira issue	Read	—
`read_connected_document`	Read one by its link, or by the id a search returned	Read	—

Both use the personal connections of the person who generated the token, so the agent sees only what that person's accounts show.

Hub, publishing and playbooks

Tool	What it does	Scope	Discard undoes it
`get_hub_status`	What a board's hub shows, starting with its attention queue	Read	—
`list_playbooks`	The playbooks you can start, and the live runs	Read	—
`get_playbook`	One playbook's definition	Read	—
`get_playbook_run`	A run's steps and what proved each one	Read	—
`get_playbook_skill`	A playbook's instructions, for an agent that runs it	Read	—
`start_playbook`	Start a playbook run	Read + write	No
`report_playbook_step`	Record what the board can't observe on a run you started	Read + write	No
`draft_playbook`	Save a new playbook, disabled	Read + write	No

get_hub_status returns what the hub shows by default, as counts and short lists. On an app board that is the attention queue, work items by status, insight counts, each repo's freshness and scheduled-run health, analysis coverage, and each aspect kind's figures. On the root board it is fleet attention app by app, totals across apps, the aspects across systems, and recent pushes. Lists stop at 5 rows and 10 apps, and say how many more there are. Ask for more with include:

`include`	Adds
`readiness`	Each app's build-readiness bar
`changes`	What shipped, change periods with no work item, contract changes and the systems that depend directly on that app, unreviewed flags with their paths, the most-changed services, and the people and agents behind the commits
`scorecard`	The System scorecard cells, on the root board
`scheduledRuns`	The newest scheduled runs of each repo
`rows`	Every row of every list, with no limit

changes and scorecard count over since, or over the workspace's default hub period when it is left out. Given a playbook run, get_hub_status counts as that run's visit to the hub.

draft_playbook needs a plan with custom playbooks (Pro).

Change record

Important

Changed 12 October 2026: get_hub_briefing is gone; get_change_diary reads the same weeks as diary entries.

Tool	What it does	Scope	Discard undoes it
`get_change_diary`	One week of changes under a board, told as pieces of work	Read	—
`list_change_periods`	The change periods under a board, newest first	Read	—
`get_change_period`	One change period in full	Read	—
`list_change_rules`	The change rules every period answers, and what answers each	Read	—

These read the change periods the code plugin's /changes records. get_change_diary returns one week as the Changes screen's diary shows it, on an app board or the root. Pass at, any date in a week, or a periodId to read that week; without either it reads the newest week with commits.

Its entries come ranked, flagged first. Each has its headline and what it did, its app and the nodes it landed on, and who did it with which coding agent. It also has the rules it hit with their impact and the work items it cites. It gives when its first and last commits landed, empty for an entry with no days of its own. On the root board, an entry that changed a contract names the systems that depend on its app, two hops out.

Such an entry also names what in other apps depends on what it touched: each app's clients, subscribers and readers, and the endpoints, events or tables they reach. A Boundaries entry names each boundary rule that broke, broke and holds again, or holds again, and how many of the app's rules hold after the last sync. Beside the entries come the row of weeks with their commits, the apps that worked that week and the apps with nothing recorded. Each app that worked gives its coupling now and at the previous sample, and what its week did not check.

list_change_periods lists one repo's periods on an app board, or every app's on the root, 20 at a time, or fewer with limit. Pass the nextAfter it returns as after for the next page. Each row names the headlines of the period's pieces of work.

get_change_period takes a periodId from that list and the same board. It returns each rule's answer with its names and paths, and each piece of work with its headline, nodes, people, rule hits with their impact and cited work items. Each piece of work also gives when its first and last commits landed. It also returns each person with their agent, each service with its commits, and the work items behind the period. For Boundaries it names the rules that moved.

list_change_periods counts over since, or over the workspace's default hub period when it is left out, the same as get_hub_status. A token limited to one board reads only that board's periods.

Working copy

Tool	What it does	Scope	Discard undoes it
`get_write_session`	What's currently uncommitted	Read + write	—
`preview_write_session_commit`	What committing would land, before doing it	Read + write	—
`discard_write_session`	Undo the whole working copy, row by row	Read + write	—
`commit_write_session`	Accept the working copy with a reason, and clear the undo log	Read + write	—

commit_write_session takes the reason as title and the longer why as summary; both are stored with the commit. A token's commit creates no work items. You can also accept or discard a token's working copy in the portal, under Plugin pushes awaiting commit. After a commit, nothing in it can be undone. See Review what an agent changed.

What no token gets

No token gets a tool that needs a person in the conversation, such as posting to Slack, or one that provisions new infrastructure.

Last updated November 6, 2026

MCP Tools

How to read the tables

Boards and layers

Styling and layout

Aspects

Insights

Work items and epics

Apps, sources and skills

Connected documents

Hub, publishing and playbooks

Change record

Working copy

What no token gets

Product

Resources

Company

Legal