synq.fm
Synq provides Coalesce Quality, a data quality and observability platform for managing monitors, incidents, lineage, alerts, and related workflows across data systems. The synq.fm domain also has a published legacy SYNQ Video API for video creation, metadata, upload, and streaming operations.
synq.fm exposes a legacy SYNQ Video HTTP API keyed by an `api_key`, plus current Coalesce Quality developer surfaces consisting of a gRPC API using client-credentials OAuth and a regional MCP server using OAuth2 PKCE or legacy bearer workspace tokens.
- Coalesce Quality MCP Serverdetected
- SYNQ Video APIdiscovered
- Coalesce Quality gRPC APIdiscovered
Sign up for a developer API key via SYNQ registration. The published OpenAPI description for SYNQ Video links to that signup page in its info.description. Use the issued key as the api_key form field when calling the Video API.
In the Coalesce Quality application API settings, create client credentials to obtain a CLIENT_ID and CLIENT_SECRET. The docs say these credentials are scoped, so choose the scope appropriate for the RPCs you plan to call. Exchange them with grant_type=client_credentials at http://api.synq.io/oauth2/token to obtain a bearer access token for the developer API.
Point your MCP client at the server URL and approve access in the browser. The server accepts a Client ID Metadata Document (CIMD), so the client authenticates with its own hosted URL as the client_id — nothing to register.
conventions · 0/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✗
/llms.txt - API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing