docs: Fix argument in README for well-architected-security-mcp-server - #4466
Open
orsifacundo wants to merge 1 commit into
Open
docs: Fix argument in README for well-architected-security-mcp-server#4466orsifacundo wants to merge 1 commit into
orsifacundo wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Changes
The README for
well-architected-security-mcp-serverdocuments theargsfor the MCP configuration as:The correct entry point provided by the package is
awslabs.well-architected-security-mcp-server, notwell-architected-security-mcp-server. This PR updates the documented configuration to:User experience
Before: Users copying the configuration from the README get a connection failure:
After: The MCP server connects successfully using the correct executable name.
Checklist
If your change doesn't seem to apply, please leave them unchecked.
I have reviewed the contributing guidelines
I have performed a self-review of this change
Changes have been tested
Changes are documented
Is this a breaking change? N
RFC issue number: N/A
Checklist:
Migration process documented
Implement warnings (if it can live side by side)
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.