# SYNQ MCP (Coalesce Quality): 134 tools, remote (hosted), from SYNQ

SERVER, read 10 Nov 2026

**The short answer.** SYNQ MCP (Coalesce Quality) is an official MCP server for SYNQ, published by SYNQ and read from its own source on 10 Nov 2026. It runs remote (hosted), and 134 tools are named. Version read: Hosted, no version published. Last release: none found on 10 Nov 2026.

- **Data tool:** [SYNQ](/mcp/synq/)
- **Publisher:** SYNQ (docs titled Coalesce Quality)
- **Kind:** Official
- **Repository or docs:** [docs.synq.io/scout/mcp.md](https://docs.synq.io/scout/mcp.md)
- **Version or commit:** Hosted, no version published
- **Last release:** none found on 10 Nov 2026
- **Transport:** Remote (hosted)
- **Auth:** OAuth 2 with PKCE per user with selectable permission tier (read, write, governance, deploy); legacy workspace token (st-...) as Bearer.
- **Access:** Configurable
- **Tools listed:** 134 named in the evidence
- **Tool definitions read at:** [docs.synq.io/scout/mcp.md](https://docs.synq.io/scout/mcp.md)
- **Context weight:** 4,550 tokens for 134 tool definitions (134 with a description), measured from the docs page read
- **Status:** Exists on 10 Nov 2026; docs.synq.io now titles itself Coalesce Quality Documentation and its MCP page calls the product Coalesce Quality; regional hosted endpoints EU/US/AU.
- **Read:** 10 Nov 2026

## In one sentence

SYNQ's hosted observability and lineage server uses per-user OAuth with tiered consent scopes, and tools hide when a scope is not granted.

## What SYNQ MCP (Coalesce Quality) exposes

134 tools are named in the evidence read on 10 Nov 2026.

`add_comment`, `apply_service_account_changes`, `batch_entity_annotations`, `batch_entity_details`, `batch_executions`, `batch_urls`, `browse_folders`, `create_incident`, `create_monitors`, `create_sql_tests`, `create_table_stats_monitor`, `decide_recommendation`, `delete_alert`, `delete_check_categorisation_rule`, `delete_data_product`, `delete_deployment_rule`, `delete_domain`, `delete_monitors`, `delete_owner`, `delete_saved_view`, `delete_sql_test_deployment_rule`, `delete_sql_tests`, `deploy_deployment_rule`, `deploy_sql_test_deployment_rule`, `describe_check_categorisation`, `describe_check_types`, `describe_resolver_ql`, `exclude_from_monitoring`, `execute_monitor`, `folder_of`, `get_alert`, `get_code`, `get_commit_diff`, `get_common_upstream_dependencies`, `get_coverage_summary`, `get_data_product`, `get_database_change_details`, `get_database_coordinates_from_entity`, `get_deployment_rule`, `get_domain`, `get_downstream_dependencies`, `get_entity_access`, `get_entity_details`, `get_entity_from_database_coordinates`, `get_entity_impact`, `get_entity_knowledge`, `get_entity_metrics`, `get_entity_overlays`, `get_immediate_downstream_dependencies`, `get_immediate_upstream_dependencies`, `get_incident_details`, `get_issue`, `get_issue_comments`, `get_issue_details`, `get_issue_impact`, `get_join_patterns`, `get_knowledge_pages`, `get_latest_executions`, `get_lineage`, `get_monitor`, `get_monitor_predictions`, `get_owner`, `get_query_activity`, `get_saved_view`, `get_schema`, `get_sql_test_deployment_rule`, `get_upstream_dependencies`, `get_upstream_sources`, `iam`, `list_access_signals`, `list_alerts`, `list_annotations`, `list_categorised_checks`, `list_check_categories`, `list_check_categorisation_rules`, `list_checks`, `list_commits`, `list_data_product_members`, `list_data_products`, `list_database_changes`, `list_deployment_rules`, `list_domain_members`, `list_domains`, `list_entity_coverage`, `list_executions`, `list_folder_members`, `list_history`, `list_integration_health`, `list_knowledge_pages`, `list_monitor_segments`, `list_monitoring_exclusions`, `list_monitors`, `list_open_incidents`, `list_open_issues`, `list_owners`, `list_ownerships`, `list_platform_users`, `list_recommendations`, `list_saved_views`, `list_service_account_suggestions`, `list_service_accounts`, `list_sql_test_deployment_rules`, `list_sql_tests`, `list_table_stats_monitors`, `list_users`, `plan_service_account_changes`, `preview_check_categorisation_rule`, `preview_deployment_rule`, `preview_sql_test_deployment_rule`, `profile_columns`, `resolve_query`, `run_sql_test_again`, `sample_column_values`, `sample_entities`, `save_alert`, `save_check_categorisation_rule`, `save_data_product`, `save_domain`, `save_owner`, `save_saved_view`, `search_entities`, `send_test_alert`, `set_alert_enabled`, `set_check_category`, `set_issue_status`, `set_monitor_segment_labels`, `set_saved_view_pin`, `submit_feature_request`, `summarise_executions`, `unexclude_from_monitoring`, `update_incident`, `update_monitors`, `update_sql_tests`, `update_table_stats_monitor`

## Not found in the sources read

- A GitHub repository, package version or release date for the SYNQ MCP server on the docs page. [Source](https://docs.synq.io/scout/mcp.md).

## The evidence on SYNQ MCP (Coalesce Quality), by topic

### Publisher and releases

- The server is hosted by SYNQ at regional URLs (EU mcp.synq.io, US, AU) and needs no workspace setup; no version or release date is published. (SYNQ's own claim; [source](https://docs.synq.io/scout/mcp.md), read 10 Nov 2026.)

### Clients, auth and scoping

- OAuth 2 with PKCE means actions are recorded as the real user with a via MCP badge. (SYNQ's own claim; [source](https://docs.synq.io/scout/mcp.md), read 10 Nov 2026.)
- The set of tools an assistant sees depends on the permissions the user grants at consent, and the consent screen offers only what the user's role allows. (SYNQ's own claim; [source](https://docs.synq.io/scout/mcp.md), read 10 Nov 2026.)
- The iam tool reports the caller's workspace, granted scopes and user. (SYNQ's own claim; [source](https://docs.synq.io/scout/mcp.md), read 10 Nov 2026.)

### Access and safety

- Four permission tiers (read-only, write, governance, deploy) each grant only the scopes asked for; read-only makes no changes. (SYNQ's own claim; [source](https://docs.synq.io/scout/mcp.md), read 10 Nov 2026.)
- Write tools do not appear in the client if the user granted only read-only access. (SYNQ's own claim; [source](https://docs.synq.io/scout/mcp.md), read 10 Nov 2026.)
- Admins can switch off OAuth access to the API for third-party clients, including MCP, with the Disable user API access setting; legacy static workspace tokens (st-...) are also accepted. (SYNQ's own claim; [source](https://docs.synq.io/scout/mcp.md), read 10 Nov 2026.)

### What it reaches

- The docs name dbt, SQLMesh, Coalesce, Airflow and warehouse query history as sources the tools draw on. (SYNQ's own claim; [source](https://docs.synq.io/scout/mcp.md), read 10 Nov 2026.)

### Lineage and impact

- SYNQ (docs now titled Coalesce Quality) serves the same lineage graph as its lineage view, including column-level lineage where the warehouse supports it. (SYNQ's own claim; [source](https://docs.synq.io/scout/mcp.md), read 10 Nov 2026.)
- Lineage tools include get_lineage (up/down/both with depth), upstream and downstream dependencies, common upstream, and upstream sources such as dbt sources. (SYNQ's own claim; [source](https://docs.synq.io/scout/mcp.md), read 10 Nov 2026.)
- Get_code returns the latest source code defining an entity, including SQL definitions and dbt models. (SYNQ's own claim; [source](https://docs.synq.io/scout/mcp.md), read 10 Nov 2026.)
- Impact tools list the entities and systems affected by an entity or an issue. (SYNQ's own claim; [source](https://docs.synq.io/scout/mcp.md), read 10 Nov 2026.)

### Definitions, ownership and rules

- Knowledge tools read entity descriptions and knowledge pages pinned to entities, including owners and certified pages. (SYNQ's own claim; [source](https://docs.synq.io/scout/mcp.md), read 10 Nov 2026.)
- The Governance permission tier lets the assistant manage data products, domains, owners, alert routing and check categories. (SYNQ's own claim; [source](https://docs.synq.io/scout/mcp.md), read 10 Nov 2026.)
- List_annotations and batch_entity_annotations read annotations carried by entities. (SYNQ's own claim; [source](https://docs.synq.io/scout/mcp.md), read 10 Nov 2026.)

### Freshness and upkeep

- Tools return execution history and latest executions for monitors, dbt models and Airflow tasks; join patterns use the last 30 days of warehouse query history. (SYNQ's own claim; [source](https://docs.synq.io/scout/mcp.md), read 10 Nov 2026.)

### Profile

- SYNQ's documentation is titled Coalesce Quality Documentation; the relationship between the names is not explained on the pages read. (SYNQ's own claim; [source](https://docs.synq.io/llms.txt), read 10 Nov 2026.)

## Read next

- [MCP servers for SYNQ](/mcp/synq/): 1 listed
- [Monte Carlo MCP Server and SYNQ MCP (Coalesce Quality), side by side](/compare/monte-carlo-mcp-vs-synq-mcp/)
- [The Context Weight Index](/context-weight/)

## Sources

- docs.synq.io/scout/mcp.md: https://docs.synq.io/scout/mcp.md (read 10 Nov 2026)
- docs.synq.io/llms.txt: https://docs.synq.io/llms.txt (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://datamcpservers.com/servers/synq-mcp/
