Deprecation Notice: Deprecated MCP Servers (Updated March 2026)

[MichaelWalker-git]

Deprecated MCP Servers (Updated March 2026)

The following servers have been deprecated. Each displays a deprecation warning at runtime and in its README. No further releases will be published.

Deprecated Server	Replacement	Migration Guide
terraform-mcp-server	HashiCorp official terraform-mcp-server	migration-terraform.md
cfn-mcp-server	aws-iac-mcp-server	migration-cfn.md
cdk-mcp-server	aws-iac-mcp-server	migration-cfn.md
cost-explorer-mcp-server	billing-cost-management-mcp-server	migration-cost-explorer.md
nova-canvas-mcp-server	bedrock-image-mcp-server	migration-nova-canvas.md
aws-bedrock-data-automation-mcp-server	boto3 API or aws-api-mcp-server	migration-bedrock-data-automation.md
cloudwatch-appsignals-mcp-server	cloudwatch-applicationsignals-mcp-server	migration-cloudwatch-appsignals.md
core-mcp-server	Configure individual MCP servers directly	migration-core.md
aws-diagram-mcp-server	Diagram agent skill	migration-diagram.md
git-repo-research-mcp-server	Context7	migration-git-repo-research.md
ccapi-mcp-server	aws-iac-mcp-server	migration-ccapi.md
syntheticdata-mcp-server	Native AI data generation	—
frontend-mcp-server	Kiro specs	—
code-doc-gen-mcp-server	Native AI documentation capabilities	—
aws-msk-mcp-server	aws-api-mcp-server or MSK boto3 APIs	—

If you have questions about any of these deprecations, please comment below or open a new issue.

[aniruddhaadak80]

This is a solid deprecation notice because it does more than say use something else. The migration guides and capability differences are the important part, especially where the replacement is not a drop-in match.nnOne thing that often helps in transitions like this is being explicit about which user profiles should move immediately versus which can safely stay on the deprecated package for a while. That makes the migration feel operational rather than purely advisory.