
Heimdall
io.github.lchampzPublished by GitHub account lchampzv1.0.1Updated Oct 24, 2026
🛡️ MCP Heimdall - Advanced Environment Architect & Diagnostic Tool.
Overview
A local MCP server that inspects a developer machine's environment — runtimes, PATH, Docker, ports, processes, resources and project dependencies — and suggests
- What you can do
- Inspect the system: OS and architecture details, Node, Python, Java and Kotlin versions, PATH entries and critical dev tool versions, Docker daemon status with containers and images, and connectivity to services such as GitHub, NPM and Docker Hub. Audit projects: scan for NPM vulnerabilities and outdated packages, detect missing node_modules or virtual environments, and compare .env files against templates to flag missing keys. Monitor resources: CPU load, memory and disk usage, top resource-consuming and orphan processes, and active listening ports. Clean up and fix: find large files and temporary build directories, kill the process on a given port, and run all checks to get prioritized, AI
- When to use it
- Useful when an assistant needs to diagnose why a local project will not build or run, verify installed tool versions against requirements, check Docker or network connectivity, or get concrete fix suggestions for a broken development environment.
- Requirements
- Runs as a local process on the user's machine, installed from the npm package and started with Node.js. Desktop only; no web execution. Optionally set the DEBUG environment variable to enable debug logging. No authentication is declared.
Installation
In SourceWeft
- Open Heimdall in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
🛡️ 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
🚀 Installation
Quick Integration
Run this command to automatically configure Heimdall in your current workspace:
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:
For Developers
- Clone the repository
- Install dependencies:
npm install - Build the project:
npm run build - Run in dev mode:
npm run dev
đź“„ License
MIT
Source: README.md at commit b568d0d
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.