env-contract-mcp

Purpose: Keeping environment variables consistent, documented, and validated across development and deployment environments.

Inferred · not functionally tested

Audience: developers and DevOps teams

Inferred · not functionally tested

Functions: data_extraction, workflow_automation

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: Open Source · platforms: CLI, WEB · deployment: browser, cli, api_only, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: github.com. These links do not verify the individual claims.

In the Frameworks & runtimes space, env-contract-mcp takes a focused approach. Inferred · not functionally tested: It focuses on keeping environment variables consistent, documented, and validated across development and deployment environments. Inferred · not functionally tested: It is built as an open-source project for developers and DevOps teams. Basis unknown · not verified: The project is open source (Open Source). Basis unknown · not verified: It ships for the web, the command line, and API, and it can be self-hosted.

Behind env-contract-mcp is mrfentmen. Inferred · not functionally tested: Among its 5 catalogued features are environment contracts, variable validation, and MCP server. Inferred · not functionally tested: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.