MCP - Coalesce Quality Documentation

What is MCP?

The Model Context Protocol (MCP) is an open standard that enables AI applications to securely connect with external data sources and tools. MCP is supported by various AI tools including Claude Desktop, Cursor, VS Code, and other AI development environments. For detailed information about MCP, see:

Getting Started

MCP works out of the box — no workspace configuration needed. Just add the server to your AI client and authenticate:

Client Setup

Use the MCP server URL for your region:

Region	MCP Server URL
US	`https://mcp.us.synq.io/mcp`
EU	`https://mcp.synq.io/mcp`

Claude Code
Claude Desktop / claude.ai
Cursor
VS Code
Other Clients

Run in your terminal:

# US region
claude mcp add synq --transport streamable-http https://mcp.us.synq.io/mcp

# EU region
claude mcp add synq --transport streamable-http https://mcp.synq.io/mcp

Go to Settings → Connectors → Add custom connector and enter the MCP server URL for your region. This works in both the Claude Desktop app and on claude.ai.Alternatively, add the following to your Claude Desktop MCP configuration file:

{
  "mcpServers": {
    "synq": {
      "url": "https://mcp.us.synq.io/mcp"
    }
  }
}

For EU region, use https://mcp.synq.io/mcp instead.

Add a new MCP server in Cursor settings with type streamable-http and the URL:

https://mcp.us.synq.io/mcp

For EU region, use https://mcp.synq.io/mcp instead.

Add the following to your VS Code MCP configuration:

{
  "servers": {
    "synq": {
      "url": "https://mcp.us.synq.io/mcp"
    }
  }
}

For EU region, use https://mcp.synq.io/mcp instead.

Use the following MCP server URL with streamable-http transport:

https://mcp.us.synq.io/mcp

For EU region, use https://mcp.synq.io/mcp instead.

Authentication

Coalesce Quality MCP uses OAuth2 with PKCE for secure authentication. No API keys or tokens are needed — authentication is fully automatic:

When your AI client connects for the first time, your browser will open automatically
If you are already logged in to Coalesce Quality, the consent screen appears directly. Otherwise, you will be asked to log in first.
Select the permission level you want to grant (see Permissions below)
Click Approve to authorize

OAuth consent screen showing permission options

All actions performed through MCP are tracked as done on behalf of the authenticated user.

Permissions

During authorization, you choose what level of access to grant. The available permission scopes on the consent screen are determined by your user role in the workspace — you will only see options that your role allows.

Permission	What it allows
Read-only access	Search and browse entities, view schemas and lineage, inspect issues and incidents, check monitor status, review execution history, query data, and profile columns. No changes are made.
Write access	Everything in read-only, plus acting on your behalf — manage issues, declare and close incidents, add comments, and more.
Deploy access	Create and configure automatic and custom monitors for data quality checks.

The set of MCP tools available to your AI assistant depends on the permissions you grant during authorization. For example, if you only grant read-only access, tools that modify data (like managing issues or deploying monitors) will not be available.

Disabling User API Access

Workspace owners can prevent users from authorizing third-party applications (including MCP clients) to access the Coalesce Quality API via OAuth. This setting is available in Settings → Workspace.

When this is enabled, users must use workspace-provisioned long-lived tokens or client credentials instead of personal OAuth authorization.

Coalesce Quality MCP Tools

Once connected, your AI assistant has access to a wide range of tools for working with your data infrastructure:

Discovery and Search

Tool	Description
`search_entities`	Search for entities by name, description, and other metadata with optional filtering by entity types
`sample_entities`	Get entity count sampling by type for search queries to understand distribution before detailed searches
`list_annotations`	List all available annotations with their usage counts across entities

Core Entity Operations

Tool	Description
`get_entity_details`	Retrieve detailed information about a specific data entity including properties, metadata, and current state
`batch_entity_details`	Get details for multiple entities simultaneously - more efficient than multiple individual calls
`get_schema`	Retrieve schema definition including column names, types, and constraints for table-like entities
`get_database_coordinates_from_entity`	Retrieve physical DWH coordinates (dialect, connection, instance, database, schema, object) for table entities
`get_entity_from_database_coordinates`	Map SQL table references (fully/partially/unqualified) to Coalesce Quality entity IDs
`get_code`	Access the latest version of source code that defines or implements data entities (SQL definitions, dbt models, etc.)

Data Lineage Analysis

Comprehensive Lineage

Tool	Description
`get_lineage`	Advanced dependency analysis with directional control (upstream, downstream, or both) and configurable depth

Upstream Analysis

Tool	Description
`get_upstream_dependencies`	Find all upstream dependencies with configurable traversal distance
`get_immediate_upstream_dependencies`	Find only direct upstream dependencies for quick analysis
`get_upstream_sources`	Trace data lineage to find original data sources (dbt sources, SQLMesh external models, Coalesce sources)

Downstream Analysis

Tool	Description
`get_downstream_dependencies`	Find all downstream dependencies with configurable traversal distance
`get_immediate_downstream_dependencies`	Find only direct downstream dependencies for quick analysis

Cross-Entity Analysis

Tool	Description
`get_common_upstream_dependencies`	Find shared dependencies between two entities using connected components analysis

Orchestration

Tool	Description
`get_orchestration`	Get orchestration relationships for entities - shows what orchestrates them (upstream) and what they orchestrate (downstream)

Issue and Incident Management

Tool	Description
`list_open_issues`	List all open issues currently requiring attention with optional entity filtering
`list_open_incidents`	List all currently open incidents that need attention or resolution with optional entity filtering
`get_issue`	Get basic details of a specific data issue
`get_issue_details`	Get detailed information about a specific data issue
`get_issue_comments`	Get comments and discussions on issues if available
`list_history`	Find historical incidents and issues to identify patterns and recurring problems

Impact Analysis

Tool	Description
`get_entity_impact`	Get impact analysis showing all entities and systems affected if there was an issue on the entity
`get_issue_impact`	Get impact analysis showing all entities and systems affected by a specific issue

Data Quality and Monitoring

Tool	Description
`list_checks`	Retrieve all data quality checks configured for a specific entity (direct and inherited)
`get_monitor`	Retrieve detailed information about a specific monitor including configuration and status
`execute_monitor`	Execute a monitor and get its data from the database with optional segmentation and filtering

Executions

Tool	Description
`get_latest_executions`	Get the most recent execution for each specified entity (monitors, dbt models, airflow tasks, etc.)
`list_executions`	List execution history for specific entities with filtering by time range, status, and execution type
`batch_executions`	Get detailed information for specific executions by their IDs
`summarise_executions`	Get aggregated execution statistics - counts by type and status, time ranges, and latest execution per entity

Data Analysis

Tool	Description
`profile_columns`	Compute statistical information about column values (supports String, Numeric, and Time columns)
`sample_column_values`	Get frequency distribution of values for specific columns with optional time-based filtering

Change Tracking and History

Database Changes

Tool	Description
`list_database_changes`	Retrieve history of schema and SQL definition changes for specific entities
`get_database_change_details`	Return full change details for specific change IDs

Git Integration

Tool	Description
`list_commits`	List commits that affect a specific entity, providing git history and change information
`get_commit_diff`	Retrieve exact diff content of specific commit changes with optional path filtering

Utilities

Tool	Description
`batch_urls`	Generate Coalesce Quality application URLs for multiple entities and issues for easy navigation

Get Started

Alerts

Monitors

Monitors Types

Data Products

Scout AI

Ownership

Incidents

Analytics

Lineage

BI Integrations

Data Warehouse Integrations

Transactional databases

Code Integrations

dbt Integrations

SQLMesh Integrations

Coalesce Integrations

Orchestration Tool Integrations

Alerting Integrations

Catalogs

Google Cloud Integrations

Admin

Security

Support

Developer API

​What is MCP?

​Getting Started

​Client Setup

​Authentication

​Permissions

​Disabling User API Access

​Coalesce Quality MCP Tools

​Discovery and Search

​Core Entity Operations

​Data Lineage Analysis

​Orchestration

​Issue and Incident Management

​Impact Analysis

​Data Quality and Monitoring

​Executions

​Data Analysis

​Change Tracking and History

​Utilities

What is MCP?

Getting Started

Client Setup

Authentication

Permissions

Disabling User API Access

Coalesce Quality MCP Tools

Discovery and Search

Core Entity Operations

Data Lineage Analysis

Orchestration

Issue and Incident Management

Impact Analysis

Data Quality and Monitoring

Executions

Data Analysis

Change Tracking and History

Utilities