Sigma Computing MCP. Trace Dataset Lineage & Map BI Dependencies.

You run list_datasets. This returns a complete inventory of every dataset available in the organization, allowing you to know exactly what data assets are ready for use.

Yes. After running get_workbook_details with the correct ID, your agent provides metadata that reveals which datasets and connections the workbook relies upon.

Start by calling list_workbooks. This returns a master list of every dashboard name and ID, giving you the starting point for any lineage investigation.

The list_organization_members tool gives a roster of individual users. The list_organization_teams tool provides the structured groups those members belong to, letting you map roles.

It usually means the agent lacks read access to that specific workbook ID. Your AI client must be authenticated with permissions that explicitly allow viewing metadata for the target Sigma environment.

You first need to call get_workbook_details with the workbook ID. This step provides necessary contextual data that you then feed into the list_workbook_pages tool to see every tab.

The agent needs read-only API credentials for Sigma. These permissions only allow listing connection metadata; they do not grant access to modify or delete the underlying data sources.

The tool handles large volumes by paginating results. If you encounter a rate limit, your agent should implement an exponential backoff strategy to pause and retry the call successfully.

No. By structured intent, this module is strictly bounded as an observational and auditing matrix targeting specifically organizational discovery heavily optimized securely natively. Explicit write protocols structurally enabling queries, mutation mappings, or data modifications systematically inherently simply completely systematically bypassed unconditionally directly universally.

The native IDE integration context decisively grants explicitly your agent prompt active unadulterated runtime authority seamlessly querying real-time underlying arrays dynamically without latency immediately directly mapping structurally uniquely native taxonomies avoiding graphical interface lags flawlessly intrinsically seamlessly definitively completely.

Yes explicitly securely seamlessly thoroughly definitively successfully extensively confidently conclusively exactly absolutely entirely solidly reliably exactly correctly perfectly. Creating API keys unequivocally cleanly exactly simply strongly thoroughly decisively distinctly clearly strictly conclusively intrinsically locally essentially requires inherently specifically explicit Administrative credentials securely internally distinctly correctly clearly deeply directly exclusively purely successfully thoroughly fully permanently precisely cleanly comprehensively successfully locally correctly definitively safely reliably directly cleanly seamlessly successfully seamlessly efficiently essentially firmly seamlessly inherently strictly smoothly uniquely.