uv --version
If missing:
Check if MCP server is configured:
Look for aurora-dsql or power-amazon-aurora-dsql-aurora-dsql in MCP settings.
If configured:
The MCP server can be configured in one of 2 ways. The default documentation-only configuration doesn't support database operations.
The MCP server can be updated to support the readonly_query, transact, and get_schema database
operation tools by connecting the server to the user's DSQL cluster, with the
Ask the user which configuration they prefer and re-configure if needed, editing the appropriate
MCP settings file.
If not configured, offer to set up:
Ask the user if they prefer the documentation-only
functionality or the database operation
functionality and edit the appropriate MCP settings file.
Would the user like a global MCP configuration or a project-scoped MCP configuration?
Default:
By default, the power has a placeholder MCP configuration globally. *This MCP configuration does
not contain any DSQL cluster details. Therefore, it can only be used for documentation tools,
but can be updated to match the database operation configuration with a DSQL cluster.*
cat ~/.kiro/settings/mcp.json
The user can update the MCP settings any time by navigating to the Kiro panel from
the left sidebar (Kiro's ghost icon) and navigating to the bottom "MCP Servers" pane.
Global Scope:
1. Locate ~/.kiro/settings/mcp.json
2. Identify the "powers" field and find the power-aurora-dsql-aurora-dsql in the
list of MCP servers.
3. Update the configuration args for the cluster endpoint, region, and database
user (default to admin).
4. Update the environment variables if necessary ("env" field):
1. Is the cluster region different than the default region?
Set the environment variable "REGION"
2. Is the user using an AWS Profile other than default?
List AWS profiles with:
aws configure list-profiles
For a non-default profile, configure the environment variable:
"AWS_PROFILE".
5. How permissive is the user? Is the MCP server permitted to write
to the database? If not, remove the --allow-writes flag from the
arguments in the MCP configuration.
Project-Scope:
1. Recommend disabling the power's global MCP server: "disabled": true
2. Locate or create a .kiro/settings directory in the project workspace:
mkdir -p .kiro/settings
3. Create a local .kiro/settings/mcp.json and add the Aurora DSQL MCP
server as specified in MCP Configuration.
1. Optional Arguments/Environment Variables:
to be configured for non-default values.
distinct from user's primary region in project/application.
to be for the MCP server. Always ask the user if writes
should be allowed.
{
"mcpServers": {
"awslabs.aurora-dsql-mcp-server": {
"command": "uvx",
"args": [
"awslabs.aurora-dsql-mcp-server@latest"
],
"env": {
"FASTMCP_LOG_LEVEL": "ERROR"
},
"disabled": false,
"autoApprove": []
}
}
}
{
"mcpServers": {
"awslabs.aurora-dsql-mcp-server": {
"command": "uvx",
"args": [
"awslabs.aurora-dsql-mcp-server@latest",
"--cluster_endpoint",
"[your dsql cluster endpoint, e.g. abcdefghijklmnopqrst234567.dsql.us-east-1.on.aws]",
"--region",
"[your dsql cluster region, e.g. us-east-1]",
"--database_user",
"[your dsql username, e.g. admin]",
"--profile",
"[your aws profile name, eg. default]"
"--allow-writes"
],
"env": {
"FASTMCP_LOG_LEVEL": "ERROR",
"REGION": "[your dsql cluster region, eg. us-east-1, only when necessary]",
"AWS_PROFILE": "[your aws profile name, eg. default]"
},
"disabled": false,
"autoApprove": []
}
}
}
Documentation: