Decide whether we should implement the feature demonstrated in this PR #74
Having config file makes sense so that user can write the config in a file and launch a proxy directly, they can also track the config in git etc.
Use Case
mcp-proxy-for-aws --config config.yaml
Proposed Solution
It is possible that the endpoint parameter can be path to a file. Then we should load the config from a file.
mcp-proxy-for-aws my-bedrock-runtime-mcp-server.yaml
content of my-bedrock-runtime-mcp-server.yaml
endpoint: "https://your-service.us-east-1.amazonaws.com/mcp"
service: "bedrock-agentcore"
profile: "default"
region: "us-east-1"
read_only: false
log_level: "INFO"
Other Information
No response
Acknowledgements
Describe the feature (Security related? please follow https://github.com/aws/mcp-proxy-for-aws/security/policy to report them to AWS Security directly.)
Decide whether we should implement the feature demonstrated in this PR #74
Having config file makes sense so that user can write the config in a file and launch a proxy directly, they can also track the config in git etc.
Use Case
Proposed Solution
It is possible that the
endpointparameter can be path to a file. Then we should load the config from a file.content of my-bedrock-runtime-mcp-server.yaml
Other Information
No response
Acknowledgements