When I explored the official tableau-mcp source in an earlier experiment, one area caught my attention: workbook tools under src/tools/desktop/workbook/.
The screenshot and original LinkedIn post record that historical observation. This article describes the design idea I took from it; it does not assert that those tools are currently available to every developer.
Three names that made the workflow interesting
The tool names recorded in my original analysis were:
get-workbook-xml
batch-create-and-cache-sheets
apply-workbook
Read together, they suggest an authoring workflow with separate steps: inspect the existing workbook, prepare new sheets, then apply changes. That is a useful design distinction for an agent: reading, creating and committing changes are different operations.
This is my interpretation of the names and the historical source observation. It is not proof of public access to a Desktop Agent API, and I am not claiming I successfully executed that internal workflow.
Why it matters for cwtwb
There are several ways to approach AI-assisted BI. One works with an active application. Another generates a workbook artifact programmatically. cwtwb focuses on the latter through a Python SDK and MCP-facing capabilities.
Both approaches raise the same practical questions: what did the agent change, can we inspect the result, and is the calculation correct?
An official project exploring workbook authoring is relevant technical context. It is not an endorsement of Datacooper or evidence of market leadership.
My work at Datacooper is to turn that authoring direction into repeatable examples and checked artifacts. A future paid MCP should earn its value by helping users complete BI tasks, not merely by exposing more tool names.
Project context: Tableau MCP repository.
Originally shared in this LinkedIn post.
Explore cwtwb on GitHub, the case replication repository and Datacooper.
Top comments (0)