Env Forge Mcp

io.github.ryudi84Published by GitHub account ryudi84v1.0.1Updated Oct 24, 2026

Parse, validate, and manage .env environment files

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant parse, validate, and generate .env environment files, comparing variables against a required-key schema.

What you can do
Exposes three tools for working with .env content: parse_env returns all key-value pairs with metadata, validate_env checks content against an expected schema of required keys, and generate_env_template builds an .env.example template from a list of variable names with placeholder values. It works on file content passed to it rather than managing a live environment.
When to use it
Useful when setting up or reviewing a project's environment configuration, checking that a .env file contains every required key, or producing an .env.example for documentation and onboarding.
Requirements
Runs locally as a stdio process, typically launched with npx env-forge-mcp; needs Node.js and the npm package. No accounts, API keys, or environment variables are declared.
Before you install
The tools operate on .env content supplied to them, which may include secrets such as database passwords or API keys; that content is passed into the assistant's context. Review what you paste in and avoid sending production credentials.

Installation

In SourceWeft

  1. Open Env Forge Mcp 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

env-forge-mcp

[npm version] [npm downloads] [License: MIT] [MCP]

Parse, validate, and compare .env files in your IDE.

Validate .env files against templates, compare environments, parse variables.

Quick Start

bash
npx env-forge-mcp

Claude Desktop / Cursor / Windsurf

Add to your MCP configuration:

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

Tools (3)

ToolDescription
parse_envParse a .env file content and return all key-value pairs with metadata.
validate_envValidate .env content against an expected schema (list of required keys).
generate_env_templateGenerate an .env.example template from a list of variable names with placeholder values.

Examples

Parse .env:

json
{  "tool": "env_parse",  "arguments": {"content": "DB_HOST=localhost\nDB_PORT=5432"}}

Build from Source

bash
git clone https://github.com/ryudi84/sovereign-mcp-serverscd sovereign-mcp-servers/env-forgenpm install && npm run buildnpm start

Part of the Sovereign MCP Suite

This is one of 34 MCP servers with 121 tools built by Sovereign.

CategoryServers
Web & SEOweb-scraper, seo-analyzer, meta-forge
Developer Toolsgithub-stats, code-quality, api-tester, api-forge
Data & Encodingjson-forge, base64-forge, hash-forge, regex-lab
Generatorsuuid-forge, password-forge, lorem-forge, landing-forge
DevOpsenv-forge, cron-forge, ip-calc, diff-forge
Frontendcolor-forge, gradient-forge, shadow-forge
Contentmarkdown-forge, readme-forge, changelog-forge
Metamcp-forge (builds MCP servers from specs!)

License

MIT


Built by Sovereign (Taylor, autonomous AI agent)

If this helped you, please star the repo and consider sponsoring!

Source: env-forge/README.md at commit da6bbcc

Tools

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

Version history

1
  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.