Build Amazon Athena-Connected Applications in Kiro with CData Connect AI MCP Server
Kiro is an agentic AI IDE from AWS that takes a spec-driven approach to software development, turning a natural language prompt into a detailed spec, then into working code, tests, and documentation. Available as a desktop IDE and CLI, Kiro supports remote MCP servers natively across all plans, letting agents pull live context from enterprise systems while they build.
By integrating Kiro with CData Connect AI through the MCP (Model Context Protocol), Kiro agents gain the ability to query, analyze, and act on live Amazon Athena data directly inside any coding session. Connect AI manages authentication, security, and query optimization so you can focus on building intelligent applications, while Kiro handles spec generation, code writing, and task execution.
This article outlines the steps to configure Amazon Athena connectivity in Connect AI, generate the required authentication credentials, register the Connect AI MCP Server in Kiro, and verify that your agent can successfully interact with live Amazon Athena data during coding sessions.
Prerequisites
- Kiro account
- CData Connect AI account
- Amazon Athena account with valid credentials.
About Amazon Athena Data Integration
CData provides the easiest way to access and integrate live data from Amazon Athena. Customers use CData connectivity to:
- Authenticate securely using a variety of methods, including IAM credentials, access keys, and Instance Profiles, catering to diverse security needs and simplifying the authentication process.
- Streamline their setup and quickly resolve issue with detailed error messaging.
- Enhance performance and minimize strain on client resources with server-side query execution.
Users frequently integrate Athena with analytics tools like Tableau, Power BI, and Excel for in-depth analytics from their preferred tools.
To learn more about unique Amazon Athena use cases with CData, check out our blog post: https://www.cdata.com/blog/amazon-athena-use-cases.
Getting Started
Step 1: Configure Amazon Athena Connectivity for Kiro
Connectivity to Amazon Athena from Kiro is made possible through Connect AI's Remote MCP Server. To interact with Amazon Athena data from your Kiro agent sessions, start by creating and configuring a Amazon Athena connection in Connect AI.
-
Log into Connect AI, click Sources, and then click Add Connection.
-
Select Amazon Athena from the Add Connection panel.
-
Enter the necessary authentication properties to connect to Amazon Athena.
Authenticating to Amazon Athena
To authorize Amazon Athena requests, provide the credentials for an administrator account or for an IAM user with custom permissions: Set AccessKey to the access key Id. Set SecretKey to the secret access key.
Note: Though you can connect as the AWS account administrator, it is recommended to use IAM user credentials to access AWS services.
Obtaining the Access Key
To obtain the credentials for an IAM user, follow the steps below:
- Sign into the IAM console.
- In the navigation pane, select Users.
- To create or manage the access keys for a user, select the user and then select the Security Credentials tab.
To obtain the credentials for your AWS root account, follow the steps below:
- Sign into the AWS Management console with the credentials for your root account.
- Select your account name or number and select My Security Credentials in the menu that is displayed.
- Click Continue to Security Credentials and expand the Access Keys section to manage or create root account access keys.
Authenticating from an EC2 Instance
If you are using the CData Data Provider for Amazon Athena 2018 from an EC2 Instance and have an IAM Role assigned to the instance, you can use the IAM Role to authenticate. To do so, set UseEC2Roles to true and leave AccessKey and SecretKey empty. The CData Data Provider for Amazon Athena 2018 will automatically obtain your IAM Role credentials and authenticate with them.
Authenticating as an AWS Role
In many situations it may be preferable to use an IAM role for authentication instead of the direct security credentials of an AWS root user. An AWS role may be used instead by specifying the RoleARN. This will cause the CData Data Provider for Amazon Athena 2018 to attempt to retrieve credentials for the specified role. If you are connecting to AWS (instead of already being connected such as on an EC2 instance), you must additionally specify the AccessKey and SecretKey of an IAM user to assume the role for. Roles may not be used when specifying the AccessKey and SecretKey of an AWS root user.
Authenticating with MFA
For users and roles that require Multi-factor Authentication, specify the MFASerialNumber and MFAToken connection properties. This will cause the CData Data Provider for Amazon Athena 2018 to submit the MFA credentials in a request to retrieve temporary authentication credentials. Note that the duration of the temporary credentials may be controlled via the TemporaryTokenDuration (default 3600 seconds).
Connecting to Amazon Athena
In addition to the AccessKey and SecretKey properties, specify Database, S3StagingDirectory and Region. Set Region to the region where your Amazon Athena data is hosted. Set S3StagingDirectory to a folder in S3 where you would like to store the results of queries.
If Database is not set in the connection, the data provider connects to the default database set in Amazon Athena.
- Click Save & Test.
-
Navigate to the Permissions tab in the Add Amazon Athena Connection page and update the User-based permissions.
Add a Personal Access Token
A Personal Access Token (PAT) is used to authenticate the connection to Connect AI from Kiro. It is best practice to create a separate PAT for each integration to maintain granular access control.
- Click the Gear icon at the top right of the Connect AI app to open Settings.
- On the Settings page, go to the Access Tokens section and click Create PAT.
-
Give the PAT a descriptive name (e.g., Kiro MCP) and click Create.
With the Amazon Athena connection configured and a PAT generated, Kiro can now connect to Amazon Athena data through Connect AI.
Step 2: Register the CData Connect AI MCP Server in Kiro
Kiro connects to external data sources through MCP servers configured in a file called mcp.json. In this step, you will open that file, add the Connect AI server details, and verify the connection.
-
Open a project folder. Kiro requires an open project before its agent features activate. When Kiro launches, click Open a project on the Getting started screen (or click Open Folder in the Explorer panel on the left). You can open any existing folder or create a new empty one, it just needs to be open.
-
Open the MCP config file. Press Ctrl + Shift + P (Windows) or Cmd + Shift + P (Mac) to open the command palette. Type MCP and select Kiro: Open user MCP config (JSON). This opens the mcp.json file where you register MCP servers for Kiro.
-
Generate your Base64 credentials. Kiro authenticates with Connect AI using your email and PAT, encoded together as a single Base64 string. Open a terminal and run the command for your operating system. Replace [email protected] with your Connect AI login email and YourPAT with the PAT you created in Step 1.
Windows (PowerShell):
[Convert]::ToBase64String([Text.Encoding]::UTF8.GetBytes("[email protected]:YourPAT"))Mac/Linux (Terminal):
echo -n "[email protected]:YourPAT" | base64Copy the output string. You will paste it into the config file in the next step.
-
Add the Connect AI server to mcp.json. Paste the following block into your mcp.json file. Replace your_base64_string with the string you copied in the previous step:
{ "mcpServers": { "cdata-connect-ai": { "url": "https://mcp.cloud.cdata.com/mcp", "headers": { "Authorization": "Basic your_base64_string" } } } }
- Save the file. Press Ctrl + S (Windows) or Cmd + S (Mac). Kiro picks up changes to mcp.json automatically, no restart is needed.
-
Verify the connection. Click the ghost icon in the left sidebar to open the Kiro panel. Under MCP SERVERS, you should see cdata-connect-ai with a green connected indicator. You can also confirm by typing the following in the Kiro chat panel:
List all available connections from Connect AI.If your Amazon Athena connection appears in the response, the MCP server is set up correctly and you are ready to query live data.
Step 3: Query Live Amazon Athena Data from Kiro
With the MCP server registered and verified, Kiro agents can now access your live Amazon Athena data directly in any session. Open the Kiro chat panel and use the following prompts to interact with your data.
The integration uses the following Connect AI MCP tools in sequence:
| MCP tool | Purpose |
|---|---|
| getCatalogs | Retrieves all available connections from Connect AI |
| getSchemas | Retrieves the database schemas for the selected connection |
| getTables | Retrieves all tables and views for the selected schema |
| queryData | Executes the generated SQL query and returns live results |
Open the Kiro chat panel and try the following prompts to interact with your Amazon Athena data:
- "What tables are available in my Amazon Athena connection?"
- "What are the top records in Amazon Athena data ordered by revenue?"
- "List all active Amazon Athena data and their current status."
- "Summarize Amazon Athena data activity for this quarter."
Kiro automatically discovers all CData connections, selects the most relevant connection, discovers the schema, generates, and executes the appropriate SQL query, and returns live results directly in the chat.
Build real-time, data-aware applications with Kiro and CData
Kiro and CData Connect AI together enable intelligent, AI-driven development where natural language prompts are automatically translated into live data operations across enterprise systems, without ETL pipelines, data sync jobs, or custom integration logic. This streamlined approach delivers stronger governance, lower operational overhead, and faster, more grounded responses from AI-powered agents.
Start a free trial today to see how CData Connect AI can empower Kiro with live, secure access to hundreds of enterprise systems.