npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

env-manager-mcp

v1.0.5

Published

Env Manager MCP server — read, write, and validate .env files

Readme

env-manager-mcp

Env Manager MCP server. Read, write, and validate .env files.

No external dependencies. Pure Node.js fs.

Install

npm install -g env-manager-mcp

Usage

Claude Desktop / Cursor / OpenCode

Add to your MCP config:

{
  "mcpServers": {
    "env-manager": {
      "command": "npx",
      "args": ["-y", "env-manager-mcp"]
    }
  }
}

Tools

read_env — Read Env File

Read and parse a .env file into a key-value object.

Input:

{
  "path": ".env"
}

Output:

{
  "path": "/path/to/project/.env",
  "count": 5,
  "variables": {
    "DB_HOST": "localhost",
    "DB_PORT": "5432",
    "API_KEY": "sk-test-12345",
    "APP_NAME": "My Application",
    "DEBUG": "true"
  }
}

write_env — Write Env Variables

Write environment variables to a .env file. Preserves existing comments and format.

Input:

{
  "path": ".env",
  "variables": {
    "NEW_KEY": "new_value",
    "API_KEY": "updated_key"
  },
  "append": true
}

Output:

{
  "success": true,
  "path": "/path/to/project/.env",
  "written": 2,
  "variables": ["NEW_KEY", "API_KEY"]
}

validate_env — Validate Env File

Check if required keys exist in a .env file. Returns missing keys.

Input:

{
  "path": ".env",
  "required_keys": ["DB_HOST", "API_KEY", "MISSING_KEY"]
}

Output:

{
  "path": "/path/to/project/.env",
  "valid": false,
  "present": ["DB_HOST", "API_KEY"],
  "missing": ["MISSING_KEY"],
  "total_required": 3
}

Features

| Feature | Description | |---------|-------------| | Parse .env files | Handles comments, quoted values, inline comments | | Preserve format | Keeps existing comments and structure when writing | | Multi-env support | Works with .env.local, .env.development, etc. | | Validation | Check for required keys before deployment |

Design

| Feature | Why | |---------|-----| | Zero runtime deps | Only @modelcontextprotocol/sdk and zod | | Native fs | No dotenv dependency — pure parsing | | Format preservation | Comments and structure kept intact | | Multi-env | Any .env file path supported |

License

MIT