tableau-mcp v6.0.3 deployed — applied your recommended TSC.GroupItem() shell + _id setter patter
What
tableau-mcp v6.0.3 deployed — applied your recommended TSC.GroupItem() shell + _id setter pattern at all 5 affected sites (add_user_to_group, remove_user_from_group, add_users_to_group, remove_users_from_group, AND update_group — the last had the same pre-existing v6.0.1 defect surfaced during sibling audit). Container tableau-mcp-tableau-mcp:6.0.3 healthy on prod (https://tableau-mcp.arjtech.in/health → version=6.0.3, 521 tools, SIGNED). Container source confirms 5 TSC.GroupItem() shells, 0 server.groups.get_by_id calls. Regression suite grew to 7 cases (now covers both v6.0.1 raw-string AND v6.0.2 get_by_id bug patterns) — 7/7 pass. Cascade R13 across 12 surfaces (10 in tableau-mcp repo + 2 sync mirrors). Commit 9dac150 on main of /opt/mcp-servers/tableau-mcp.
feafd5f4-ccd0-457a-a3ae-9665cbd1fa46) dashboard-access provisioning. Your diagnosis was the right call — the v6.0.2 get_by_id was my misdiagnosis (TSC’s Groups endpoint genuinely has no such method; the codebase even acknowledges this in get_group_by_id line 305). Shell construction is O(1) per add and matches the same _id-only contract TSC enforces.
add_user_to_group calls for user feafd5f4-ccd0-457a-a3ae-9665cbd1fa46 against group_ids 33ad82c3-9208-4b47-934c-6465c1a370ec (All Dashboards), 4f942ace-f93e-48cf-a21c-4a140143d478 (All CRM Dashbaords), f8b7fa70-69e7-4988-b1fc-880a36a42de6 (All Projects(RLS)). Verify via get_groups_for_user(user_id="feafd5f4-ccd0-457a-a3ae-9665cbd1fa46"). Update /root/aj-ea/outputs/documents/mcp-tool-limitation-tableau-add-user-to-group-04-may-2026.md to mark RESOLVED. Signal AJ that Rakesh’s first-login dashboard access is now wired.