Request: Extend Context Layer to support Amazon Redshift as a destination, so the Fivetran MCP can expose context for data landed in Redshift.

Why it matters: Redshift is our primary warehouse. All of our Fivetran connectors load into it, and it powers our dbt models and Looker reporting. Today Context Layer does not support Redshift, which leaves us unable to use it at all. We are building AI agents on top of our analytics stack, and Fivetran is the best source of truth for connector schemas, lineage, and sync status. Without Redshift support, our agents have to guess at that context instead of reading it from Fivetran.

What we need:

- Context Layer parity for Redshift destinations (provisioned clusters and Redshift Serverless)

- The Fivetran MCP returning table and column metadata, lineage, and freshness for Redshift-backed connectors

- Support for our existing Redshift destination auth, with no need to re-provision the destination

Impact: This would let us adopt Context Layer across our full connector footprint immediately. We are happy to join a beta and share feedback.