Skip to main content
Glama
EngIcaro

qlik-lineage-mcp

by EngIcaro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
QLIK_API_KEYYesAPI key for authenticating with Qlik Cloud
QLIK_TENANT_URLYesURL of the Qlik Cloud tenant

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
ghost_filesC

Return data files in a space that no app in the tenant consumes.

Args: space_name: Display name of the space to scan. Case-insensitive.

unused_columnsA

Return columns of a data file that no app in the tenant consumes.

Args: file_name: Data file name with extension (e.g. Sales.qvd). Case-insensitive but extension must match. space_name: Display name of the space the file lives in. Case-insensitive. lineage_activation_date: ISO 8601 date when field-level lineage was activated in the tenant (e.g. "2025-06-01"). Consumer apps last reloaded before this date have no edges in their lineage graph and are marked as stale instead of being queried. Omit to skip staleness detection.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: ghost_files identifies unused data files, while unused_columns identifies unused columns within a file. No overlap.

Naming Consistency5/5

Both tool names follow a consistent snake_case verb_noun pattern (ghost_files, unused_columns), making them predictable.

Tool Count4/5

With only 2 tools, the server is focused on a narrow domain (identifying unused resources). While minimal, the scope is appropriately scoped for its specific purpose.

Completeness3/5

The tools cover file-level and column-level unused resources, but missing capabilities such as listing spaces, retrieving lineage graphs, or identifying unused apps, which may be needed for full lineage analysis.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources