Integrating Kiro CLI with GetResponse Data via CData CLI

Kiro CLI is a terminal-based AI coding agent from AWS designed to take you from prompt to production directly in the command line. It understands your codebase through advanced code intelligence and context management and can autonomously execute multi-step workflows, running multiple agents in parallel, automating CI/CD pipelines, and integrating with external tools and data sources through native MCP support. Its support for agent steering files, custom agents, and agent skills makes it well-suited for structured, tool-driven workflows, making it a natural fit for connecting to external data sources through CData CLI. By describing your data goals in plain language, Kiro CLI can handle the full setup process, from driver configuration and license activation to connection creation and query execution, without manual intervention at each step.

This article details step-by-step directions for how to connect GetResponse data to Kiro CLI through CData CLI.

Prerequisites

1. Kiro CLI installed
2. CData CLI installed
3. Access to GetResponse

Step 1: Download the skill (one-time setup)

Always use CData CLI with the official skill.

1. The official CData CLI Skill on GitHub can be downloaded using npx skills through the terminal:

   npx skills add CDataSoftware/cli-skills

2. Follow the prompts in the terminal to install for Kiro CLI.

Step 2: Set up the project directory

Create a project directory to contain all project files.

1. Navigate to your desired directory in the terminal and start a session with the kiro-cli command.

Step 3: Establish the driver and connection

Describe what you want to accomplish in this session with the CLI and GetResponse data.

I would like to build a command line app that connects to GetResponse and checks for updates from AccountBilling. Make sure to include data from important columns like ListSize and PaymentPlan.

This prompt automatically loads the skill and kicks off the following process. You can also manually prompt the agent for each step below.

1. Driver setup: Kiro CLI checks for an existing CData GetResponse driver, or searches and downloads a new one:

• cdatacli drivers list

• cdatacli drivers search GetResponse

• cdatacli drivers download --artifact-id <artifact-id>

2. Activation: Activate the GetResponse driver with a single command for a trial or full license:

•  cdatacli drivers activate GetResponse --name "<name>" --email "<email>" --trial

• cdatacli drivers activate GetResponse --name "<name>" --email "<email>" --key "<product-key>"

3. Establish GetResponse connection: Check for existing GetResponse connections or create a new one:

• cdatacli connection list

• cdatacli drivers activate GetResponse --name "<name>" --email "<email>" --trial

4. Create a GetResponse skill (if applicable): CData provides driver instructions for popular sources that can be used to create a source specific skill to guide the agent through best practices for the driver.
• Run the following command and save the output to your skills directory, either at the project level or globally. (Note: If you receive a "No instructions available for GetResponse" message, no driver instructions exist for this source. You can continue using the main driver skill.)

  cdatacli drivers skill GetResponse > ~/skills/cdata-GetResponse/SKILL.md

Step 4: Query GetResponse data

With the CData driver fully configured, your agent can now execute queries and write code against live GetResponse data:

1. 
   cdatacli query sql --connection <my_GetResponse_connection> --sql <SELECT * FROM table>

Query GetResponse data directly from your terminal with CData CLI

Kiro CLI and CData CLI together give your AI coding agent a direct path to live GetResponse data without custom middleware, scheduled syncs, or manual setup at each step. Describe your goal, and the agent handles driver configuration, connection setup, and query execution from start to finish in the terminal.

Download the free CData CLI and start a free, 30-day trial of the CData API Driver for JDBC today.