Amazon SageMaker Well-Architected MCP Server
Integrates with Amazon SageMaker to validate workloads against the AWS Well-Architected Framework across all six pillars (Security, Reliability, Performance Efficiency, Cost Optimization, Operational Excellence, Sustainability). Provides tools to check endpoints, training jobs, notebook instances, and models, returning findings with severity levels and actionable recommendations.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Amazon SageMaker Well-Architected MCP Server Validate my SageMaker endpoint for reliability"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Amazon SageMaker Well-Architected MCP Server
The Amazon SageMaker Well-Architected MCP server provides agents with tools to validate SageMaker workloads against all six AWS Well-Architected Framework pillars: Security, Reliability, Performance Efficiency, Cost Optimization, Operational Excellence, and Sustainability.
Available Features
Well-Architected Validation
Provides comprehensive tools for validating SageMaker resources (endpoints, training jobs, notebook instances, and models) against AWS best practices across all six Well-Architected pillars. Each validation returns findings with severity levels and actionable recommendations. See the validators documentation for detailed information on the supported tools.
Related MCP server: AWS CDK MCP Server
Prerequisites
Quickstart
This quickstart guide walks you through the steps to configure the Amazon SageMaker Well-Architected MCP Server for use with Kiro, Cursor, and other compatible IDEs.
Kiro | Cursor | VS Code |
Set up Kiro
See the Kiro IDE documentation or the Kiro CLI documentation for details.
For global configuration, edit ~/.kiro/settings/mcp.json. For project-specific configuration, edit .kiro/settings/mcp.json in your project directory.
The example below includes the --allow-sensitive-data-access flag for accessing detailed resource configurations:
For Mac/Linux:
```
{
"mcpServers": {
"awslabs.sagemaker-wa-mcp-server": {
"command": "uvx",
"args": [
"awslabs.sagemaker-wa-mcp-server@latest",
"--allow-sensitive-data-access"
],
"env": {
"FASTMCP_LOG_LEVEL": "ERROR"
},
"autoApprove": [],
"disabled": false
}
}
}
```For Windows:
```
{
"mcpServers": {
"awslabs.sagemaker-wa-mcp-server": {
"command": "uvx",
"args": [
"--from",
"awslabs.sagemaker-wa-mcp-server@latest",
"awslabs.sagemaker-wa-mcp-server.exe",
"--allow-sensitive-data-access"
],
"env": {
"FASTMCP_LOG_LEVEL": "ERROR"
},
"autoApprove": [],
"disabled": false
}
}
}
```Verify your setup by running the /tools command in the Kiro CLI to see the available SageMaker Well-Architected MCP tools.
This server provides comprehensive Well-Architected validation for SageMaker workloads with 51 checks across all six pillars. For broader AWS API access and documentation lookup, you can also use AWS API MCP Server and AWS Documentation MCP Server.
Configurations
Arguments
The args field in the MCP server definition specifies the command-line arguments passed to the server when it starts. These arguments control how the server is executed and configured. For example:
For Mac/Linux:
{
"mcpServers": {
"awslabs.sagemaker-wa-mcp-server": {
"command": "uvx",
"args": [
"awslabs.sagemaker-wa-mcp-server@latest",
"--allow-sensitive-data-access"
],
"env": {
"AWS_PROFILE": "your-profile",
"AWS_REGION": "us-east-1"
}
}
}
}For Windows:
{
"mcpServers": {
"awslabs.sagemaker-wa-mcp-server": {
"command": "uvx",
"args": [
"--from",
"awslabs.sagemaker-wa-mcp-server@latest",
"awslabs.sagemaker-wa-mcp-server.exe",
"--allow-sensitive-data-access"
],
"env": {
"AWS_PROFILE": "your-profile",
"AWS_REGION": "us-east-1"
}
}
}
}Command Format
The command format differs between operating systems:
For Mac/Linux:
awslabs.sagemaker-wa-mcp-server@latest- Specifies the latest package/version specifier for the MCP client config.
For Windows:
--from awslabs.sagemaker-wa-mcp-server@latest awslabs.sagemaker-wa-mcp-server.exe- Windows requires the--fromflag to specify the package and the.exeextension.
--allow-sensitive-data-access (optional)
Enables access to sensitive data such as detailed resource configurations, tags, and endpoint config details. This flag is required for tools that access potentially sensitive information.
Default: true (Access to sensitive data is allowed by default)
Example: remove
--allow-sensitive-data-accessfrom theargslist in your MCP server definition to disable it.
Environment variables
The env field in the MCP server definition allows you to configure environment variables that control the behavior of the SageMaker Well-Architected MCP server. For example:
{
"mcpServers": {
"awslabs.sagemaker-wa-mcp-server": {
"env": {
"FASTMCP_LOG_LEVEL": "ERROR",
"AWS_PROFILE": "my-profile",
"AWS_REGION": "us-west-2"
}
}
}
}FASTMCP_LOG_LEVEL (optional)
Sets the logging level verbosity for the server.
Valid values: "DEBUG", "INFO", "WARNING", "ERROR", "CRITICAL"
Default: "WARNING"
Example:
"FASTMCP_LOG_LEVEL": "ERROR"
AWS_PROFILE (optional)
Specifies the AWS profile to use for authentication.
Default: None (If not set, uses default AWS credentials).
Example:
"AWS_PROFILE": "my-profile"
AWS_REGION (optional)
Specifies the AWS region where SageMaker resources are validated, which will be used for all AWS service operations.
Default: None (If not set, uses default AWS region).
Example:
"AWS_REGION": "us-west-2"
Security & Permissions
Features
The SageMaker Well-Architected MCP Server implements the following security features:
AWS Authentication: Uses AWS credentials from the environment for secure authentication.
SSL Verification: Enforces SSL verification for all AWS API calls.
Least Privilege: Only requires read/describe/list permissions on SageMaker resources.
User Agent Tracking: All API calls include a custom user agent for auditability.
Considerations
When using the SageMaker Well-Architected MCP Server, consider the following:
AWS Credentials: The server needs permission to describe and list SageMaker resources.
Network Security: Ensure the environment running the server has network access to AWS APIs.
Authentication: Use appropriate authentication mechanisms for AWS resources.
Authorization: Configure IAM with read-only SageMaker permissions.
Data Protection: Resource configurations may contain sensitive information.
Logging and Monitoring: Enable logging and monitoring for SageMaker resources.
Permissions
The SageMaker Well-Architected MCP Server performs only read-only operations, which is recommended and considered generally safe for production environments. Below are the tools available:
Read-only mode (default):
validate_sagemaker_resource,validate_all_endpoints,list_sagemaker_resources,get_pillar_details.
autoApprove (optional)
An array within the MCP server definition that lists tool names to be automatically approved by the MCP Server client, bypassing user confirmation for those specific tools. Since all operations are read-only, auto-approving all tools is safe. For example:
For Mac/Linux:
{
"mcpServers": {
"awslabs.sagemaker-wa-mcp-server": {
"command": "uvx",
"args": [
"awslabs.sagemaker-wa-mcp-server@latest"
],
"env": {
"AWS_PROFILE": "sagemaker-wa-mcp-readonly-profile",
"AWS_REGION": "us-east-1",
"FASTMCP_LOG_LEVEL": "INFO"
},
"autoApprove": [
"validate_sagemaker_resource",
"validate_all_endpoints",
"list_sagemaker_resources",
"get_pillar_details"
]
}
}
}For Windows:
{
"mcpServers": {
"awslabs.sagemaker-wa-mcp-server": {
"command": "uvx",
"args": [
"--from",
"awslabs.sagemaker-wa-mcp-server@latest",
"awslabs.sagemaker-wa-mcp-server.exe"
],
"env": {
"AWS_PROFILE": "sagemaker-wa-mcp-readonly-profile",
"AWS_REGION": "us-east-1",
"FASTMCP_LOG_LEVEL": "INFO"
},
"autoApprove": [
"validate_sagemaker_resource",
"validate_all_endpoints",
"list_sagemaker_resources",
"get_pillar_details"
]
}
}
}Role Scoping Recommendations
In accordance with security best practices, we recommend the following:
Create dedicated IAM roles to be used by the SageMaker Well-Architected MCP Server with the principle of "least privilege."
Use read-only roles since the server only performs describe and list operations.
Implement resource tagging to limit actions to specific resources.
Enable AWS CloudTrail to audit all API calls made by the server.
Regularly review the permissions granted to the server's IAM role.
Use IAM Access Analyzer to identify unused permissions that can be removed.
Sensitive Information Handling
IMPORTANT: Do not pass secrets or sensitive information via allowed input mechanisms:
Do not include secrets or credentials in tool parameters.
Do not pass sensitive information directly in the prompt to the model.
Avoid using MCP tools for creating secrets, as this would require providing the secret data to the model.
Instead of passing secrets through MCP:
Use AWS Secrets Manager or Parameter Store to store sensitive information.
Configure proper IAM roles for service accounts.
Use IAM roles for service accounts (IRSA) for AWS service access.
File System Access and Operating Mode
Important: This MCP server is intended for STDIO mode only as a local server using a single user's credentials. The server runs with the same permissions as the user who started it and has complete access to the file system.
Security and Access Considerations
Read-Only Operations: The server does not write to the file system or modify any AWS resources
Host Credentials: The server uses the host's AWS credentials configuration
Do Not Modify for Network Use: This server is designed for local STDIO use only; network operation introduces additional security risks
General Best Practices
Resource Naming: Use descriptive names for SageMaker resources.
Error Handling: Check for errors in tool responses and handle them appropriately.
Prioritize Findings: Address HIGH severity findings first, then MEDIUM, then LOW.
Regular Audits: Run validations periodically to catch configuration drift.
Monitoring: Monitor resource status regularly.
Security: Follow AWS security best practices for SageMaker resources.
General Troubleshooting
Permission Errors: Verify that your AWS credentials have the necessary read-only SageMaker permissions.
Resource Not Found: Verify the resource name and region are correct.
SageMaker API Errors: Verify that the SageMaker resources exist and are accessible.
Network Issues: Check that the environment has network access to AWS APIs.
Client Errors: Verify that the MCP client is configured correctly.
Log Level: Increase the log level to DEBUG for more detailed logs.
For service-specific issues, consult the relevant documentation:
Version
Current MCP server version: 0.1.0
Available Tools
5 toolsget_pillar_detailsB
Get detailed information about a specific Well-Architected pillar and its checks.
Returns the pillar description and all validation checks that are performed
for the specified pillar.
Args:
ctx: MCP context
pillar: Pillar name
Returns:
PillarInfoResponse with pillar details and checks
Inputs: pillar (required). Returns: Response model for pillar information.
list_sagemaker_resourcesB
List SageMaker resources available for validation.
Returns endpoints, training jobs, notebook instances, and models
in the specified region.
Args:
ctx: MCP context
region_name: AWS region name (default: us-east-1)
profile_name: AWS profile name (optional)
Returns:
ListResourcesResponse with resource lists
Inputs: region_name, profile_name. Returns: Response model for listing SageMaker resources.
validate_all_endpointsA
Validate all SageMaker endpoints in a region against Well-Architected pillars.
Scans all endpoints in the specified region and returns aggregated findings
across all six Well-Architected pillars.
Args:
ctx: MCP context
region_name: AWS region name (default: us-east-1)
profile_name: AWS profile name (optional)
Returns:
ValidateAllResponse with aggregated findings
Inputs: region_name, profile_name. Returns: Response model for batch validation.
validate_all_resourcesA
Validate all SageMaker resources in a region against Well-Architected pillars.
Scans all endpoints, training jobs, notebook instances, and models in the
specified region. Returns an on-screen summary and generates a single
comprehensive HTML report (wa-report.html) with all findings.
Args:
ctx: MCP context
region_name: AWS region name (default: us-east-1)
profile_name: AWS profile name (optional)
Returns:
ValidateAllResponse with aggregated findings and path to HTML report
Inputs: region_name, profile_name. Returns: Response model for batch validation.
validate_sagemaker_resourceA
Validate a SageMaker resource against all Well-Architected Framework pillars.
Checks security, reliability, performance efficiency, cost optimization,
operational excellence, and sustainability best practices for the specified resource.
## Supported Resource Types
- **endpoint**: SageMaker real-time inference endpoints
- **training_job**: SageMaker training jobs
- **notebook_instance**: SageMaker notebook instances
- **model**: SageMaker models
## Checks Performed
- **Security**: KMS encryption, VPC isolation, network isolation, inter-container encryption
- **Reliability**: Multi-instance endpoints, training timeouts, checkpointing, retry strategies
- **Performance**: Instance generation, data capture, data distribution, instance sizing
- **Cost**: Cost tags, spot training, serverless inference, lifecycle configs
- **Operational Excellence**: Operational tags, auto-scaling, experiment tracking
- **Sustainability**: Graviton instances, spot utilization, right-sizing
## Fallback Options
- If this tool fails, use AWS CLI: `aws sagemaker describe-endpoint --endpoint-name <name>`
- Or use the AWS SageMaker Console to review resource configurations
Args:
ctx: MCP context
resource_type: Type of SageMaker resource
resource_name: Name of the resource to validate
region_name: AWS region name (default: us-east-1)
profile_name: AWS profile name (optional)
Returns:
ValidateResourceResponse with findings and summary
Inputs: resource_name (required), resource_type (required), region_name, profile_name. Returns: Response model for single resource validation.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a clear purpose: validate a single resource, validate all endpoints, validate all resources, list resources, and get pillar details. The only potential confusion is between validate_all_endpoints and validate_all_resources, since the former is a subset of the latter, but the descriptions clearly distinguish their scopes.
Tool names follow a consistent verb_noun pattern: validate_*, list_*, and get_*. All names are snake_case and clearly indicate the action being performed, with no mixed conventions or vague verbs.
Five tools is well-scoped for a SageMaker Well-Architected validation server. Each tool serves a distinct and necessary function, covering single-resource validation, bulk validation, listing, and reference information without unnecessary bloat.
The tool set covers the full validation workflow: discover resources, validate an individual resource, validate all resources, validate all endpoints specifically, and understand the pillars being checked. There are no obvious dead ends or missing operations for the stated domain.
Related MCP Connectors
Lowers your AWS bill by helping you clean up and optimize your setup
Read-only, deterministic AI triage and readiness tools implementing Sophon's published rubrics.
Check AI work against requirements and return structured verdicts, findings, and repair steps.
Read-only AWS cost and security findings, priced in $/month, with a fix for each
Related MCP Servers
- -licenseNot gradedqualityNot gradedmaintenanceThis server provides guidance and recommendations based on AWS's Well-Architected Framework for cloud architectures, enabling analysis and review focused on operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability.-
- AlicenseBqualityDmaintenanceProvides guidance and tools for the AWS Cloud Development Kit, including infrastructure patterns, GenAI constructs, and security compliance via CDK Nag. It streamlines development by generating Bedrock Agent schemas and providing comprehensive documentation for Lambda layers and AWS Solutions Constructs.7Apache 2.0
- AlicenseNot gradedqualityDmaintenanceProvides comprehensive access to AWS Trusted Advisor checks and recommendations through both legacy and modern APIs, with support for AWS Organizations.3MIT

AWS SRA Verify MCP Serverofficial
AlicenseAqualityBmaintenanceEnables AI agents to assess AWS environments against the AWS Security Reference Architecture (SRA) by providing tools to discover, describe, and run security checks across AWS services and accounts.53Apache 2.0