-
Notifications
You must be signed in to change notification settings - Fork 822
Description
When converting plugins to Kiro format using convert or install with --to kiro, MCP servers and hooks are not included in the output.
MCP servers: When a plugin uses .mcp.json (instead of defining mcpServers directly in plugin.json), the converter doesn't parse the file correctly and drops all MCP servers. Tested with the 4 AWS agent plugins from awslabs/agent-plugins — all 7 MCP servers across the plugins were skipped.
Additionally, the converter warns "Kiro only supports stdio" and skips HTTP/remote servers, but Kiro now supports remote MCP servers.
Hooks: Plugins that define hooks (e.g., PostToolUse) have them skipped during Kiro conversion. The converter warns that Kiro hooks use a different format but doesn't attempt conversion.
Reproduction:
git clone https://github.com/awslabs/agent-plugins.git
# MCP servers get dropped
bunx @every-env/compound-plugin convert ./agent-plugins/plugins/deploy-on-aws --to kiro
# Hooks get skipped
bunx @every-env/compound-plugin convert ./agent-plugins/plugins/aws-serverless --to kiroSkills convert and activate correctly in Kiro, but without the MCP servers they depend on, they can't function.