docs: Add one-click "Add to Kiro" install badge#271
docs: Add one-click "Add to Kiro" install badge#271AnilMaktala wants to merge 1 commit intoGoogleCloudPlatform:mainfrom
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
There was a problem hiding this comment.
Code Review
This pull request updates the README.md to include Kiro as a supported MCP client and provides a new section with its configuration details. A review comment suggests removing unnecessary indentation from the Kiro configuration code block to ensure consistent Markdown formatting and rendering.
| ```json | ||
| { | ||
| "mcpServers": { | ||
| "cloud-run": { | ||
| "command": "npx", | ||
| "args": ["-y", "@google-cloud/cloud-run-mcp"] | ||
| } | ||
| } | ||
| } | ||
| ``` |
There was a problem hiding this comment.
The code block for the Kiro configuration is indented by 3 spaces, which is inconsistent with other top-level code blocks in this document (such as the one at the beginning of the file). In Markdown, fenced code blocks should not be indented unless they are nested within a list item or another block element. Removing the leading spaces will ensure consistent formatting and correct rendering across different Markdown parsers.
| ```json | |
| { | |
| "mcpServers": { | |
| "cloud-run": { | |
| "command": "npx", | |
| "args": ["-y", "@google-cloud/cloud-run-mcp"] | |
| } | |
| } | |
| } | |
| ``` | |
| { | |
| "mcpServers": { | |
| "cloud-run": { | |
| "command": "npx", | |
| "args": ["-y", "@google-cloud/cloud-run-mcp"] | |
| } | |
| } | |
| } |
|
@AnilMaktala Can you please sign the Google CLA? |
Adds one-click install for Kiro, an AI-powered IDE.
When clicked, Kiro auto-configures this MCP server — no manual JSON editing needed.
Only the README is modified — no other content changed.