Prerequisites
- Kiro (latest version recommended)
- Node.js 20.x or later
Installing Mouse
- Open the Extensions panel in Kiro (
Ctrl+Shift+X/Cmd+Shift+X) - Search for Mouse by HIC AI, Inc.
- Click Install
- Open the Command Palette (
Ctrl+Shift+P/Cmd+Shift+P) and runMouse: Initialize Workspace
This creates a .hic directory in your project and generates the MCP configuration file at .kiro/settings/mcp.json.
Configuration
The workspace initialization creates the following configuration automatically. If you need to configure it manually, create .kiro/settings/mcp.json with:
{
"mcpServers": {
"hic_local": {
"type": "stdio",
"command": "node",
"args": ["./.hic/mcp/src/core/server.js"],
"env": {
"HIC_AGENT_ADAPTER": "kiro",
"HIC_ALLOWED_DIRECTORIES": "./"
}
}
}
}
Steering Instructions
Kiro's built-in file-editing tools cannot be disabled. To ensure Kiro uses Mouse tools for all file-editing operations, add the following to your steering instructions at .kiro/steering/:
Always use Mouse (hic_local MCP) tools for all file navigation and editing operations. Do not use built-in file-editing tools.
IMPORTANT
Unlike other clients that inject user-provided system instructions after each turn, Kiro only injects steering instructions at the beginning of each conversation. In longer conversations, Kiro may gradually revert to using its built-in tools. If this happens, remind Kiro to use Mouse tools.
Verifying the Connection
Ask your AI assistant:
"Use Mouse's
get_file_metadatatool to check the metadata of any file in this workspace."
If the assistant successfully calls the tool and returns file metadata, Mouse is working correctly. Check the status bar; it should show Mouse: Trial or Mouse: Licensed.