feat(dms): add AWS Database Migration Service MCP Server

[nikoshet]

Add comprehensive AWS Database Migration Service (DMS) MCP server with full migration workflow operations for replication instances, endpoints, replication tasks, and table-level monitoring.

Features:

• Replication Instance Management: Create and describe replication instances with Multi-AZ support, storage configuration, and VPC settings

• Endpoint Operations: Create, describe, and test connectivity to source/target database endpoints supporting MySQL, PostgreSQL, Oracle, MariaDB, Aurora, and Aurora-PostgreSQL

• Replication Task Management: Create, start, stop, and monitor replication tasks with support for full-load, CDC, and full-load-and-cdc migration types

• Table-Level Operations: Get detailed table-level replication statistics and reload specific tables during migration

• Connection Testing: Test and validate connectivity between replication instances and endpoints with comprehensive error reporting

• Real-time Monitoring: Monitor migration progress with detailed statistics, error tracking, and performance metrics

Security Features:

• Read-only mode support (--read-only-mode flag) to prevent mutations during monitoring
• Comprehensive input validation using Pydantic models with strict type checking
• Built-in security warnings for sensitive operations like endpoint creation with credentials
• AWS credential chain support with proper IAM permission validation
• JSON validation for table mappings and task settings

Technical Implementation:

• Built with FastMCP framework following MCP specification
• Comprehensive test suite with 88 passing tests and 94% code coverage
• Docker support with health checks and multi-stage builds
• Follows AWS security best practices and MCP design guidelines
• Production-ready error handling with user-friendly messages
• Support for 6 database engines with engine-specific validation

The server enables AI assistants to safely manage AWS DMS migration workflows while providing detailed guidance on database migration best practices and real-time monitoring capabilities.

Summary

Changes

New MCP server for AWS Database Migration Service (DMS):

Tools Implemented

1. describe_replication_instances - List and describe DMS replication instances
2. create_replication_instance - Create new replication instances with Multi-AZ support
3. describe_endpoints - List and describe source/target database endpoints
4. create_endpoint - Create database endpoints for supported engines
5. test_connection - Test connectivity between replication instances and endpoints
6. describe_connections - List existing connection test results with filtering
7. describe_replication_tasks - List and describe replication tasks with detailed filtering
8. create_replication_task - Create replication tasks with table mappings and CDC settings
9. start_replication_task - Start replication tasks (new, resume, or reload operations)
10. stop_replication_task - Stop running replication tasks safely
11. describe_table_statistics - Get detailed table-level replication statistics
12. reload_replication_task_tables - Reload specific tables during replication

Database Engine Support

• mysql - MySQL databases (on-premises and RDS)
• oracle - Oracle databases (on-premises and RDS)
• postgres - PostgreSQL databases (on-premises and RDS)
• mariadb - MariaDB databases (on-premises and RDS)
• aurora - Amazon Aurora (MySQL-compatible)
• aurora-postgresql - Amazon Aurora (PostgreSQL-compatible)

User Experience

Before This Change

Limited Database Migration Capabilities
• AI assistants had no way to manage AWS DMS resources
• Users had to manually create replication instances, endpoints, and tasks
• No automated migration workflow orchestration
• Manual intervention required for connection testing and monitoring
• No guidance on DMS migration best practices
• Complex setup required for table-level operations and CDC configuration

After This Change

Comprehensive Database Migration Management
• AI assistants can safely manage complete DMS migration workflows
• Automated replication instance and endpoint creation with best practices
• Connection testing before migration execution to prevent failures
• Real-time monitoring with table-level granularity and progress tracking
• Intelligent guidance on migration strategies and troubleshooting
• Natural language database migration operations with comprehensive error handling

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 (88 tests, 94% coverage)
• Changes are documented (comprehensive README with examples)

Is this a breaking change? No

RFC issue number: #1254

Checklist:

• [N/A] Migration process documented
• [N/A] 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.

[krokoko]

Hi @nikoshet , thank you for this contribution ! One question: are the operations (tools) listed here simple wrappers over boto3 ? If yes, can these actions be done through the aws-api-mcp-server ?

[nikoshet]

Yes they can be implemented through the aws-api-mcp-server, i guess that we can close the PR!

[github-actions]

This pull request is now marked as stale because it hasn't seen activity for a while. Add a comment or it will be closed soon. If you wish to exclude this issue from being marked as stale, add the "backlog" label.

[nikoshet]

Yes they can be implemented through the aws-api-mcp-server, i guess that we can close the PR!