copy-connections

Copy Connections

Copy existing Fivetran connections to a new destination with full config fidelity. Connections are created paused and without credentials; you decide how to handle credentials afterward (let the skills help, or finish in the Fivetran UI).

Six skills that orchestrate a copy workflow against the Fivetran REST API. Packaged as a Claude Code plugin; also runs in Codex. Depends on the Fivetran MCP server.

Status

v0.2.0 — implementation complete, pre-testing. Skills are written. They've been tested again copying into a destination of the same type. Have not yet been tested by copying into a destination of a different type.

What this does

Given an existing Fivetran account, Copy Connections helps you create a duplicate set of connections pointing to a different destination. Typical use cases:

• Testing a few connections against a new warehouse before committing to a full migration (e.g., Redshift → Snowflake)
• Migrating everything from one destination to another
• Splitting a single destination into prod and dev
• Standing up a staging or DR mirror

What copies: connection configs (sync frequency, data delay, networking method, connector-specific settings), schema configs (enabled tables/columns, sync mode), column config (hashing, blocking), and Quickstart transformation packages.

What doesn't copy: credentials (can be added post-copy via the credentials skill or manually in the UI), OAuth tokens (re-auth required in the UI — the skills can't do browser OAuth), custom dbt projects (detected and flagged, require separate setup), historical data (new connections start fresh from the time you unpause them).

Connections are created paused. The skills never unpause connections — you verify and unpause when you're ready.

The workflow

Five phases. The first three create the connections; the last two get them ready to sync.

1. Scope — you describe what you want, the scope skill fetches current state, and produces a structured copy plan. Intent-first: "testing a few connections" and "migrating everything" get different defaults.
2. Validate — checks the plan for issues (naming collisions, type compatibility, schema portability, source state). Produces a report; execute refuses to run if validation fails.
3. Execute — creates the connection shells with config and installs Quickstart packages. Uses run_setup_tests: false so no credentials are needed. Produces a results file.
4. Credentials — helps attach credentials to the created connections. For credential-based connections (password, API key), collects and patches via the API. For OAuth connectors, provides Fivetran UI links. You can skip this entirely and handle credentials yourself in the Fivetran UI.
5. Schema — after credentials are in place, runs setup tests to verify and discover the schema, then applies table/column selections, sync modes, and hashing from the plan.

Between phases, the coordinator asks before continuing. State is persisted in .copy-connections/ in your working directory, so you can close your session mid-workflow and resume later.

Requirements

• Claude Code or Codex CLI installed
• Fivetran MCP server configured in your working directory — see setup instructions

• These MCP tools enabled (uncomment in server.py if needed):
  • Reads: list_connections, get_connection_details, get_connection_schema_config, list_destinations, get_destination_details, list_groups, list_transformations, get_transformation_details, list_transformation_projects, Quickstart package metadata endpoints
  • Writes: create_group, create_destination, run_destination_setup_tests, create_connection, modify_connection, modify_connection_table_config, run_connection_setup_tests, create_transformation

Installation

From the directory where fivetran-mcp is configured:

Claude Code:

claude --plugin-dir /path/to/copy-connections

Codex:

Copy the skills into Codex's skills directory, then restart Codex:

cp -r /path/to/copy-connections/skills/* ~/.codex/skills/

Alternatively, symlink them if you want updates to flow through automatically:

for skill in /path/to/copy-connections/skills/*/; do
  ln -s "$skill" ~/.codex/skills/
done

Restart Codex after installing so it picks up the new skills.

Usage

Start a session (Claude Code or Codex) in a working directory that has your Fivetran MCP configured. Then say something like:

"I want to copy my Fivetran connections from Redshift to a new Snowflake destination."

The coordinator will figure out where you are in the workflow (no .copy-connections/ → start scoping; existing plan → offer to validate or modify it; etc.) and walk you through from there.

Modifying an existing plan