docs: add Kiro to supported MCP hosts across all documentation

Complete documentation update to include Kiro IDE as supported MCP host platform:

- README.md: Add Kiro to introduction, key features, and supported hosts section
- MCPHostConfiguration.md: Add Kiro to supported platforms and validation lists
- CLIReference.md: Add Kiro-specific CLI arguments and usage examples
- Tutorial series: Add Kiro to all host platform references for consistency

Ensures complete documentation consistency across user journey from
project introduction through advanced tutorials and CLI reference.

All host lists now include Kiro in alphabetical order with consistent
description: 'Kiro IDE with MCP support'

Author: LittleCoinCoin

README.md

@@ -4,15 +4,15 @@
 
 ## Introduction
 
-Hatch is the package manager for managing Model Context Protocol (MCP) servers with environment isolation, multi-type dependency resolution, and multi-host deployment. Deploy MCP servers to Claude Desktop, VS Code, Cursor, and other platforms with automatic dependency management.
+Hatch is the package manager for managing Model Context Protocol (MCP) servers with environment isolation, multi-type dependency resolution, and multi-host deployment. Deploy MCP servers to Claude Desktop, VS Code, Cursor, Kiro, and other platforms with automatic dependency management.
 
 The canonical documentation is at `docs/index.md` and published at <https://hatch.readthedocs.io/en/latest/>.
 
 ## Key Features
 
 - **Environment Isolation** — Create separate, isolated workspaces for different projects without conflicts
 - **Multi-Type Dependency Resolution** — Automatically resolve and install system packages, Python packages, Docker containers, and Hatch packages
-- **Multi-Host Deployment** — Deploy MCP servers to Claude Desktop, Claude Code, VS Code, Cursor, LM Studio, and Google Gemini CLI
+- **Multi-Host Deployment** — Deploy MCP servers to Claude Desktop, Claude Code, VS Code, Cursor, Kiro, LM Studio, and Google Gemini CLI
 - **Package Validation** — Ensure packages meet schema requirements before distribution
 - **Development-Focused** — Optimized for rapid development and testing of MCP server ecosystems
 
@@ -24,6 +24,7 @@ Hatch supports deployment to the following MCP host platforms:
 - **Claude Code** — Claude integration for VS Code with MCP capabilities
 - **VS Code** — Visual Studio Code with the MCP extension for tool integration
 - **Cursor** — AI-first code editor with built-in MCP server support
+- **Kiro** — Kiro IDE with MCP support
 - **LM Studio** — Local LLM inference platform with MCP server integration
 - **Google Gemini CLI** — Command-line interface for Google's Gemini model with MCP support
 

docs/articles/users/CLIReference.md

@@ -412,6 +412,9 @@ Syntax:
 | `--exclude-tools` | multiple | Tool blocklist - these tools will be excluded (Gemini). Space-separated values. | none |
 | `--env-file` | string | Path to environment file (Cursor, VS Code, LM Studio) | none |
 | `--input` | multiple | Input variable definitions format: type,id,description[,password=true] (VS Code) | none |
+| `--disabled` | flag | Disable the MCP server (Kiro) | false |
+| `--auto-approve-tools` | multiple | Tool names to auto-approve (Kiro). Can be used multiple times. | none |
+| `--disable-tools` | multiple | Tool names to disable (Kiro). Can be used multiple times. | none |
 | `--dry-run` | flag | Preview configuration without applying changes | false |
 | `--auto-approve` | flag | Skip confirmation prompts | false |
 | `--no-backup` | flag | Skip backup creation before configuration | false |
@@ -475,6 +478,37 @@ Configure MCP server 'my-server' on host 'gemini'? [y/N]: y
 [SUCCESS] Successfully configured MCP server 'my-server' on host 'gemini'
 ```
 
+**Example - Kiro Configuration**:
+
+```bash
+$ hatch mcp configure my-server --host kiro --command python --args server.py --auto-approve-tools weather,calculator --disable-tools debug
+
+Server 'my-server' created for host 'kiro':
+  name: UPDATED None --> 'my-server'
+  command: UPDATED None --> 'python'
+  args: UPDATED None --> ['server.py']
+  autoApprove: UPDATED None --> ['weather', 'calculator']
+  disabledTools: UPDATED None --> ['debug']
+
+Configure MCP server 'my-server' on host 'kiro'? [y/N]: y
+[SUCCESS] Successfully configured MCP server 'my-server' on host 'kiro'
+```
+
+**Example - Kiro with Disabled Server**:
+
+```bash
+$ hatch mcp configure my-server --host kiro --command python --args server.py --disabled
+
+Server 'my-server' created for host 'kiro':
+  name: UPDATED None --> 'my-server'
+  command: UPDATED None --> 'python'
+  args: UPDATED None --> ['server.py']
+  disabled: UPDATED None --> True
+
+Configure MCP server 'my-server' on host 'kiro'? [y/N]: y
+[SUCCESS] Successfully configured MCP server 'my-server' on host 'kiro'
+```
+
 **Example - Remote Server Configuration**:
 
 ```bash

docs/articles/users/MCPHostConfiguration.md

@@ -19,6 +19,7 @@ Hatch currently supports configuration for these MCP host platforms:
 - **Claude Code** - Anthropic's VS Code extension
 - **VS Code** - Microsoft Visual Studio Code with MCP extensions
 - **Cursor** - AI-powered code editor
+- **Kiro** - Kiro IDE with MCP support
 - **LM Studio** - Local language model interface
 - **Gemini** - Google's AI development environment
 
@@ -184,7 +185,7 @@ hatch mcp configure my-server --host claude-desktop --command python --args serv
 hatch mcp configure my-server --host claude-desktop --command python --args server.py --no-backup
 ```
 
-### Manual Backup Management
+### Restore From Backups
 
 ```bash
 # List available backups
@@ -201,267 +202,13 @@ Backups are stored in `~/.hatch/mcp_host_config_backups/` with the naming patter
 mcp.json.<hostname>.<timestamp>
 ```
 
-## Troubleshooting
-
-### Host Not Available
-
-If a host is not detected:
-
-```bash
-# Check which hosts are available
-hatch mcp hosts
-
-# Get detailed host information
-hatch mcp hosts --verbose
-```
-
-**Common solutions:**
-- Ensure the host application is installed
-- Check that configuration directories exist
-- Verify file permissions for configuration files
-
-### Configuration Validation Errors
-
-If server configuration is rejected:
-
-```bash
-# Validate configuration before applying
-hatch mcp validate my-server \
-  --host claude-desktop \
-  --command python \
-  --args server.py
-```
-
-**Common issues:**
-- Claude hosts require absolute paths for commands
-- Some hosts don't support environment variables
-- URL format must include protocol (http:// or https://)
-
-### Backup and Recovery Issues
-
-If configuration changes fail:
-
-```bash
-# Check backup status
-hatch mcp backup list --host claude-desktop
-
-# Restore previous working configuration
-hatch mcp restore --host claude-desktop --latest
-```
-
-### Permission Issues
-
-If you encounter permission errors:
-
-```bash
-# Check configuration file permissions
-ls -la ~/.config/Code/User/settings.json  # VS Code example
-
-# Fix permissions if needed
-chmod 644 ~/.config/Code/User/settings.json
-```
-
-## Advanced Usage
-
-### Batch Operations
-
-Configure multiple servers efficiently:
-
-```bash
-# Configure multiple servers from a configuration file
-hatch mcp configure --from-file servers.json --host claude-desktop
-
-# Remove multiple servers
-hatch mcp remove server1,server2,server3 --host claude-desktop
-```
-
-### Environment Integration
-
-Integrate with Hatch environment management:
-
-```bash
-# Configure servers for current environment
-hatch env use my-project
-hatch mcp sync --all-hosts
-
-# Configure servers when switching environments
-hatch env use production
-hatch mcp sync --hosts claude-desktop,cursor
-```
-
-### Automation and Scripting
-
-Use Hatch MCP configuration in automation:
-
-```bash
-# Non-interactive configuration
-hatch mcp configure my-server \
-  --host claude-desktop \
-  --command python \
-  --args server.py \
-  --auto-approve
-
-# Check configuration status in scripts
-if hatch mcp list --host claude-desktop | grep -q "my-server"; then
-  echo "Server is configured"
-fi
-```
-
-## Best Practices
-
-### Development Workflow
-
-1. **Start with one host** - Configure and test on your primary development host first
-2. **Use absolute paths** - Especially for Claude hosts, use absolute paths to avoid issues
-3. **Test configurations** - Use `--dry-run` to preview changes before applying
-4. **Keep backups** - Don't use `--no-backup` unless you're certain about changes
-
-### Production Considerations
-
-1. **Environment synchronization** - Use `hatch mcp sync` to maintain consistency across hosts
-2. **Backup management** - Regularly clean up old backups to manage disk space
-3. **Configuration validation** - Validate configurations before deployment
-4. **Host availability** - Check host availability before attempting configuration
-
-### Security Considerations
-
-1. **Credential management** - Avoid storing sensitive credentials in configuration files
-2. **File permissions** - Ensure configuration files have appropriate permissions
-3. **Backup security** - Protect backup files containing configuration data
-4. **Network security** - Use HTTPS for remote server configurations
-
-## Integration with Other Hatch Features
-
-### Package Management
-
-MCP host configuration integrates with Hatch package management:
-
-```bash
-# Install package and configure MCP server
-hatch package add weather-toolkit
-hatch mcp sync --all-hosts  # Sync package's MCP server to hosts
-```
-
-### Environment Management
-
-Configuration follows environment boundaries:
-
-```bash
-# Different environments can have different MCP configurations
-hatch env create development
-hatch env use development
-hatch mcp configure dev-server --host claude-desktop --command python --args dev_server.py
-
-hatch env create production  
-hatch env use production
-hatch mcp configure prod-server --host claude-desktop --command python --args prod_server.py
-```
-
-This ensures that MCP server configurations are isolated between different project environments, maintaining clean separation of development, testing, and production setups.
-
-## Advanced Synchronization Patterns
-
-### Pattern-Based Server Selection
-
-Use regular expressions for flexible server selection during synchronization:
-
-```bash
-# All API servers
-hatch mcp sync --from-env my_hatch_env --to-host claude-desktop --pattern ".*api.*"
-
-# Development tools
-hatch mcp sync --from-env my_hatch_env --to-host cursor --pattern "^dev-"
-
-# Production servers
-hatch mcp sync --from-host production-host --to-host staging-host --pattern ".*prod.*"
-```
-
-### Multi-Host Batch Operations
-
-Efficiently manage configurations across multiple host platforms:
-
-```bash
-# Replicate configuration across all hosts
-hatch mcp sync --from-host claude-desktop --to-host all
-
-# Selective multi-host deployment
-hatch mcp sync --from-env production --to-host claude-desktop,cursor,vscode
-
-# Environment-specific multi-host sync
-hatch mcp sync --from-env development --to-host all --pattern "^dev-"
-```
-
-### Complex Filtering Scenarios
-
-Combine filtering options for precise control:
-
-```bash
-# Multiple specific servers
-hatch mcp sync --from-env my_hatch_env --to-host all --servers api-server,db-server,cache-server
-
-# Pattern-based with host filtering
-hatch mcp sync --from-host claude-desktop --to-host cursor --pattern ".*tool.*"
-```
-
-## Management Operations
-
-### Server Removal Workflows
-
-Remove MCP servers from host configurations with safety features:
-
-```bash
-# Remove from single host
-hatch mcp remove server <server_name> --host <host-name>
-
-# Remove from multiple hosts
-hatch mcp remove server <server_name> --host <host1>,<host2>,<host3>
-
-# Remove from all configured hosts
-hatch mcp remove server <server_name> --host all
-```
-
-### Host Configuration Management
-
-Complete host configuration removal and management:
-
-```bash
-# Remove all MCP configuration for a host
-hatch mcp remove host <host-name>
-
-# Remove with environment specification
-hatch mcp remove server <server_name> --host <host> --env-var <environment>
-```
-
-### Safety and Backup Features
-
-All management operations include comprehensive safety features:
-
-**Automatic Backup Creation**:
-```bash
-# Backup created automatically
-hatch mcp remove server test-server --host claude-desktop
-# Output: Backup created: ~/.hatch/mcp_backups/claude-desktop_20231201_143022.json
-```
-
-**Dry-Run Mode**:
-```bash
-# Preview changes without executing
-hatch mcp remove server test-server --host claude-desktop --dry-run
-hatch mcp sync --from-env prod --to-host all --dry-run
-```
-
-**Skip Backup (Advanced)**:
-```bash
-# Skip backup creation (use with caution)
-hatch mcp remove server test-server --host claude-desktop --no-backup
-```
-
 ### Host Validation and Error Handling
 
 The system validates host names against available MCP host types:
 - `claude-desktop`
 - `cursor`
 - `vscode`
+- `kiro`
 - `lmstudio`
 - `gemini`
 - Additional hosts as configured

docs/articles/users/tutorials/03-author-package/05-checkpoint.md

@@ -18,6 +18,6 @@
 
 You now have the fundamental skills to create, validate, and install Hatch packages.
 
-**Continue to**: [Tutorial 04: MCP Host Configuration](../04-mcp-host-configuration/01-host-platform-overview.md) to learn how to deploy your packages to host platforms like Claude Desktop, VS Code, and Cursor with automatic dependency resolution.
+**Continue to**: [Tutorial 04: MCP Host Configuration](../04-mcp-host-configuration/01-host-platform-overview.md) to learn how to deploy your packages to host platforms like Claude Desktop, VS Code, Cursor, and Kiro with automatic dependency resolution.
 
 For more advanced topics, explore the [CLI Reference](../../CLIReference.md) and [Security and Trust](../../SecurityAndTrust.md) guides.

docs/articles/users/tutorials/04-mcp-host-configuration/01-host-platform-overview.md

@@ -3,7 +3,7 @@
 ---
 **Concepts covered:**
 
-- MCP host platforms (Claude Desktop, VS Code, Cursor, etc.)
+- MCP host platforms (Claude Desktop, VS Code, Cursor, Kiro, etc.)
 - Hatch's role as package manager with host configuration features
 - Host platform configuration files and formats
 - Package-first vs. direct configuration approaches
@@ -53,6 +53,7 @@ Hatch currently supports configuration for these MCP host platforms:
 - [**Claude Code**](https://claude.com/product/claude-code) - Anthropic's AI Command Line Interface
 - [**Cursor**](https://cursor.com/) - AI-powered code editor
 - [**VS Code**](https://code.visualstudio.com/) - Microsoft Visual Studio Code
+- [**Kiro**](https://kiro.ai/) - Kiro IDE with MCP support
 - [**LM Studio**](https://lmstudio.ai/) - Local language model interface
 - [**Gemini**](https://github.com/google-gemini/gemini-cli) - Google's AI Command Line Interface
 

docs/articles/users/tutorials/04-mcp-host-configuration/04-environment-synchronization.md

@@ -17,7 +17,7 @@
 
 ---
 
-This tutorial teaches you how to deploy MCP servers to multiple host platforms using environments as project isolation containers. You'll learn to maintain clean separation between different projects while efficiently deploying their servers to host applications like Claude Desktop, Cursor, and VS Code.
+This tutorial teaches you how to deploy MCP servers to multiple host platforms using environments as project isolation containers. You'll learn to maintain clean separation between different projects while efficiently deploying their servers to host applications like Claude Desktop, Cursor, Kiro, and VS Code.
 
 ## Understanding Project Isolation with Environments