No existing tool was built for DynamoDB's unique model. dynamochange is purpose-built — GSI lifecycle management, TTL policies, streams, table class — all versioned in YAML and tracked in a history table inside DynamoDB itself.
Every feature maps to a real DynamoDB API — not a lowest-common-denominator abstraction that works for Postgres and kind-of-works for DynamoDB.
dynamochange ships a Model Context Protocol server — letting Claude, Cursor, and any MCP-compatible AI assistant query your DynamoDB schema history, run drift detection, validate migrations, and plan deployments without leaving the chat.
Connect your AI assistant to dynamochange and unlock schema-aware conversations — ask about pending migrations, get drift reports, validate YAML scripts before running them, or generate new migration files from a natural language description of the GSI or table change you need.
The dynamochange MCP server exposes schema tools through the standard Model Context Protocol. Works with Claude Desktop, Cursor, Windsurf, and any editor with MCP support. Your AWS credentials stay local — the MCP server reads your existing dynamochange profiles.
Every operation follows the same --profile flag, --dry-run support, and JSON output contract. Scripts in CI; humans at the terminal.
--dry-run to preview without touching AWS.The honest comparison nobody else publishes.
| Capability | dynamochange | Generic tool A | Generic tool B | Terraform |
|---|---|---|---|---|
| Table creation / deletion | ✓ | ✗ | ✗ | ✓ |
| GSI lifecycle (create, monitor, drop) | ✓ | ✗ | ✗ | partial |
| TTL management | ✓ | ✗ | ✗ | ✓ |
| DynamoDB Streams | ✓ | ✗ | ✗ | ✓ |
| Table class (Standard / IA) | ✓ | ✗ | ✗ | ✓ |
| Migration history & audit trail | ✓ | ✗ | ✗ | ✗ |
| Versioned rollback | ✓ | ✗ | ✗ | ✗ |
| Drift detection | ✓ | ✗ | ✗ | plan only |
| Per-environment credential isolation | ✓ | ✗ | ✗ | ✓ |
| GSI backfill monitoring | ✓ | ✗ | ✗ | ✗ |
| Policy-as-code contracts | ✓ | ✗ | partial | ✗ |
| MCP server for AI agents | ✓ | ✗ | ✗ | ✗ |