Skip to content
Data MCP Directory

SITUATION, read 10 Nov 2026

When analysts stop trusting the dashboards, check which servers can trace a number and report incidents

The directoryAll situations

The question behind an untrusted dashboard is where the number came from and whether something upstream broke. An agent can only help if a server gives it lineage or impact tools, and, for incidents, an observability server.

The page lists what to check and the published facts for each server in scope. It names no choice: the facts differ by stack, and the engineer's own stack decides which server is relevant.

What to check

CheckThe field or fact that answers it
Can the agent follow a BI field back to its source tables?Lineage and impact facts on each entry; tool names such as get_lineage or get_upstream_lineage
Can the agent see open data incidents?Observability servers' tool names and the Access field
Does the agent see only what the person asking may see?Auth field: OAuth as the user versus a shared token
Is the server current?Version or commit and Last release fields

The published facts, for the 19 servers in scope

Filed by data tool, read 10 Nov 2026. Scope: catalogs and metadata, data observability, bi and analytics.
ServerKindTransportAuthTools listedLast release
Alation AI Agent SDK MCP serverOfficialRemote and localOAuth client credentials of a service account (role-limited) or user refresh token; remote MCP at <instance>/ai/mcp needs client_id and client_secret (no dynamic client registration).12 named in the evidence26 Oct 2026
Atlan MCP ServerOfficialRemote (hosted)OAuth per user (calls run as the signed-in user) or Atlan API key as Bearer token (shared service identity); local server uses API key + base URL.41 named in the evidence17 Feb 2026
Collibra MCP Server (chip)OfficialRemote and localCollibra username/password: server-wide credentials over stdio (mcp.yaml or env vars), or client-supplied Basic Auth headers per request over HTTP; tools respect the connecting user's DGC scopes.49 named in the evidence27 Oct 2026
Cube MCP serverOfficialRemote (hosted)OAuth Authorization Code + PKCE (scope mcp-agent-access, public client cube-mcp-client), or a Cube API key exchanged for a token (client_id cube-api-key).30 named in the evidencenone found on 10 Nov 2026
DataHub MCP ServerOfficialRemote and localStdio: DATAHUB_GMS_URL + DATAHUB_GMS_TOKEN (or ~/.datahubenv); HTTP: per-request DataHub personal access token as Authorization Bearer, no shared server token.22 named in the evidence21 Oct 2026
Euno MCPOfficialRemote (hosted)OAuth sign-in (default) or API key and headers; active persona scopes data and actions.56 named in the evidencenone found on 10 Nov 2026
Hex MCP serverOfficialRemote (hosted)OAuth authorization to the user's Hex workspace (server URL app.hex.tech/mcp, or the customer's single-tenant, EU or HIPAA domain); requires Explorer role or higher.18 named in the evidencenone found on 10 Nov 2026
Looker tools in MCP Toolbox for DatabasesOfficialRemote and localLooker API client_id and client_secret in the Looker source config, or use_client_oauth to pass the caller's OAuth token (default false).55 named in the evidence5 Nov 2026
Monte Carlo MCP ServerOfficialRemote (hosted)OAuth 2.1 with Dynamic Client Registration (user identity, Editor role or above), or MCP-server-type API key id:secret as Bearer token via mcp-remote.15 named in the evidencenone found on 10 Nov 2026
Omni MCP ServerOfficialRemote (hosted)OAuth 2.1 with PKCE (creates an MCP OAuth PAT for the user), or an API key (personal token or Organization API key; Organization keys can act as a user with X-MCP-User-ID).26 named in the evidencenone found on 10 Nov 2026
OpenMetadata MCP ServerOfficialRemote (hosted)OAuth 2.0 via existing SSO (per user), personal access token, or Bot JWT as Authorization Bearer.15 named in the evidence27 Oct 2026
Power BI Modeling MCP ServerOfficialRemote and localLocal: Microsoft Entra interactive sign-in (default) or service principal (client secret or certificate). Hosted: Entra ID as the signed-in user.21 named in the evidence6 Nov 2026
Secoda MCPOfficialRemote and localSecoda API token (API_TOKEN env var) for the local FastMCP wrapper; docs also describe a Secoda-hosted MCP endpoint authenticated against workspace and AI permissions.8 named in the evidencenone found on 10 Nov 2026
Select Star MCP ServerOfficialRemote (hosted)Select Star API token sent as Authorization: Bearer header (mcp-remote proxy used for Claude Desktop).7 named in the evidencenone found on 10 Nov 2026
Sifflet MCP ServerOfficialLocal (stdio)Sifflet API token (Viewer role for most tools, Editor for monitor generation) and backend URL as environment variables.10 named in the evidence3 Aug 2026
Sigma MCP serverOfficialRemote (hosted)OAuth (HTTP transport) inheriting the user's Sigma account permissions; API-key access token with scope mcp:access (Beta).0 named in the evidencenone found on 10 Nov 2026
SYNQ MCP (Coalesce Quality)OfficialRemote (hosted)OAuth 2 with PKCE per user with selectable permission tier (read, write, governance, deploy); legacy workspace token (st-...) as Bearer.134 named in the evidencenone found on 10 Nov 2026
Tableau MCPOfficialRemote and localHosted: OAuth 2.1 with each user's own Tableau Cloud identity. Self-hosted: PAT (default), direct-trust (Connected Apps), OAuth, passthrough, or unified access tokens.40 named in the evidence9 Nov 2026
ThoughtSpot MCP ServerOfficialRemote (hosted)OAuth to a ThoughtSpot instance (dynamic client registration, or manually registered client id and secret); bearer-token and /sse paths also exist; the user chooses or is bound to a ThoughtSpot instance URL.20 named in the evidence6 Jun 2025

What each server documents on lineage and impact

  • Alation AI Agent SDK MCP server: Alation's lineage tool traverses upstream or downstream from a starting object and supports column-level lineage; it is a BETA feature that Alation support must enable on the instance. The lineage tool takes max_depth (default 10), allowed_otypes, design/run-time filters and schema exclusions. None found: Documentation that the lineage tool returns transformation SQL/logic or BI-field/metric nodes; the tool page lists graph nodes filtered by object type only.
  • Atlan MCP Server: The hosted Atlan MCP exposes a traverse_lineage tool for upstream/downstream lineage with deeper hops on request. The docs say the hosted Atlan MCP can traverse end-to-end lineage; the tool page does not state column-level or SQL-logic parsing for the lineage tool. None found: A statement on the MCP tools page that traverse_lineage returns column-level edges or transformation SQL. Query_assets runs read-only SQL against a connected warehouse (Snowflake, Redshift, BigQuery, Databricks), returning up to 100 rows.
  • Collibra MCP Server (chip): The Collibra MCP server has separate tools for upstream and downstream technical lineage, lineage entities, and transformations. Get_lineage_transformation returns the details and logic of a specific data transformation. Lineage tools search entities and transformations in the technical lineage graph. Get_measure_data traces a measure back to its underlying physical columns and tables. None found: A README statement that the lineage tools return column-level edges or BI-field lineage explicitly; the tool list names entities and transformations only.
  • Cube MCP server: SearchDataModel searches the semantic model by similarity, covering views and their measures and dimensions, and returns name, title, description and type. ListDataModelFiles and readDataModelFile read the raw YAML, JavaScript or Python source of the semantic model, so the definition logic itself is readable. None found: A lineage tool in the Cube MCP tool tables (getBranchDiff and getDataModelChanges compare model versions, not data lineage).
  • DataHub MCP Server: DataHub's MCP server exposes a get_lineage tool covering datasets, columns and dashboards with hop control. The README says lineage is traceable at table and column level and that transformation logic is understood. A get_lineage_paths_between tool returns exact lineage paths between two assets or columns, including intermediate transformations and SQL query information. Get_dataset_queries fetches real SQL queries that reference a dataset or column.
  • Euno MCP: Euno MCP exposes get_upstream_lineage and resource_impact_analysis tools for one resource URI. Euno MCP can search and aggregate the metadata graph with EQL (search, count, multi-count, pivot). Euno MCP's example prompt traces a Tableau dashboard's upstream lineage.
  • Hex MCP server: Project editing tools list cells and read cell outputs and chart images, giving agents the SQL, Python and Markdown cells of a notebook. Search_projects finds projects in the workspace, and get_project reads a project's metadata. None found: A lineage tool on the Hex MCP server page (cell-level reads exist, but no column or upstream-table lineage tool is listed).
  • Looker tools in MCP Toolbox for Databases: Looker-get-explore returns explore metadata including always_filter and conditionally_filter constraints, tags and hidden status. Separate tools return dimensions, measures, filters and parameters of an explore, and the columns of connection tables. Looker-get-project-file returns the contents of a LookML file, so an agent can read the transformation and field logic written in LookML. None found: A lineage tool among the 55 looker-* tools in the Toolbox llms.txt index (no column-lineage or upstream-table tool is named).
  • Monte Carlo MCP Server: Monte Carlo's MCP server includes a get_asset_lineage tool, used to see how data flows into a table. None found: Documentation that get_asset_lineage returns column-level lineage, transformation SQL, BI fields or metrics; the MCP pages name only asset lineage.
  • Omni MCP Server: PickModel returns the models available to the calling user and pickTopic returns the topics in the chosen model and selects the most relevant one. SearchContent finds existing dashboards and apps by name, folder or tile name, and listDocumentQueries lists the saved queries in a document. None found: A lineage tool among the Omni MCP tools (no column or upstream-table lineage tool documented).
  • OpenMetadata MCP Server: Get_entity_lineage returns upstream and downstream lineage for any entity, with an includeColumnLineage option (default false, table level only), up to 10 hops. Create_lineage lets an agent write lineage edges, and root_cause_analysis is a lineage-and-impact tool. None found: Documentation that the MCP lineage tools return transformation SQL or logic.
  • Power BI Modeling MCP Server: The server exposes model-object tools for tables, columns, measures, relationships, partitions, hierarchies, calculation groups and named expressions (model definition level). Database_operations can import and export TMDL folders and deploy to Fabric, giving agents the model definition as code. None found: A lineage tool in the Power BI Authoring MCP tool table (no upstream-table, column-lineage or report-dependency tool).
  • Secoda MCP: The entity_lineage tool explores upstream and downstream dependencies for an entity. In the open-source wrapper entity_lineage takes only an entity_id and no depth or column parameter. None found: Documentation of column-level lineage, transformation SQL, BI-field or metric lineage in the Secoda MCP docs. The run_sql tool executes SQL against connected warehouses.
  • Select Star MCP Server: The Select Star MCP server has a traverse_lineage tool for lineage relationships and dependencies. Get_asset_queries returns warehouse queries connected to tables or columns. None found: Documentation on the MCP page that traverse_lineage is column-level or returns transformation SQL, BI-field or metric lineage.
  • Sifflet MCP Server: Sifflet MCP exposes get_downstream_assets_of_asset, which returns all downstream assets of an asset by URN. Sifflet says the server can start from an incident and trace the downstream assets affected.
  • Sigma MCP server: Agents can explore data sources and documents by asking about column names, definitions, descriptions, data types and column attributes. Search covers documents and data sources including data models, warehouse tables, and elements from workbooks and data models. None found: Lineage or upstream-dependency capability on the Sigma MCP server page.
  • SYNQ MCP (Coalesce Quality): SYNQ (docs now titled Coalesce Quality) serves the same lineage graph as its lineage view, including column-level lineage where the warehouse supports it. Lineage tools include get_lineage (up/down/both with depth), upstream and downstream dependencies, common upstream, and upstream sources such as dbt sources. Get_code returns the latest source code defining an entity, including SQL definitions and dbt models. Impact tools list the entities and systems affected by an entity or an issue.
  • Tableau MCP: Tableau's get-datasource-metadata tool returns table relationships, field descriptions, roles and types, calculation strings and parameters for a data source (table, column and calculation-definition level, not transformation lineage). The describe-flow tool summarizes a Tableau Prep flow's design including inputs, outputs, steps, lineage and connections, on all SKUs. On Tableau+ only, query-knowledge-context queries governed definitions, relationships, lineage, impact and graph sources through one read-only tool. The server's get-datasource-metadata tool enriches VizQL Data Service results with Tableau's Metadata API and only returns the richer descriptions for published data sources.
  • ThoughtSpot MCP Server: Search_objects finds Answers, Liveboards and Worksheets with filters for types, owner, tag, modified_since and verified_only, returning object metadata (title, description, query tokens, tags). The tool source warns that description and query tokens are authoring metadata that can be stale, and advises grounding explanations in the object's data via get_data. None found: A lineage tool in tool-definitions.ts (no column, upstream-table or transformation lineage tool among the 20 tools).

What Euno's server does not do

Euno's server gives an agent governed context about the data; it does not run the query, which is the job of the warehouse's own server.

Other situations

Sources

  1. github.com/Alation/alation-ai-agent-sdk/blob/main/guides/tools/lineage.md, read 10 Nov 2026
  2. docs.atlan.com/product/capabilities/atlan-ai/references/mcp-tools, read 10 Nov 2026
  3. docs.atlan.com/product/capabilities/atlan-ai/how-tos/remote-mcp-overview, read 10 Nov 2026
  4. github.com/collibra/chip/blob/main/README.md, read 10 Nov 2026
  5. docs.cube.dev/docs/integrations/mcp-server.md, read 10 Nov 2026
  6. raw.githubusercontent.com/acryldata/mcp-server-datahub/main/README.md, read 10 Nov 2026
  7. docs.euno.ai/ai/mcp-setup.md, read 10 Nov 2026
  8. learn.hex.tech/docs/api-integrations/mcp-server, read 10 Nov 2026
  9. mcp-toolbox.dev/integrations/looker/tools/looker-get-explore, read 10 Nov 2026
  10. mcp-toolbox.dev/llms.txt, read 10 Nov 2026
  11. docs.getmontecarlo.com/docs/mcp-server, read 10 Nov 2026
  12. docs.omni.co/ai/mcp/tools.md, read 10 Nov 2026
  13. docs.open-metadata.org/v2.0.x/how-to-guides/mcp/reference.md, read 10 Nov 2026
  14. raw.githubusercontent.com/microsoft/powerbi-modeling-mcp/main/README.md, read 10 Nov 2026
  15. docs.secoda.co/features/ai-assistant/secoda-mcp-server.md, read 10 Nov 2026
  16. github.com/secoda/secoda-mcp/blob/main/server.py, read 10 Nov 2026
  17. docs.selectstar.com/features/mcp-server, read 10 Nov 2026
  18. github.com/siffletdata/sifflet-mcp/blob/1f390ca06d7919214bfe067991539502fdb4b9fc/src/sifflet_mcp/server.py, read 10 Nov 2026
  19. github.com/siffletdata/sifflet-mcp/blob/main/README.md, read 10 Nov 2026
  20. help.sigmacomputing.com/docs/use-sigma-mcp-server, read 10 Nov 2026
  21. docs.synq.io/scout/mcp.md, read 10 Nov 2026
  22. tableau.github.io/tableau-mcp/docs/intro, read 10 Nov 2026
  23. raw.githubusercontent.com/tableau/tableau-mcp/main/src/tools/web/getDatasourceMetadata/getDatasourceMetadata.ts, read 10 Nov 2026
  24. raw.githubusercontent.com/thoughtspot/mcp-server/main/src/servers/tool-definitions.ts, read 10 Nov 2026

Last reviewed 10 Nov 2026.