AWS amazonq documentation change
Summary
Updated MCP configuration documentation with file locations, legacy support details, and path corrections
Security assessment
The changes clarify configuration management and legacy file support but do not explicitly address security vulnerabilities or document new security features. The legacy configuration note highlights potential misconfiguration risks but does not indicate an active security issue.
Diff
diff --git a/amazonq/latest/qdeveloper-ug/mcp-ide.md b/amazonq/latest/qdeveloper-ug/mcp-ide.md index 43d823373..3a2aa1a2f 100644 --- a//amazonq/latest/qdeveloper-ug/mcp-ide.md +++ b//amazonq/latest/qdeveloper-ug/mcp-ide.md @@ -5 +5 @@ -With the IDEAdding an MCP serverTroubleshooting your MCP configurationEnabling an MCP serverDisabling an MCP serverDeleting an MCP server that is currently enabledDeleting an MCP server that is currently disabledReviewing and adjusting tool permissions +MCP IDE config filesAccessing the UIAdding an MCP serverTroubleshooting your MCP configurationEnabling an MCP serverDisabling an MCP serverDeleting an MCP server that is currently enabledDeleting an MCP server that is currently disabledReviewing and adjusting tool permissions @@ -10,0 +11,32 @@ This page covers IDE-specific options for configuring MCP servers. +## Understanding MCP configuration files for Q Developer in the IDE + +When you use the GUI to add an MCP server to Q Developer in the IDE, the configuration is stored in one of two files: + + * At the global scope: ~/.aws/amazonq/default.json + + * At the local scope: .amazonq/default.json + + + + +However, for legacy reasons, it is also possible to put MPC configuration information in two other locations: + + * At the global scope: ~/.aws/amazonq/mcp.json + + * At the local scope: .amazonq/mcp.json + + + + +Q Developer gives precedence to workspace level configurations for MCP servers, their permissions, and the settings stored. + +###### Note + +If you have already set up an MCP configuration in an mcp.json file, and you are using the MCP configuration GUI for the first time, you will see that configuration in the GUI. + +Support for legacy mcp.json files is enabled by the useLegacyMcpJson field in your global default.json config file. By default, this field is set to true. For more information, see [UseLegacyMcpJson Field](https://github.com/aws/amazon-q-developer-cli/blob/main/docs/agent-format.md#uselegacymcpjson-field) in the Q Developer CLI GitHub repo. + +Note that the mcp.json files may also be used by the Q CLI. + +For information about how to set granular controls on MCP tooling, see the [Built-in tools reference](https://github.com/aws/amazon-q-developer-cli/blob/main/docs/built-in-tools.md). + @@ -40 +72 @@ To add an HTTP MCP server to the IDE: -If you select global scope, the MCP server configuration is stored in ~/.aws/amazonq/agents/default.json and available across all your projects. If you select local scope, the configuration is stored in .aws/amazonq/agents/default.json within your current project. +If you select global scope, the MCP server configuration is stored in ~/.aws/amazonq/default.json and available across all your projects. If you select local scope, the configuration is stored in .amazonq/default.json within your current project. @@ -75 +107 @@ To add an STDIO MCP server to the IDE: -If you select global scope, the MCP server configuration is stored in ~/.aws/amazonq/mcp.json and available across all your projects. If you select local scope, the configuration is stored in .amazonq/mcp.json within your current project. +If you select global scope, the MCP server configuration is stored in ~/.aws/amazonq/default.json and available across all your projects. If you select local scope, the configuration is stored in .amazonq/default.json within your current project.