This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Reason given by maintainers: load individual MCPs
Core MCP Server
⚠️ DEPRECATION NOTICE: This server is deprecated and will no longer receive updates. Modern MCP clients (Kiro, Cursor, VS Code) support multi-server configurations natively, making the proxy/orchestration pattern unnecessary. Please configure the individual MCP servers you need directly. See the migration guide for a role-to-server mapping.
MCP server that provides a starting point for using MCP servers for AWS through a dynamic proxy server strategy based on role-based environment variables.
Features
Planning and orchestration
- Provides tool for prompt understanding and translation to AWS services
Dynamic Proxy Server Strategy
The Core MCP Server implements a proxy server strategy that dynamically imports and proxies other MCP servers based on role-based environment variables. This allows you to create tailored server configurations for specific use cases or roles without having to manually configure each server.
Role-Based Server Configuration
You can enable specific roles by setting environment variables. Each role corresponds to a logical grouping of MCP servers that are commonly used together for specific use cases.
Important: Environment variable names can be either lowercase with hyphens or uppercase with underscores (e.g.,
aws-foundationorAWS_FOUNDATION). Some systems may not support the hyphenated format, so choose the format that works best for your environment.
| Role Environment Variable | Description | Included MCP Servers |
|---|---|---|
aws-foundation |
AWS knowledge and API servers | aws-knowledge-server, aws-api-server |
dev-tools |
Development tools | git-repo-research-server, code-doc-gen-server, aws-knowledge-server |
ci-cd-devops |
CI/CD and DevOps | cdk-server, cfn-server |
container-orchestration |
Container management | eks-server, ecs-server, finch-server |
serverless-architecture |
Serverless development | serverless-server, lambda-tool-server, stepfunctions-tool-server, sns-sqs-server |
analytics-warehouse |
Data analytics and warehousing | redshift-server, timestream-for-influxdb-server, dataprocessing-server, syntheticdata-server |
data-platform-eng |
Data platform engineering | dynamodb-server, s3-tables-server, dataprocessing-server |
frontend-dev |
Frontend development | frontend-server, nova-canvas-server |
solutions-architect |
Solution architecture | diagram-server, pricing-server, cost-explorer-server, syntheticdata-server, aws-knowledge-server |
finops |
Financial operations | cost-explorer-server, pricing-server, cloudwatch-server, billing-cost-management-server |
monitoring-observability |
Monitoring and observability | cloudwatch-server, cloudwatch-appsignals-server, prometheus-server, cloudtrail-server |
caching-performance |
Caching and performance | elasticache-server, memcached-server |
security-identity |
Security and identity | iam-server, support-server, well-architected-security-server |
sql-db-specialist |
SQL database specialist | postgres-server, mysql-server, aurora-dsql-server, redshift-server |
nosql-db-specialist |
NoSQL database specialist | dynamodb-server, documentdb-server, keyspaces-server, neptune-server |
timeseries-db-specialist |
Time series database specialist | timestream-for-influxdb-server, prometheus-server, cloudwatch-server |
messaging-events |
Messaging and events | sns-sqs-server, mq-server |
healthcare-lifesci |
Healthcare and life sciences | healthomics-server |
Benefits of the Proxy Server Strategy
- Simplified Configuration: Enable multiple servers with a single environment variable
- Reduced Duplication: Servers are imported only once, even if needed by multiple roles
- Tailored Experience: Create custom server configurations for specific use cases
- Flexible Deployment: Easily switch between different server configurations
Usage Notes
- If no roles are enabled, the Core MCP Server will still provide its basic functionality (prompt_understanding) but won't import any additional servers
- You can enable multiple roles simultaneously to create a comprehensive server configuration
- The proxy strategy ensures that each server is imported only once, even if it's needed by multiple roles
Note: Not all MCP servers for AWS are represented in these logical groupings. For specific use cases, you may need to install additional MCP servers directly. See the main README for a complete list of available MCP servers.
Prerequisites
- Python 3.12 or higher
- uv - Fast Python package installer and resolver
- AWS credentials configured with Bedrock access
- Node.js (for UVX installation support)
Installation
| Kiro | Cursor | VS Code |
|---|---|---|
Configure the MCP server in your MCP client configuration (e.g., for Kiro, edit ~/.kiro/settings/mcp.json):
{
"mcpServers": {
"awslabs-core-mcp-server": {
"command": "uvx",
"args": [
"awslabs.core-mcp-server@latest"
],
"env": {
"FASTMCP_LOG_LEVEL": "ERROR",
"aws-foundation": "true",
"solutions-architect": "true"
// Add other roles as needed
},
"autoApprove": [],
"disabled": false
}
}
}
To enable specific role-based server configurations, add the corresponding environment variables to the env section of your MCP client configuration. For example, the configuration above enables the aws-foundation and solutions-architect roles, which will import the corresponding MCP servers.
Windows Installation
For Windows users, the MCP server configuration format is slightly different:
{
"mcpServers": {
"awslabs-core-mcp-server": {
"disabled": false,
"timeout": 60,
"type": "stdio",
"command": "uv",
"args": [
"tool",
"run",
"--from",
"awslabs.core-mcp-server@latest",
"awslabs.core-mcp-server.exe"
],
"env": {
"FASTMCP_LOG_LEVEL": "ERROR",
"AWS_PROFILE": "your-aws-profile",
"AWS_REGION": "us-east-1",
"aws-foundation": "true",
"solutions-architect": "true"
// Add other roles as needed
}
}
}
}
or docker after a successful docker build -t awslabs/core-mcp-server .:
{
"mcpServers": {
"awslabs-core-mcp-server": {
"command": "docker",
"args": [
"run",
"--rm",
"--interactive",
"--env",
"FASTMCP_LOG_LEVEL=ERROR",
"--env",
"aws-foundation=true",
"--env",
"solutions-architect=true",
"awslabs/core-mcp-server:latest"
],
"env": {},
"disabled": false,
"autoApprove": []
}
}
}
Tools and Resources
The server exposes the following tools through the MCP interface:
prompt_understanding- Helps to provide guidance and planning support when building AWS Solutions for the given prompt
Release files for awslabs.core-mcp-server 1.0.27
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| awslabs_core_mcp_server-1.0.27.tar.gz | 409.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| awslabs_core_mcp_server-1.0.27-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 432.2 kB
Release files / awslabs_core_mcp_server-1.0.27.tar.gz
| Download URL | awslabs_core_mcp_server-1.0.27.tar.gz |
|---|---|
| Size | 409.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a75febfe46bf80b63c7e2530ace1bd915e283ce5eae9316c74a1e52f61047381
|
|
BLAKE2b-256 checksum How to use checksums |
70fb871efc6f8374597dd8d2bd8c68be52e89967aadaf2345bf9e4dc5179d706
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 27, 2026.
Transparency logRelease files / awslabs_core_mcp_server-1.0.27-py3-none-any.whl
| Download URL | awslabs_core_mcp_server-1.0.27-py3-none-any.whl |
|---|---|
| Size | 23.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
991c7220f249b6e512946e949115ecf514599a34c1f7e1545b46af0083539aa1
|
|
BLAKE2b-256 checksum How to use checksums |
3f19de9af0feeb975a5e1e3462f87066cd2bfd6a0209b8a24a811d8234a9e9c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 27, 2026.
Transparency log