Fivetran

Data integration platform (177 MCP tools) syncing Salesforce and other sources into Snowflake for analytics.

Current State

Fivetran with session-based MCP server (177 tools, v8.0.0). Core of the enterprise data pipeline: Salesforce Fivetran Snowflake. Manages connector setup, data synchronization, schema management, and monitoring.

Key Learnings

  • runwal-group-business-context-indian-real-estate-developer — Runwal Group business context with Fivetran pipeline

  • vps-credential-leaks-in-tmp-from-previous-sessions-found — VPS credential leaks context

  • mcp-namespace-collision-health-check-collides-across-10-serv — The tool name health_check is 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_check is 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.json unde

  • 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-server-registrations-bloat-context-of-unused-workspaces — MCP servers registered in ~/.claude.json under 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-ea project in ~/.claude.json had mcpServers: {} (completely empty) despite MEMORY.md asserting 4 perm

  • aj-ea-4-permanent-mcp-servers-registered-09-apr-2026 — All 4 workspace MCP servers for /root/aj-ea are now permanently registered in ~/.claude.json under `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

  • runwal-vantage-project-scope-canonical-reference — Runwal Vantage is a Tableau-grade internal BI platform forked from Redash. Scope: 9 Runwal functions, 500→1000 users, 5

  • vantage-snowflake-only-single-source-architecture — Runwal Vantage consumes only Snowflake as its data source. All upstream sources (Salesforce, SAP S/4, SharePoint CSV/Exc

  • sharepoint-data-must-flow-through-snowflake-not-vantage-inge — SharePoint CSVs and Excel files for R-Dash/Vantage must be materialized into Snowflake by upstream pipelines (Fivetran/n

  • r-same-snowflake-only-no-ingestion-architecture — R-Same is a consumption-only BI platform: Snowflake is the single active data source, and zero ingestion/ETL code exists

  • r-same-snowflake-only-no-direct-source-connectors — R-Same consumes data exclusively from Snowflake — no direct connectors to Salesforce, SAP S/4, or SharePoint inside the

  • r-same-snowflake-only-consumption-zero-ingestion — All upstream data sources (Salesforce, SAP S/4, SharePoint CSVs/Excels, other files) flow into Snowflake via existing up

  • sharepoint-snowflake-no-ingestion-in-analytics-platform — All upstream data sources (SharePoint, SAP, Salesforce) must materialize into Snowflake via dedicated pipelines (Fivetra

  • sharepoint-must-materialize-to-snowflake-upstream — SharePoint CSV/Excel ingestion must NOT be handled inside R-Same. Any attempt to add file-polling or Graph API calls to

  • r-same-snowflake-only-consumption-ar4-constraint — R-Same consumes Snowflake as its single data source — zero ingestion code lives inside the platform. All upstream source

  • sharepoint-sap-salesforce-all-via-snowflake-zero-ingestion — R-Same consumes Snowflake as its sole data source — zero ingestion code inside the platform. All upstream sources (Sales

  • sharepoint-data-routes-through-snowflake-vantage-is-consumpt — Initial design explored a file-to-table materialisation shim inside R-Same to ingest SharePoint CSV/Excel directly. This

  • sharepoint-data-flows-via-snowflake-not-direct-ingestion — SharePoint CSV/Excel files are NOT ingested directly by R-Same. They flow upstream via Fivetran/n8n/custom shim → Snowfl

  • r-same-sharepoint-snowflake-upstream-only — R-Same consumes Snowflake only — all SharePoint CSV/Excel, Salesforce, and SAP data flows upstream via Fivetran/n8n befo

  • bible-v1913-canonized-mcp-2025-11-25-spec-compliance-mandate Bible v19.1.3 canonized — MCP 2025-11-25 spec-compliance mandated

  • cost-observer-fivetran-sync-cost-observability-runwal-local Cost Observer — Runwal Fivetran cost visibility (2026-04-23)

  • r13-cascade-single-source-idiom-contract-sourced-fields Pattern: R13 Cascade Single-Source Idiom for Config-Sourced Fields

  • bible-v1915-v1916-r24-r13-framework-promotions Bible v19.1.5 + v19.1.6 — R24 task gating + R13 no-hardcode idiom framework promotion

  • 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 9c41f847 on

  • snowflake-mcp-v22-retro-bible-law-11-r38-r40-upstream-verifi Snowflake MCP v22 retrospective — Bible Law 11 (R38-R40) institutional learning

  • claude-code-deferred-tool-registry-is-frozen-at-session-star The trap

Known Issues

(none)

Decisions

Relationships

Sources

  • Vault notes: 3 references

Contradictions

(none)

salesforce | snowflake | tableau | runwal