20 Legacy MCP Board tools to be deprecated

Twenty tools that read and write board content are now deprecated. They stop working on September 14, 2026. All functionality and additional functionality will be covered by the new canvas tools.

⚠️
Layout tools will be removed September 14, 2026
No tool has been removed and no behavior has changed. Every deprecated tool still works exactly as before, and it now tells the calling agent which Canvas Composer tool to use instead. But, as of Sept 14, the deprecated layout tools will stop working. Please ensure you are prepared by updating your skills, custom prompts, and workflows before Sept 14.

This is the follow-up to Canvas tools replace the layout tools. That post covered layout tools, but didn't talk about updates to diagrams, documents, and tables tools. Those tools will now be covered by the canvas tools.

Why

canvas_create_from_svg, canvas_read_as_svg, canvas_update_from_svg, and canvas_search already cover everything these twenty tools did, in one consistent format.

What is deprecated, and what replaces it

Board reads

Deprecated tool	Purpose	Replacement
`board_list_items`	List raw board items	`canvas_search` plus `canvas_read_as_svg`
`context_explore`	Discover high-level board content	`canvas_search` with `result_mode="overview"`
`context_get`	Read or summarize board content	`canvas_search` plus `canvas_read_as_svg`

Layout

Deprecated tool	Purpose	Replacement
`layout_get_dsl`	Load the legacy generic-layout DSL	`canvas_get_canvas_composer_skill`
`layout_create`	Create board items and connectors	`canvas_create_from_svg`
`layout_read`	Read supported items as layout DSL	`canvas_read_as_svg`
`layout_update`	Create, update, delete through a DSL diff	`canvas_update_from_svg`

Diagrams

Deprecated tool	Purpose	Replacement
`diagram_get_dsl`	Load the structured-diagram DSL	`canvas_get_canvas_composer_skill` plus `canvas_load_format_skill`
`diagram_create`	Create a diagram from structured DSL	`canvas_create_from_svg`
`diagram_get_mermaid_instructions`	Load Mermaid authoring guidance	`canvas_get_canvas_composer_skill` plus `canvas_load_format_skill`
`diagram_create_mermaid`	Create a diagram from Mermaid	`canvas_create_from_svg`
`diagram_update_mermaid`	Replace Mermaid content in a diagram	`canvas_update_from_svg`

Documents

Deprecated tool	Purpose	Replacement
`doc_get`	Read one document as Markdown	`canvas_read_as_svg`
`doc_create`	Create a structured document	`canvas_create_from_svg`
`doc_update`	Find and replace document content	`canvas_update_from_svg`

Tables

Deprecated tool	Purpose	Replacement
`table_create`	Create a data table and its columns	`canvas_create_from_svg`
`table_list_rows`	Read, filter, paginate table rows	`canvas_read_as_svg`
`table_get_latest_update_history`	Read a row's Latest Update history	`canvas_read_as_svg`, current state only
`table_sync_rows`	Insert or update table rows	`canvas_update_from_svg`
`table_update_view`	Switch table, grid, timeline, or kanban view	`canvas_update_from_svg`

Migrating

Search your skills, prompt files, custom instructions, and automations for board_list_items, context_, layout_, diagram_, doc_, and table_, then swap each name using the tables.
Delete any DSL syntax examples. Have your agent call canvas_get_canvas_composer_skill once per session and work from that spec.
For flowcharts, ERDs, and UML, layer canvas_load_format_skill on top for the the best diagramming results.
Use canvas_search to find what you need before reading, rather than listing every item on the board.

🚧
Reconnect, do not refresh
Some clients cache the tool list at the connector level. If your agent still reaches for a deprecated tool after you migrate, fully disconnect and reconnect the Miro MCP server. Refreshing the tool list is often not enough.

Two gaps we are still closing

Both are on our side and will be resolved ASAP:

canvas_read_as_svg returns a table row's current state, not its Latest Update history.
canvas_read_as_svg does not yet preserve the filtering and pagination behavior of table_list_rows.

If either matters to your workflow, tell us in the MCP feedback form so we can weigh it before removal.

For the current tool list and the format spec, see the Miro MCP tools reference.