Skip to content

docs: Add one-click 'Add to Kiro' install badge for filesystem server#4010

Open
Jay2113 wants to merge 7 commits intomodelcontextprotocol:mainfrom
Jay2113:add-kiro-badge
Open

docs: Add one-click 'Add to Kiro' install badge for filesystem server#4010
Jay2113 wants to merge 7 commits intomodelcontextprotocol:mainfrom
Jay2113:add-kiro-badge

Conversation

@Jay2113
Copy link
Copy Markdown

@Jay2113 Jay2113 commented Apr 22, 2026

Description

Hello from the Kiro team! 👋

Summary

Adds a one-click install button for Kiro, an agentic IDE, to the filesystem MCP server README. When clicked, Kiro automatically configures the filesystem server with the correct command and arguments — no manual JSON editing needed.

Changes

  • Added Usage with Kiro section to src/filesystem/README.md
  • Includes one-click Add to Kiro badge
  • Step-by-step manual configuration instructions for Kiro
  • Links to Kiro MCP documentation for both IDE and CLI

Publishing Your Server

Note: We are no longer accepting PRs to add servers to the README. Instead, please publish your server to the MCP Server Registry to make it discoverable to the MCP ecosystem.

To publish your server, follow the quickstart guide. You can browse published servers at https://registry.modelcontextprotocol.io/.

Server Details

  • Server:
  • Changes to:

Motivation and Context

Kiro supports one-click MCP server installation, but users currently have to manually configure the filesystem server by copying JSON into their settings. Adding the badge removes that friction and matches the existing VS Code and Claude Desktop install patterns already in this README.

How Has This Been Tested?

Validated the deep link in a browser which launches the mcp config in Kiro.

Breaking Changes

No

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant