Four skills told Claude the Braze MCP cannot build a Canvas. That was true of seventy tools and false of the seventy-first
0.41.0 added braze-operator without going back through the skills that already had an opinion about what the Braze MCP can reach. Every Canvas skill in Orbit said, correctly, that no Braze API writes a Canvas — and then drew the wrong conclusion from it, that the MCP is therefore not a path to one. send_operator_prompt is an MCP tool that drives the dashboard in a live browser session, so the server can build a Canvas even though none of its structured tools can. Three skills now carry that carve-out. One of them was also citing a function count from the wrong server entirely.
What shipped
•Fix — braze-claude-in-chrome-build cited 43 functions in its dead-ends table. That is the deprecated local Braze MCP server, retired in August 2025; the hosted server exposes 71 tools, verified live on 8 September. The row's actual verdict was right either way — zero of the 71 write a Canvas — but the number sent anyone checking to the wrong server. It now names Operator as a browser path reached through the MCP, and keeps this skill for the case where you need to watch each step.
•Fix — braze-canvas-creator upgraded its Braze MCP note from documentation to observation and gained the carve-out. Its answer to "but Braze has an MCP now" also stops saying the MCP added segment writes without qualification: it added a segment writer that cannot filter on any custom attribute, which for most B2B and product-led audiences is the same as not having one.
•Fix — braze-canvas-qa said a Canvas finding cannot be fixed without the dashboard. Fixing one still means the dashboard, but not necessarily your hands — Operator drives it. The skill points there, with the reminder that a QA pass is not a licence to launch.