# Hightouch (Reverse ETL) MCP for AI Agents AI Agent Connect

> Hightouch (Reverse ETL) MCP lets you manage data synchronization workflows directly through your AI client. You can audit warehouse connections, inspect SQL models, and monitor the health of your outbound syncs to platforms like Salesforce or HubSpot without leaving your workspace.

## Overview
- **Category:** growth-engine
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_Ol0VUkS1D1nD6Pbi85YceDBC5tsYdocr5u8J49aY/ai-agent-connect
- **Tags:** reverse-etl, data-sync, warehouse-integration, data-modeling, pipeline-orchestration, saas-integration

## Description

The Hightouch (Reverse ETL) MCP lets you manage your data synchronization workflows directly through your AI client. Managing data pipelines usually means jumping between multiple tabs to check if your warehouse is actually talking to your CRM. You have to hunt for specific sync IDs, dig through logs to see why a run failed, and constantly verify that your SQL models aren't breaking the downstream flow. This Connector changes that by bringing your entire Hightouch environment into your primary workspace. Instead of hunting for information, you just ask your agent to tell you which syncs are active or what the success rate looks like for a specific marketing pipeline. It lets you audit your data models and source connections in seconds, making it much easier to keep your growth operations running smoothly. By connecting this through the Vinkius catalog, you get a unified way to oversee your Reverse ETL architecture. You can quickly identify which SaaS nodes are receiving data and ensure your data warehouse is feeding the right information to the right places, all while keeping your focus on the actual engineering work rather than the administrative overhead of monitoring.

## Tools

### list_syncs
The list_syncs tool lets you see all active data synchronizations in your account. This gives you a quick overview of your entire warehouse-to-SaaS pipeline architecture.

### get_sync
The get_sync tool retrieves specific details for a single data sync. Use it to check the configuration and metadata for a specific pipeline.

### list_sync_runs
The list_sync_runs tool lets you view the history of your sync runs. It lets you monitor the performance and reliability of your data flows over time.

### list_models
The list_models tool lets you audit all the data models driving your warehouse analytics. It helps you verify the SQL definitions used in your syncs.

### list_sources
The list_sources tool lets you enumerate all active warehouse data sources. It helps you see which platforms like Snowflake or BigQuery are feeding your data.

### list_destinations
The list_destinations tool identifies all connected SaaS destinations like Salesforce or HubSpot. Use it to confirm where your synchronized data is being sent.

## Prompt Examples

**Prompt:** 
```
Show me all my active syncs.
```

**Response:** 
```
I've found 5 active syncs in your Hightouch account:

| Sync Name | ID | Status |
| :--- | :--- | :--- |
| Snowflake to Salesforce | sync-001 | Active |
| BigQuery to HubSpot | sync-004 | Active |
| Postgres to Slack | sync-007 | Active |

Would you like to see the details for any of these?
```

**Prompt:** 
```
Did the Snowflake to Salesforce sync run successfully last night?
```

**Response:** 
```
Checking the run history for `sync-001`...

| Run Time | Status | Rows Processed |
| :--- | :--- | :--- |
| 2023-10-26 02:00 | **Success** | 12,450 |
| 2023-10-25 02:00 | **Success** | 11,900 |
| 2023-10-24 02:00 | **Failed** | 0 |

It looks like it succeeded last night, but there was a failure on the 24th. Should I pull the error logs for that failed run?
```

**Prompt:** 
```
What warehouse sources are connected?
```

**Response:** 
```
I've identified 3 active warehouse sources connected to your Hightouch account:

*   **Production Snowflake** (Active)
*   **Stripe BigQuery Dataset** (Active)
*   **Internal Postgres** (Active)

Would you like to see the data models available for any of these sources?
```

## Capabilities

### Audit active syncs
Get a complete list of all your data synchronizations in one view.

### Retrieve sync details
Pull specific configuration and metadata for any individual sync.

### Monitor run history
View past execution logs to check for successes or failures.

### Inspect data models
Audit the SQL definitions that power your warehouse analytics.

### Enumerate warehouse sources
See all active connections to platforms like Snowflake or BigQuery.

### Identify SaaS destinations
See which platforms like Salesforce or HubSpot are receiving data.

## Use Cases

### Checking failed marketing syncs
A Growth Ops lead asks why the Salesforce sync failed and uses list_sync_runs to see the error logs from the last hour.

### Auditing warehouse sources
A Data Engineer needs to see all active connections and uses list_sources to verify that the new BigQuery dataset is properly mapped.

### Verifying CRM destinations
An Analytics Engineer wants to confirm which platforms are getting data and uses list_destinations to check HubSpot and Slack connections.

### Model verification
A team member wants to see the SQL logic for a specific sync and uses list_models to inspect the warehouse analytics pipeline.

## Benefits

- Stop manual log hunting by viewing the history of your data pipelines in one place to see past successes or failures.
- Audit your SQL definitions quickly to ensure your warehouse data is accurate before it hits your CRM.
- Get a bird's-eye view of your entire data ecosystem by seeing all active warehouse connections at once.
- Verify your outbound marketing data flow by identifying exactly which SaaS nodes are receiving synchronized objects.
- Reduce context switching by checking sync statuses directly in your chat interface instead of logging into the Hightouch UI.

## How It Works

The bottom line is that you get instant visibility into your Reverse ETL pipelines without leaving your chat interface.

1. Subscribe to the Hightouch (Reverse ETL) MCP and provide your API key.
2. Connect your preferred AI client to the Vinkius platform.
3. Ask your agent to check sync statuses, audit models, or list active destinations.

## Frequently Asked Questions

**What is the Hightouch (Reverse ETL) MCP?**
It's a way to connect your Hightouch account to your AI client so you can manage data syncs, audit models, and check run histories using natural language.

**Can I use the Hightouch (Reverse ETL) MCP to check if my data hit Salesforce?**
Yes, you can use it to identify all connected SaaS destinations and then check the specific run history to see if the data synchronized successfully.

**How does the Hightouch (Reverse ETL) MCP help with data engineering?**
It helps by letting you audit your SQL models and warehouse source connections quickly without having to navigate the full Hightouch dashboard.

**Can I see my sync history with the Hightouch (Reverse ETL) MCP?**
Yes, you can ask your agent to show you the history of sync runs, which includes success statuses and the number of rows processed.

**Does the Hightouch (Reverse ETL) MCP support Snowflake and BigQuery?**
Yes, it allows you to see all active warehouse sources, including Snowflake and BigQuery, that are connected to your Hightouch account.

**Can the Hightouch (Reverse ETL) MCP help me find my SQL models?**
Yes, it can list all the data models currently driving your warehouse analytics so you can verify your SQL definitions.

**Can I check the SQL definition of a data model through my agent?**
Yes. Use the `list_models` tool to retrieve pure SQL definitions bounding your warehouse analytics pipelines. This allows your agent to audit transformation logic without you needing to dive into the Hightouch UI.

**How do I monitor the success rate of my sync runs?**
The `list_sync_runs` tool provides historical execution states and success tracking for any specific Sync ID. Your agent can aggregate these logs to report on overall reliability and identify transient failures.

**Can I see which SaaS apps are receiving data from Hightouch?**
Absolutely. Use the `list_destinations` tool to identify all connected SaaS nodes accepting synchronized outbound objects. This helps you audit exactly where your warehouse data is being pushed.