Incomplete configuration for awslab mcp servers executed by MCP Toolkit?

[meyayl]

It appears the awslab mcp servers from the mcp catalog have an incomplete configuration.

For instance, https://hub.docker.com/mcp/server/awslabs-dynamodb/overview lists environment Variables AWS_REGION and AWS_PROFILE. This would be sufficient, if the mcp server runs as native process on the host, so it's able to access the aws config folder ~/.aws (Mac/Linux) or ${env:USERPROFILE}/.aws (Windows Powershell).

In case the mcp server is runing in a container, this is not sufficient, as the aws configuration folder is not mounted into the container. Another, less favorable, approach would be tp add further environment variables AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY and AWS_SESSION_TOKEN, but those are rather short living and inconvient to use, compared to mounting the config folder.

This bit explains what is required: https://github.com/awslabs/mcp?tab=readme-ov-file#running-mcp-servers-in-containers

In case the the aws config folder is already implicitly mounted, please mention in the docs of the mcp server.

[richbourne]

I have the same issue, as mentioned here: https://forums.docker.com/t/docker-mcp-error-nonetype-object-has-no-attribute-error/150672