Skip to content

Kiro Integration

Vheins x C.O.R.E edited this page Aug 14, 2026 · 1 revision

Integration with Kiro

Complete guide for connecting MCP Local Memory Service to Kiro — AI-powered IDE.

Prerequisites

  • Node.js 20+ installed
  • Kiro installed (download)
  • Internet access for first-time setup

Installation

npm install -g @vheins/local-memory-mcp

Global install gives faster startup and no re-download every time Kiro restarts; then configure the MCP server in Kiro (see below).

MCP Server Configuration

Kiro reads MCP configuration from a JSON file. There are two levels:

Workspace Level (per project)

Create a .kiro/settings/mcp.json file in your project root:

{
	"mcpServers": {
		"local-memory": {
			"command": "npx",
			"args": ["-y", "@vheins/local-memory-mcp"],
			"disabled": false
		}
	}
}

Or if already globally installed:

{
	"mcpServers": {
		"local-memory": {
			"command": "local-memory-mcp",
			"args": [],
			"disabled": false
		}
	}
}

User Level (all projects)

Create a ~/.kiro/settings/mcp.json file with the same structure.

Priority: workspace level overrides user level. If both files exist, the workspace configuration takes precedence.

Setup via Command Palette

  1. Open Kiro
  2. Open the command palette: Cmd + Shift + P (Mac) / Ctrl + Shift + P (Windows/Linux)
  3. Search for "MCP"
  4. Choose one of:
    • Kiro: Open workspace MCP config (JSON) — for this project only
    • Kiro: Open user MCP config (JSON) — for all projects
  5. Add the local-memory configuration as shown above
  6. Save the file — Kiro automatically reconnects to the server

Setup via Kiro Panel

  1. Open Kiro Panel (sidebar)
  2. Click the Open MCP Config icon
  3. Add the local-memory configuration
  4. Save the file

Auto-Approve Tools (Optional)

To prevent Kiro from asking for confirmation every time the agent calls a memory tool, you can auto-approve:

{
	"mcpServers": {
		"local-memory": {
			"command": "npx",
			"args": ["-y", "@vheins/local-memory-mcp"],
			"autoApprove": ["memory-read", "task-read", "standard-read"]
		}
	}
}

Read-only tools are safe to auto-approve. Write tools (memory-write, task-write, etc.) should still require confirmation. To auto-approve all tools (not recommended): "autoApprove": ["*"].

Disable Specific Tools

If there are tools you don't want to use:

{
	"mcpServers": {
		"local-memory": {
			"command": "npx",
			"args": ["-y", "@vheins/local-memory-mcp"],
			"disabledTools": ["memory-delete", "task-delete"]
		}
	}
}

Environment Variables

You can add environment variables for the server:

{
	"mcpServers": {
		"local-memory": {
			"command": "npx",
			"args": ["-y", "@vheins/local-memory-mcp"],
			"env": {
				"PORT": "3456"
			}
		}
	}
}

Or use variable expansion from the system:

{
	"mcpServers": {
		"local-memory": {
			"command": "npx",
			"args": ["-y", "@vheins/local-memory-mcp"],
			"env": {
				"STORAGE_PATH": "${HOME}/my-custom-path/memory"
			}
		}
	}
}

Temporarily Disable

To turn off the server without removing the configuration, set "disabled": true in the server config.

Verification

  1. Save the MCP configuration file
  2. Open Kiro Panel
  3. Check whether the local-memory server appears with status running
  4. Try asking the Kiro agent:

"What do you know about this project?"

If the agent responds with a list of memories or "No memories yet" (not an error), the connection is successful.

Running the Dashboard

Kiro can run the memory web dashboard:

npx @vheins/local-memory-mcp dashboard
# Open http://localhost:3456

Or ask the Kiro agent to run it — but the dashboard will run in a separate terminal.

Troubleshooting for Kiro

  • Server not showing in the panel: validate the JSON file syntax (cat .kiro/settings/mcp.json | python3 -m json.tool) and check PATH (which npx, which local-memory-mcp if global install).
  • Server error / disconnect: try running directly to see errors: npx -y @vheins/local-memory-mcp.
  • Configuration changes not taking effect: Kiro auto-reconnects when the file is saved; if not, search for "Kiro: Reload Window" in the command palette or restart Kiro.
  • Slow startup: if using npx, every Kiro restart may re-download the package — use the global install.

References

Clone this wiki locally