Skip to directory

About Data Lineage MCP

Google Cloud managed MCP server for Data lineage. Exact tool names and accessible operations depend on the published server reference and configured Google Cloud permissions.

What you can use it for

  • Performs a breadth-first search (upstream or downstream) to retrieve lineage links for an asset identified by its Fully Qualified Name (FQN). Supports Column-Level Lineage (CLL), including wildcards to retrieve all CLL for an entity FQN. The search_lineage method also retrieves link-creating processes if max_process_per_link is not zero and links.processes.process is requested in the FieldMask . Required project permissions for stored links and processes are as follows: - datalineage.events.get for links stored for entity-level lineage - datalineage.events.getFields for links stored for column-level lineage - datalineage.processes.get for processes.
Connection and setup
Hosting
Google-managed remote
Transport
Streamable HTTP
Endpoint
https://datalineage.googleapis.com/mcp
Authentication
Google Cloud authentication: OAuth 2.0 using Application Default Credentials (ADC) in supported Google clients, or a client OAuth ID/secret or bearer token in compatible third-party clients. The principal needs mcp.tools.call plus the underlying product permissions; API key authentication is only available for services that explicitly support it.

Requirements

  • A Google Cloud project and access to the target product/resource.
  • Enable this MCP service and its underlying Google Cloud API as required by the product guide.
  • An MCP client that supports Streamable HTTP.
  • An identity with the MCP Tool User role (roles/mcp.toolUser) or equivalent mcp.tools.call permission, plus permissions for the underlying product operations.

Setup steps

  1. Choose the correct global or regional endpoint for your data location; this catalog lists the documented endpoint.
  2. In the Google Cloud project, enable the MCP service and the underlying product API if the product guide requires it.
  3. Authenticate the client with Google Cloud ADC (simplest with Antigravity/Gemini CLI) or configure OAuth 2.0 credentials in a compatible client.
  4. Grant the connecting identity roles/mcp.toolUser and only the product IAM roles needed for the intended operations.
  5. Add datalineage.googleapis.com to the client as a Streamable HTTP MCP server and complete sign-in.
  6. Refresh the client tool list and check that the tools match the product reference; availability may depend on permissions and selected toolset.
Tools 1

The Google-hosted remote service exposes one documented search_lineage tool for upstream/downstream and column-level lineage. A separate local MCP Toolbox config can expose the same tool; the local setup is not the hosted server. Search is read-only and operates on lineage metadata accessible to the authenticated Google identity.

  • search_lineage

    Performs a breadth-first search (upstream or downstream) to retrieve lineage links for an asset identified by its Fully Qualified Name (FQN). Supports Column-Level Lineage (CLL), including wildcards to retrieve all CLL for an entity FQN. The search_lineage method also retrieves link-creating processes if max_process_per_link is not zero and links.processes.process is requested in the FieldMask . Required project permissions for stored links and processes are as follows: - datalineage.events.get for links stored for entity-level lineage - datalineage.events.getFields for links stored for column-level lineage - datalineage.processes.get for processes.

    01
Limitations and notes
  • Google marks this service Preview in its supported-products catalog.
Original sources

Documentation checked 2026-10-28. Connection has not been runtime tested.

Similar tools