Tableau
Business intelligence and visualization platform (514 MCP tools) consuming Snowflake data for CRM dashboards and reporting.
Current State
Tableau with session-based MCP server (514 tools, v6.0, fully audited). End of the enterprise data pipeline: Salesforce → Fivetran → Snowflake → Tableau/Power BI. Provides CRM dashboards, sales analytics, and operational reporting for Runwal Group.
Key Learnings
-
runwal-fy-2026-27-strategic-direction-consolidate-entire — FY 2026-27 strategic direction includes Tableau consolidation
-
mcp-upgrade-api-version-hardcodes — API version hardcodes in Tableau MCP
-
runwal-group-business-context-indian-real-estate-developer — Runwal Group business context
-
mcp-namespace-collision-health-check-collides-across-10-serv — The tool name
health_checkis registered in 10 MCP servers simultaneously: switchy-mcp, boostspace-mcp, sharepoint-mcp -
mcp-namespace-collisions-generic-crud-names-across-4-platfor — Six additional generic tool names collide across 2-4 servers:
list_users/get_user/delete_user/list_groups/`get_g -
health-check-tool-collides-across-10-mcp-servers — The tool name
health_checkis registered across 10 simultaneously-active MCP servers: switchy-mcp, boostspace-mcp, sha -
mcp-generic-crud-names-collide-across-2-4-servers — 11 generic CRUD tool names collide across 2-4 MCP servers:
list_users(tableau, fivetran, blue, late-social), `get_use -
aj-ea-core-mcp-servers-permanently-registered — Salesforce, Snowflake, Fivetran, and Tableau are permanently registered for the aj-ea workspace in
~/.claude.jsonunde -
operational-mcp-servers-were-duplicated-across-three-workspa — The 4 permanent operational MCP servers (Salesforce, Snowflake, Fivetran, Tableau) were found registered in /root/aj-ea
-
mcp-duplicate-registrations-removed-from-aj-workspace — The 4 permanent operational MCP servers (Salesforce, Snowflake, Fivetran, Tableau) were found duplicated in /root/aj-wor
-
mcp-server-registrations-bloat-context-of-unused-workspaces — MCP servers registered in
~/.claude.jsonunder a workspace path load into that workspace’s context every session, even -
salesforce-mcp-not-permanently-registered-in-aj-ea — Despite MEMORY.md claiming Salesforce, Snowflake, Fivetran, and Tableau are permanently registered under projects./root/
-
salesforce-mcp-registration-missing-from-aj-ea-workspace — MEMORY.md claims aj-ea has 4 permanent workspace-default MCP servers (Salesforce, Snowflake, Fivetran, Tableau) but no s
-
aj-ea-workspace-mcpservers-empty-despite-memory-md-claim — The
/root/aj-eaproject in~/.claude.jsonhadmcpServers: {}(completely empty) despite MEMORY.md asserting 4 perm -
aj-ea-snowflake-fivetran-tableau-mcp-also-missing-permanent — When investigating the missing Salesforce MCP, only Salesforce was registered. Snowflake, Fivetran, and Tableau — also c
-
aj-ea-4-permanent-mcp-servers-registered-09-apr-2026 — All 4 workspace MCP servers for
/root/aj-eaare now permanently registered in~/.claude.jsonunder `projects./root/a -
permanent-mcp-servers-are-exactly-8 — The definitive permanent MCP set (user-scope, both workspaces, every session) is: excalidraw, graphiti-mcp, hostinger-ad
-
internal-platform-vs-product-eliminates-40pct-architecture-s — When the deployment target is an internal enterprise platform (not a SaaS product), explicitly drop: multi-tenancy, bill
-
r-dash-m11-ai-agents-v1-must-not-deferred — M11 AI Agent Fabric was locked as a v1 MUST, not deferred to v1.5. Project 120 agents are native to the R-Dash dashboard
-
r-same-repo-and-infra-location — R-Same (Runwal’s internal BI platform, Redash-inspired Tableau replacement) lives at
/opt/infra/r-same/on the VPS and -
mcp-framework-fastmcp-3-task-surface-r33-9th-cascade-surface — Two reusable findings from Fivetran v19.1.5 → v19.1.7 upgrade — now canonical in Bible main (PR #19 squash
9c41f847on -
snowflake-mcp-v22-retro-bible-law-11-r38-r40-upstream-verifi — Snowflake MCP v22 retrospective — Bible Law 11 (R38-R40) institutional learning
-
tableau-cloud-web-authoring-two-step-viewerauthoring-transit — Tableau Cloud Web Authoring is a TWO-STEP transition — canvas DOM at TOP-LEVEL, not iframe
-
tableau-cloud-web-authoring-is-a-two-step-transition-canvas — Tableau Cloud Web Authoring is a TWO-STEP transition — canvas DOM at TOP-LEVEL, not iframe
-
mcp-bible-v1919-r45r46r47-wrapper-impl-arity-discipline — # Bible v19.1.9 — Wrapper-Impl Arity Discipline (R45-R47)
-
heuristic-manual-fallback-wins-when-5-min-and-reliable — # Don’t autonomous-tool what AJ already does fast manually
-
tableau-cloud-rest-keypair-publish-gap — Tableau Cloud REST API cannot attach a saved-credential by UUID at publish-time. Upstream Tableau platform limitatio
-
claude-code-deferred-tool-registry-is-frozen-at-session-star — The trap
Known Issues
(none)
Decisions
-
nova-decision-log-consolidated — NOVA decisions on Tableau
-
permanent-mcp-workspace-defaults-for-aj-ea — Permanent MCP workspace defaults for aj-ea Register Salesforce, Snowflake, Fivetran, Tableau MCP servers as permanent wo
-
r-dash-requirements-freeze-checkpoint-1 — R-Dash Requirements Freeze (Checkpoint 1) Build R-Dash — Runwal’s internal BI platform to replace Tableau. ENTERPRISE sc
-
r-dash-wave-2-pass-1-m4-semantic-m5-governance-models-rls-en — R-Dash Wave 2 Pass 1 — M4 Semantic + M5 Governance Models + RLS Engine Wave 2 pass 1 shipped in commit bb24b1f (2026-04-
-
r-dash-wave-2-pass-2-m4m5-routes-first-rls-contract-test-j3 — R-Dash Wave 2 Pass 2 — M4/M5 Routes + First RLS Contract Test (J3 First Instance) Wave 2 pass 2 shipped in commit e09da8
-
strategic-scan-2026-04-23-three-actionable-insights-with-30 — Strategic Scan 2026-04-23: Three actionable insights with 30-90d action windows. (1) ACCELERATE AI PoC: AI/PropTech comp
-
strategic-scan-2026-04-23-ai-poc-rd-pipeline-factory-resolut — Strategic Scan 2026-04-23 — AI PoC + R&D Pipeline + Factory Resolution Strategic Scan 2026-04-23: Three actionable insig
-
bible-v181-v1917-framework-upgrade-for-tableau-mcp-pair-ship — Bible v18.1 → v19.1.7 framework upgrade for tableau MCP pair: shipped v6.0.1 with 521 tools (514 baseline + 7 R29-verifi
-
tableau-mcp-pair-upgrade-bible-v181-v1917-signed-at-v601-521 — Tableau MCP pair upgrade Bible v18.1 → v19.1.7 SIGNED at v6.0.1 / 521 tools — closure with surfaced framework refinement
-
tableau-mcp-v601-bible-v1917-signed-pair-certified-for-produ — Tableau MCP v6.0.1 / Bible v19.1.7 SIGNED pair certified for production use; 4 P1 defects (D-7..D-10) routed to dev agen
-
tableau-mcp-v601-bible-v1917-signed-pair-certified-productio — Tableau MCP v6.0.1 / Bible v19.1.7 SIGNED pair certified production-ready; 4 P1 defects (D-7..D-10) routed to dev agent;
-
ship-tableau-3-tier-suite-v10-as-is-back-up-monorepo-to-arj9 — Ship Tableau 3-tier suite v1.0 as-is + back up monorepo to ARJ999/tableau-mcp-server-v2 with documented gaps (calc-works
-
install-browser-use-as-on-demand-skillcli-not-permanent-9-mc — Install browser-use as on-demand skill+CLI (NOT Permanent 9 MCP); enforce dual-stack boundary via mutually-exclusive SKI
-
tableau-mcp-wrapper-impl-positional-arg-fault-family-fix-shi — Tableau-MCP wrapper-impl positional-arg fault family fix — ship fadb8c7 broad-scope: 23 wrapper sites + 9 impl signature
-
land-bible-v1920-patch-in-same-session-r43-ci-gate-ast-arity — Land Bible v19.2.0 patch in same session: R43 (CI gate AST arity audit, soft-warn first cycle), R44 (kwargs-by-name lint
-
tableau-keypair-workbook-republish-desktop-is-canonical-no-t — Tableau keypair workbook republish — Desktop is canonical, no Tier-3 autonomous For Tableau Cloud workbooks bound to Sno
-
ea-workbook-delivery-contract-universal-tableau-output-rule — EA Workbook Delivery Contract — universal Tableau output rule via Desktop hop All EA-delivered Tableau workbooks (revamp
-
ship-tableau-mcp-v602-groupitem-hydration-fix-and-hand-back — Ship tableau-mcp v6.0.2 GroupItem hydration fix and hand back to EA without dev-side live mutation smoke. Release gate s
-
confirmed-via-reasoning-chain-ship-tableau-mcp-v602-hand-to — [Confirmed via reasoning chain] Ship tableau-mcp v6.0.2 + hand to EA without dev-side live smoke. Reasoning chain id=ses
-
iteration-2-chain-derived-ship-tableau-mcp-v603-with-tscgrou — [Iteration 2 — chain-derived] Ship tableau-mcp v6.0.3 with TSC.GroupItem() + _id shell pattern across 5 sites (4 EA-flag
-
shift-dsr-pipeline-window-from-05000800-ist-to-11301230-ist — Shift DSR pipeline window from 05:00→08:00 IST to 11:30→12:30 IST (Fivetran SharePoint sync + Tableau extract refresh fo
-
dsr-pipeline-reschedule-re-attempt-session-cache-staleness-p — DSR pipeline reschedule re-attempt — session-cache staleness pattern identified, distinct from server-feature gap Re-fla
-
dsr-pipeline-reschedule-blocked-by-session-cache-staleness-n — DSR pipeline reschedule blocked by session-cache staleness (NOT server gap); resolution = fresh Claude session inherits
Relationships
- Depends on: snowflake
- Used by: runwal
- Integrates with: fivetran, salesforce
Sources
- Vault notes: 4 references
Contradictions
(none)
Related
snowflake | fivetran | salesforce | runwal
- rbac-rls-at-query-execution-layer-is-non-negotiable-enterpri
- runwal-vantage-project-scope-canonical-reference
- cube-js-widget-data-jwt-signing-pattern
- dsr-pipeline-reschedule-step-1-executed-step-2-failed-via-no
- tableau-mcp-updateextractrefreshtask-non-atomic-delete-succe
- tableau-cortex-analyst-alignment-phased-approach-definitiona
- cortex-analyst-392700-wrapper-view-pattern-validator
- cortex-analyst-formatting-prevention-three-layer-defense
- tableausnowflake-metric-build-extract-calc-fields-first-mirr
- funnel-scope-canonical-exclusion-framework-config-table-cano
- tableau-mcp-gap-set-project-default-permissions
- capture-cortex-tableau-alignment-as-new-playbook-section-in