io.github.lchampz/heimdall
🛡️ MCP Heimdall - Advanced Environment Architect & Diagnostic Tool.
What can you do with io.github.lchampz/heimdall?
- Workspace Janitor: Find large files (>50MB) and temporary directories (
dist,build, etc.) for cleanup. - Path Inspector: Audit the
PATHvariable and verify versions of critical dev tools (git,brew,make). - Process Explorer: Identify top CPU/Memory consumers and potential orphan Node/Python processes.
- Docker Sight: Check Docker daemon status, list containers and images.
- Connectivity Check: Ping essential services (GitHub, NPM, Docker Hub) to verify internet status.
- Project Doctor: Scan Project for NPM vulnerabilities and outdated packages.
- Resource Watcher: Monitor CPU load, memory usage, and disk space.
- Port Manager: List active listening ports and kill processes blocking specific ports.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
@lchampz/mcp-heimdallclaude mcp add heimdall -e 'DEBUG=<DEBUG>' -- npx -y @lchampz/mcp-heimdall@1.0.1
{
"mcpServers": {
"heimdall": {
"command": "npx",
"args": [
"-y",
"@lchampz/mcp-heimdall@1.0.1"
],
"env": {
"DEBUG": "<DEBUG>"
}
}
}
}
Environment variables
DEBUGEnable debug logging (true/false)
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
🛡️ MCP Heimdall
Advanced Environment Architect & Diagnostic Tool for Model Context Protocol (MCP).
Heimdall helps AI agents understand, verify, and fix their execution environment. It provides detailed insights into system architecture, runtime versions, dependencies, and environment variables, along with actionable correction suggestions.
✨ Features
- Workspace Janitor: Find large files (>50MB) and temporary directories (
dist,build, etc.) for cleanup. - Path Inspector: Audit the
PATHvariable and verify versions of critical dev tools (git,brew,make). - Process Explorer: Identify top CPU/Memory consumers and potential orphan Node/Python processes.
- Docker Sight: Check Docker daemon status, list containers and images.
- Connectivity Check: Ping essential services (GitHub, NPM, Docker Hub) to verify internet status.
- Project Doctor: Scan Project for NPM vulnerabilities and outdated packages.
- Resource Watcher: Monitor CPU load, memory usage, and disk space.
- Port Manager: List active listening ports and kill processes blocking specific ports.
- Runtime Inspector: Verify Node.js, Python, Java, and Kotlin versions against project requirements.
- Dependency Guard: detects missing
node_modulesor virtual environments. - Environment Audit: Compares
.envagainst templates and flags missing keys. - Intelligent Advisor: consolidated tool that suggests specific commands to fix environment issues.
🛠️ Tools
| Tool | Description |
|---|---|
system_info | Get OS and architecture details. |
inspect_runtimes | Check Node, Python, Java, and Kotlin versions. |
inspect_docker | Check Docker daemon status and list containers. |
check_connectivity | Test internet connection to essential dev services. |
project_doctor | Scan for NPM vulnerabilities and outdated packages. |
resource_watcher | Monitor CPU load, memory and disk usage. |
workspace_janitor | Find large files and temporary directories for cleanup. |
path_inspector | Inspect system PATH and critical dev tools versions. |
process_explorer | Identify top resource-consuming and orphan processes. |
audit_dependencies | Detect missing packages or broken environments. |
audit_env | Verify .env files against templates. |
list_ports | List all active listening ports and their processes. |
kill_port_process | Kill the process running on a specific port. |
suggest_corrections | The Core Feature: Runs all checks and returns prioritized solutions. |
🚀 Installation
Quick Integration
Run this command to automatically configure Heimdall in your current workspace:
npx @lchampz/mcp-heimdall integrate
This will create a .vscode/mcp.json file with the correct configuration.
For Users (via MCP Registry)
Add to your mcp.json or editor settings:
{
"servers": {
"heimdall": {
"command": "node",
"args": ["path/to/mcp-heimdall/build/index.js"]
}
}
}
For Developers
- Clone the repository
- Install dependencies:
npm install - Build the project:
npm run build - Run in dev mode:
npm run dev
📄 License
MIT
Frequently asked questions
What is io.github.lchampz/heimdall?
🛡️ MCP Heimdall - Advanced Environment Architect & Diagnostic Tool.
How do I install io.github.lchampz/heimdall?
It runs on your machine. In Claude Code: claude mcp add heimdall -e 'DEBUG=<DEBUG>' -- npx -y @lchampz/mcp-heimdall@1.0.1. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.lchampz/heimdall need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is io.github.lchampz/heimdall open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains io.github.lchampz/heimdall?
It is published by lchampz. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.