Skip to main content

What You'll Build

An AI-powered data pipeline development system that uses Continue’s AI agent with dlt MCP to inspect pipeline execution, retrieve schemas, analyze datasets, and debug load errors - all through simple natural language prompts

Prerequisites

Before starting, ensure you have:
  • Python 3.8+ installed locally
  • A dlt pipeline project (or create one during this guide)
  • Basic understanding of data pipelines
For all options, first:
1

Install Continue CLI

2

Install dlt

To use agents in headless mode, you need a Continue API key.

dlt MCP Workflow Options

🚀 Fastest Path to Success

Skip the manual setup and use our pre-built dlt Agent that includes the dlt MCP and optimized data pipeline workflows for more consistent results. You can customize it for your specific needs.
After ensuring you meet the Prerequisites above, you have two paths to get started:
To use the pre-built dlt Agent, you need either:
  • Continue CLI Pro Plan with the models add-on, OR
  • Your own API keys configured as environment variables
The agent will automatically detect and use your configuration along with the pre-configured dlt MCP for pipeline operations.

dlt MCP vs dlt+ MCP

Understanding the Difference

dlt MCP is focused on local pipeline development and inspection. It provides tools to:
  • Inspect pipeline execution and load information
  • Retrieve schema metadata from your local pipelines
  • Query dataset records from destination databases
  • Analyze load errors, timings, and file sizes
dlt+ MCP extends these capabilities with cloud-based features for production deployments:
  • Connect to dlt+ Projects and manage deployments
  • Monitor pipeline runs across multiple environments
  • Access centralized logging and observability
  • Collaborate with team members on pipeline development
For local development and getting started, dlt MCP is the right choice. Consider dlt+ MCP when you need production deployment features and team collaboration.

Pipeline Development Recipes

Now you can use natural language prompts to develop and debug your dlt pipelines. The Continue agent automatically calls the appropriate dlt MCP tools.
Where to run these workflows:
  • IDE Extensions: Use Continue in VS Code, JetBrains, or other supported IDEs
  • Terminal (TUI mode): Run cn to enter interactive mode, then type your prompts
  • CLI (headless mode): Use cn -p "your prompt" for headless commands
Test in Plan Mode First: Before running pipeline operations that might make changes, test your prompts in plan mode (see the Plan Mode Guide; press Shift+Tab to switch modes in TUI/IDE). This shows you what the agent will do without executing it.To run any of the example prompts below in headless mode, use cn -p "prompt"
About the —auto flag: The --auto flag enables tools to run continuously without manual confirmation. This is essential for headless mode where the agent needs to execute multiple tools automatically to complete tasks like pipeline inspection, schema retrieval, and error analysis.

Pipeline Inspection

Inspect Pipeline Execution

Review pipeline execution details including load timing and file sizes.Prompt:

Schema Management

Retrieve Schema Metadata

Get detailed schema information for your pipeline’s tables.Prompt:

Data Exploration

Query Dataset Records

Retrieve and analyze records from your destination database.Prompt:

Error Debugging

Analyze Load Errors

Investigate and understand pipeline load errors.Prompt:

Pipeline Creation

Build New Pipeline

Create a new dlt pipeline from an API or data source.Prompt:

Schema Evolution

Handle Schema Changes

Review and manage schema evolution in your pipelines.Prompt:

Continuous Data Pipelines with GitHub Actions

This example demonstrates a Continuous AI workflow where data pipeline validation runs automatically in your CI/CD pipeline in headless mode using the dlt Assistant agent. Consider customizing this agent to add your organization’s specific validation rules.

Add GitHub Secrets

Navigate to Repository Settings → Secrets and variables → Actions and add:
The workflow uses the pre-built dlt Agent with --agent continuedev/dlt-agent. This agent comes pre-configured with the dlt MCP and optimized rules for pipeline operations. You can customize the validation rules and prompts for your specific pipeline requirements.

Create Workflow File

This workflow automatically validates your dlt data pipelines on pull requests using the Continue CLI in headless mode. It inspects pipeline schemas, checks for errors, and posts a summary report as a PR comment. The workflow can also be triggered manually via workflow_dispatch. Create .github/workflows/dlt-pipeline-validation.yml in your repository:
The dlt MCP works with your local pipeline state. Make sure your CI environment has access to the necessary pipeline configuration and credentials.

Pipeline Development Best Practices

Implement automated pipeline quality checks using Continue’s rule system. See the Rules deep dive for authoring tips.

Schema Validation

Error Handling

Performance Monitoring

Data Quality

Troubleshooting

Pipeline Not Found

Destination Connection Issues

Schema Inference Problems

Verification Steps:
  • dlt MCP is installed and configured
  • Pipeline directory is accessible
  • Destination database credentials are configured
  • Pipeline has been run at least once

What You’ve Built

After completing this guide, you have a complete AI-powered data pipeline development system that: ✅ Uses natural language — Simple prompts instead of complex pipeline commands ✅ Debugs automatically — AI analyzes errors and suggests fixes ✅ Runs continuously — Automated validation in CI/CD pipelines ✅ Ensures quality — Pipeline checks prevent bad data from shipping

Continuous AI

Your data pipeline workflow now operates at Level 2 Continuous AI - AI handles routine pipeline inspection and debugging with human oversight through review and approval of changes.

Next Steps

  1. Inspect your first pipeline - Try the pipeline inspection prompt on your current project
  2. Debug load errors - Use the error analysis prompt to fix any issues
  3. Set up CI pipeline - Add the GitHub Actions workflow to your repo
  4. Create new pipelines - Use AI to scaffold new data sources
  5. Monitor performance - Track pipeline execution metrics over time

Additional Resources

dlt Documentation

Complete dlt platform documentation

Continue Documentation

Explore Continue documentation and guides

dlt Blog: MCP Deep Dive

Learn about AI agents, MCP, and Continue integration

MCP Concepts

Deep dive into dlt MCP integration