Env

io.github.rog0xPublished by GitHub account rog0xv1.0.2Updated Oct 24, 2026

Dotenv parser, ports, system info for AI agents

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Lets an assistant inspect local environment configuration: parse .env files, generate templates, check ports, and report system and tool versions.

What you can do
Provides tools for working with local development environment configuration. It parses .env files to list variable keys with values masked, detects missing or duplicate variables, and compares .env against .env.example. It also generates .env.example files, finds variables referenced in package.json scripts or docker-compose.yml, checks whether ports are in use or free, lists processes on ports, reports OS, CPU, memory, disk and Node/npm/Python/Git/Docker versions, and verifies installed tools and PATH directories.
When to use it
Useful when setting up or debugging a project's environment: checking which variables are missing before a run, keeping .env.example in sync, resolving port conflicts, or confirming required tools and versions are installed. Best for local development machines rather than remote or shared environments.
Requirements
Runs as a local stdio process on the user's machine, installed from the npm package @rog0x/mcp-env-tools and started with Node.js. No authentication, API keys, or environment variables are declared. It reads local files such as .env, package.json and docker-compose.yml, and inspects local ports, processes and system information.
Before you install
It reads local configuration files and system details, so results may expose project structure and environment variable names, though values are masked in listings. Port and process inspection reports local process information. It is a local desktop-only server and does not appear to write, send, or delete data, but review what it reads before pointing it at sensitive directories.

Installation

In SourceWeft

  1. Open Env in the dashboard and add it to a workspace.
  2. 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

@rog0x/mcp-env-tools

MCP server providing environment and configuration tools for AI agents. Helps with parsing .env files, generating templates, checking ports, inspecting system info, and verifying tool dependencies.

Tools

Environment Parser

  • env_list_variables - Parse a .env file and list all variable keys (values masked)
  • env_detect_missing - Check if required environment variables are present and populated
  • env_compare_files - Compare .env vs .env.example to find missing or extra variables
  • env_find_duplicates - Find duplicate variable keys in a .env file

Environment Generator

  • env_generate_example - Generate .env.example from an existing .env file (strips values, keeps comments, adds placeholders)
  • env_detect_from_package_json - Detect environment variables referenced in package.json scripts
  • env_detect_from_docker_compose - Detect environment variables referenced in a docker-compose.yml file

Port Checker

  • port_check - Check if a specific port is in use and identify the process
  • port_find_available - Find available ports within a given range
  • port_list_processes - List processes using specific ports

System Info

  • system_info - OS, CPU, memory, disk, Node/npm/Python/Git/Docker versions

Dependency Checker

  • deps_check_tools - Check if specified tools are installed and get their versions
  • deps_check_versions - Verify installed tools meet minimum version requirements
  • deps_verify_path - Analyze the system PATH for common tool directories

Setup

bash
npm installnpm run build

Configuration

Add to your MCP client config:

json
{  "mcpServers": {    "env-tools": {      "command": "node",      "args": ["D:/products/mcp-servers/mcp-env-tools/dist/index.js"]    }  }}

License

MIT

Source: README.md at commit 0054460

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

50% 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