Skip to content

awslabs.core-mcp-server: failure to load specific roles #1657

@bspaulding1

Description

@bspaulding1

Describe the bug

I initially added environment variables for nearly all roles, and the server would crash. By process of elimination from running on the command line, I found that I had to remove the following roles in order to get the core server to successfully load:

  • CONTAINER_ORCHESTRATION=true
  • SERVERLESS_ARCHITECTURE=true
  • NOSQL_DB_SPECIALIST=true
  • MESSAGING_EVENTS=true

Expected Behavior

I expected the core server to be able to load all of the roles without failure

Current Behavior

the mcp server fails to load with a variety of errors depending on which of the culprit roles are included

Reproduction Steps

Run the following for the error, which can be resolved by removing the aforementioned culprits:

FASTMCP_LOG_LEVEL=ERROR
AWS_FOUNDATION=true
DEV_TOOLS=true
CI_CD_DEVOPS=true
CONTAINER_ORCHESTRATION=true
SERVERLESS_ARCHITECTURE=true
ANALYTICS_WAREHOUSE=true
DATA_PLATFORM_ENG=true
FRONTEND_DEV=true
SOLUTIONS_ARCHITECT=true
FINOPS=true
MONITORING_OBSERVABILITY=true
CACHING_PERFORMANCE=true
SECURITY_IDENTITY=true
SQL_DB_SPECIALIST=true
NOSQL_DB_SPECIALIST=true
TIMESERIES_DB_SPECIALIST=true
MESSAGING_EVENTS=true
uvx awslabs.core-mcp-server@latest

Possible Solution

No response

Additional Information/Context

No response

OS

macOS Sequoia 15.7.1

Server

core-mcp-server

Server Version

1.0.0

Region experiencing the issue

n/a - local machine

Other information

No response

Service quota

  • I have reviewed the service quotas for this construct

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingneeds-triageThis needs to be handled, it is the first automatically assigned label to issues.

    Type

    No type

    Projects

    Status

    To triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions