This gives Claude direct access to your development environment through tools for parsing dotenv files, checking port availability, and inspecting system info. You get operations like env_list_variables to see what's in your .env, env_compare_files to diff against .env.example, port_check to identify what's using port 3000, and system_info for OS and runtime versions. The env_generate_example tool creates sanitized templates by stripping values while preserving structure. Useful when Claude needs to troubleshoot configuration issues, verify dependencies are installed, find an open port for a new service, or detect missing environment variables before deployment.
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.
.env file and list all variable keys (values masked).env vs .env.example to find missing or extra variables.env file.env.example from an existing .env file (strips values, keeps comments, adds placeholders)package.json scriptsdocker-compose.yml filenpm install
npm run build
Add to your MCP client config:
{
"mcpServers": {
"env-tools": {
"command": "node",
"args": ["D:/products/mcp-servers/mcp-env-tools/dist/index.js"]
}
}
}
MIT