io.github.lchampz/heimdall
🛡️ MCP Heimdall - Advanced Environment Architect & Diagnostic Tool.
Que pouvez-vous faire avec 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.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
@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>"
}
}
}
}
Variables d'environnement
DEBUGEnable debug logging (true/false)
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent 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
Questions fréquentes
Qu'est-ce que io.github.lchampz/heimdall ?
🛡️ MCP Heimdall - Advanced Environment Architect & Diagnostic Tool.
Comment installer io.github.lchampz/heimdall ?
Il s'exécute sur votre machine. Dans Claude Code : claude mcp add heimdall -e 'DEBUG=<DEBUG>' -- npx -y @lchampz/mcp-heimdall@1.0.1. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour io.github.lchampz/heimdall ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
io.github.lchampz/heimdall est-il open source ?
Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.
Qui maintient io.github.lchampz/heimdall ?
Il est publié par lchampz. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.