feat(dynamodb-mcp-server): Add MySQL integration to support DynamoDB Data Modeling and Migration planning #1277

kishorln · 2025-09-12T16:06:18Z

Summary

Changes

Implementation of MySQL integration into the DynamoDB MCP server, providing foundational query capabilities for database migration analysis. This establishes the framework for comprehensive MySQL database analysis tooling.

Key Changes:

• Added MySQL Integration: Direct import of mysql_mcp_server functionality into the DynamoDB MCP server
• Tool: mysql_run_query tool is added to DynamoDB server and connects to MySQL DB when MySQL environment variables are configured
• Basic query execution: Execute SQL queries against RDS / Aurora MySQL clusters for migration analysis. Foundation for migration workflow analysis and database assessment

User experience

Before this change:

Users needed separate MCP servers for MySQL and DynamoDB operations, requiring:
• Multiple MCP server configurations in their setup
• Separate authentication and connection management
• Manual coordination between MySQL analysis and DynamoDB design workflows

After this change:

Users get a unified experience with a single MCP server that provides:
• Single Configuration: One MCP server configuration handles both MySQL analysis and DynamoDB operations
• Seamless Migration Workflow: Direct access to MySQL data for informing DynamoDB design decisions within the same tool context
• Extensible Foundation: Framework ready for specialized migration analysis like schema assessment and access pattern analysis

Checklist

If your change doesn't seem to apply, please leave them unchecked.

I have reviewed the contributing guidelines
I have performed a self-review of this change
Changes have been tested
Changes are documented

Is this a breaking change? No

Checklist:

Migration process documented
Implement warnings (if it can live side by side)

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.

…Data Modeling and Migration planning

codecov · 2025-09-12T16:07:21Z

Codecov Report

❌ Patch coverage is 72.97297% with 10 lines in your changes missing coverage. Please review.
✅ Project coverage is 89.21%. Comparing base (74082b0) to head (448a8f1).
⚠️ Report is 15 commits behind head on main.

Files with missing lines	Patch %	Lines
...b-mcp-server/awslabs/dynamodb_mcp_server/server.py	72.22%	7 Missing and 3 partials ⚠️

Additional details and impacted files

@@           Coverage Diff            @@
##             main    #1277    +/-   ##
========================================
  Coverage   89.21%   89.21%            
========================================
  Files         692      695     +3     
  Lines       48083    48209   +126     
  Branches     7464     7493    +29     
========================================
+ Hits        42896    43011   +115     
- Misses       3385     3392     +7     
- Partials     1802     1806     +4

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

rvamz · 2025-09-12T16:13:03Z

src/dynamodb-mcp-server/README.md

 The official MCP Server for interacting with AWS DynamoDB

-This comprehensive server provides both operational DynamoDB management and expert design guidance, featuring 30+ operational tools for managing DynamoDB tables, items, indexes, backups, and more, expert data modeling guidance.
+This comprehensive server provides both operational DynamoDB management and expert design guidance, featuring 30+ operational tools for managing DynamoDB tables, items, indexes, backups, and more, expert data modeling guidance and also MySQL query capabilities for database analysis and migration planning.


Have we considered to add or change existing evals to include this new use case? Please also consider adding a comment to the CR to show an end-to-end trace where the tool is exercised within the modeling workflow.

+1 showing end-to-end trace, also keep add a task to add this to current evals.

Sure, will include an end-to-end trace in the PR for better understanding of the workflow. Also, will plan for evals changes later once the actual MySQL data analysis tools are merged.

rvamz · 2025-09-12T16:13:12Z

src/dynamodb-mcp-server/README.md

 - `dynamodb_data_modeling` - Retrieves the complete DynamoDB Data Modeling Expert prompt

+### MySQL Integration
+- `mysql_run_query` - Run SQL queries against MySQL databases for analysis and migration planning


I wonder if we really need to expose a free-from SQL query tool to the LLM. Have we considered having a parameterized SQL query to read the performance schema if that's our only use case?

It feels odd that the DynamoDB MCP server would expose a tool to run MySQL queries. Was there another option?

We need to be explicit that this currently uses Aurora/RDS only.

I don't think that's the only query (read the performance schema) we need to run. I think in the workflow I have seen, we need to do validation to check if users have enabled the performance schema, and also I think there are queries regarding getting the whole schema for a database. So there is a need for a tool that can run many such queries. The question is, is there a way to restrict the queries to only a few approved by us? Worth checking.

I'm working on calling the mysql_run_query method within our analysis tool to execute the required SQL instead of registering as a separate tool. This will avoid exposing the tool publicly or user runs random calls.

rvamz · 2025-09-12T16:13:31Z

src/dynamodb-mcp-server/awslabs/dynamodb_mcp_server/server.py

+        except Exception as e:
+            return [{'error': f'MySQL initialization failed: {str(e)}'}]
+    else:
+        return [{'error': 'MySQL configuration not properly configured or available'}]


1/ This error is vague, most users don't read documentation. Should we make it
clearer what's misconfigured?
2/ Should we log errors with logging?
3/ Should we log the error in the MCP context?

Sure, will do

rvamz · 2025-09-12T16:13:40Z

src/dynamodb-mcp-server/awslabs/dynamodb_mcp_server/server.py

+    try:
+        return await mysql_query(sql, DummyContext(), None, query_parameters)
+    except Exception as e:
+        return [{'error': f'MySQL query failed: {str(e)}'}]


See my previous comment about error handling

…s for CI build

LeeroyHannigan · 2025-09-15T11:13:59Z

src/dynamodb-mcp-server/README.md

+        "FASTMCP_LOG_LEVEL": "ERROR",
+        "MYSQL_CLUSTER_ARN": "[your data]",
+        "MYSQL_SECRET_ARN": "[your data]",
+        "MYSQL_DATABASE": "[your data]",
+        "MYSQL_AWS_REGION": "us-west-2",
+        "MYSQL_READONLY": "true"


Explain MYSQL_SECRET_ARN in the README and why its required. Don't use [your data], put place holder values that are dummy and more intuitive to understand.

sure, will explain that in readme

LeeroyHannigan · 2025-09-15T11:14:31Z

src/dynamodb-mcp-server/awslabs/dynamodb_mcp_server/server.py

+MySQL Integration: This server also includes MySQL query capabilities through the run_query tool, enabling database
+analysis and migration planning from MySQL to DynamoDB.


For Aurora/RDS

LeeroyHannigan · 2025-09-15T11:15:50Z

src/dynamodb-mcp-server/pyproject.toml

    "strands-agents>=1.5.0",
-    "dspy-ai>=2.6.27"
+    "dspy-ai>=2.6.27",
+    "awslabs-mysql-mcp-server>=1.0.5",


Should we be dependent on other MCP servers. When we need to extend support to other databases, or on-prem how do we handle that. Take a dependence on N number of MCP's doesn't seem like a viable approach.

For now MySQL package is focused on Aurora MySQL, PR (1246) is yet to merge which will support both AWS and on-prem mysql. so this 1 package will eventually take care of entire MySQL databases. We will have to find / use similar packages for other databases.

shetsa-amzn · 2025-09-15T11:41:45Z

src/dynamodb-mcp-server/README.md

 The official MCP Server for interacting with AWS DynamoDB

-This comprehensive server provides both operational DynamoDB management and expert design guidance, featuring 30+ operational tools for managing DynamoDB tables, items, indexes, backups, and more, expert data modeling guidance.
+This comprehensive server provides both operational DynamoDB management and expert design guidance, featuring 30+ operational tools for managing DynamoDB tables, items, indexes, backups, and more, expert data modeling guidance and also MySQL query capabilities for database analysis and migration planning.


+1 showing end-to-end trace, also keep add a task to add this to current evals.

shetsa-amzn · 2025-09-15T11:42:16Z

src/dynamodb-mcp-server/README.md

 - `dynamodb_data_modeling` - Retrieves the complete DynamoDB Data Modeling Expert prompt

+### MySQL Integration
+- `mysql_run_query` - Run SQL queries against MySQL databases for analysis and migration planning


I don't think that's the only query (read the performance schema) we need to run. I think in the workflow I have seen, we need to do validation to check if users have enabled the performance schema, and also I think there are queries regarding getting the whole schema for a database. So there is a need for a tool that can run many such queries. The question is, is there a way to restrict the queries to only a few approved by us? Worth checking.

shetsa-amzn · 2025-09-15T11:42:49Z

src/dynamodb-mcp-server/README.md

        "FASTMCP_LOG_LEVEL": "ERROR",
        "AWS_PROFILE": "your-aws-profile",
-        "AWS_REGION": "us-east-1"
+        "AWS_REGION": "us-east-1",,


Whats the purpose of this?

Currently, we have DynamoDB API's using this particular AWS_REGION variable, we will remove that and use DB specific variables. It will help in case use resources (such as DB's) running on different regions.

shetsa-amzn · 2025-09-15T11:43:19Z

src/dynamodb-mcp-server/README.md

+        "MYSQL_CLUSTER_ARN": "[your data]",
+        "MYSQL_SECRET_ARN": "[your data]",
+        "MYSQL_DATABASE": "[your data]",
+        "MYSQL_AWS_REGION": "us-west-2",


This should be place holder

feat(dynamodb-mcp-server): Add MySQL integration to support DynamoDB …

187cc24

…Data Modeling and Migration planning

kishorln requested review from erbenmo, shetsa-amzn, LeeroyHannigan and a team as code owners September 12, 2025 16:06

github-project-automation bot added this to awslabs/mcp Project Sep 12, 2025

github-project-automation bot moved this to To triage in awslabs/mcp Project Sep 12, 2025

rvamz suggested changes Sep 12, 2025

View reviewed changes

fix(dynamodb-mcp-server): Update uv.lock to include MySQL dependencie…

37f04fd

…s for CI build

LeeroyHannigan reviewed Sep 15, 2025

View reviewed changes

shetsa-amzn reviewed Sep 15, 2025

View reviewed changes

kishorln added 2 commits September 15, 2025 15:57

fix(dynamodb-mcp-server): Add conftest.py to fix the test import issues

2761b40

fix(dynamodb-mcp-server): resolve test failures and namespace conflicts

448a8f1

		MySQL Integration: This server also includes MySQL query capabilities through the run_query tool, enabling database
		analysis and migration planning from MySQL to DynamoDB.

feat(dynamodb-mcp-server): Add MySQL integration to support DynamoDB Data Modeling and Migration planning #1277

Are you sure you want to change the base?

feat(dynamodb-mcp-server): Add MySQL integration to support DynamoDB Data Modeling and Migration planning #1277

Uh oh!

Conversation

kishorln commented Sep 12, 2025

Summary

Changes

Key Changes:

User experience

Before this change:

After this change:

Checklist

Acknowledgment

Uh oh!

codecov bot commented Sep 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

codecov bot commented Sep 12, 2025 •

edited

Loading