# One MCP server for SYNQ: SYNQ MCP (Coalesce Quality), from SYNQ

MCP SERVERS FOR A DATA TOOL, read 10 Nov 2026

**The short answer.** One MCP server for SYNQ is listed: SYNQ MCP (Coalesce Quality), official, published by SYNQ and read on 10 Nov 2026. It runs remote (hosted) and names 134 tools; the version read is 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

## SYNQ MCP (Coalesce Quality)

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

`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`

- None found on 10 Nov 2026: A GitHub repository, package version or release date for the SYNQ MCP server on the docs page.

## Read next

- [SYNQ MCP (Coalesce Quality), the full entry](/servers/synq-mcp/): 18 facts
- [Monte Carlo MCP Server and SYNQ MCP (Coalesce Quality), side by side](/compare/monte-carlo-mcp-vs-synq-mcp/)
- [Data observability](/categories/observability/)

## Sources

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

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