mcpField
E
envdiff

envdiff

Local
github.com/CloudCorpRecordsDeveloper Tools0Updated 1w ago
Repository

About envdiff

envdiff compares local and CI environment descriptors for developers diagnosing environment differences. It reports variable names without exposing values.

Key features

  1. 01Compare Node, OS, and lockfile fields
  2. 02Find environment variables present on one side
  3. 03Flag differing values by variable name
  4. 04Return a JSON difference count

Use cases

  1. 01Diagnose local-versus-CI discrepancies
  2. 02Check environment differences without exposing secrets

MCP support

The MCP server exposes `diff_environments`, which compares required local and CI descriptors.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "cloudcorprecords-envdiff": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/envdiff"
      ]
    }
  }
}
Run commandnpx -y @reneturcios/envdiff

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@reneturcios/envdiff0.1.0
ocighcr.io/cloudcorprecords/envdiff:0.1.0

Tools

1

Saved tool list · updated 1w ago

ParameterTypeRequiredDescription
ciobjectYesThe CI environment descriptor
ci.osstringNoOperating system identifier
ci.envobjectNoEnvironment variables as a string map (values are compared, never echoed)
ci.nodestringNoNode.js version string
ci.lockfile_presentbooleanNoWhether a lockfile is present
localobjectYesThe local environment descriptor
local.osstringNoOperating system identifier
local.envobjectNoEnvironment variables as a string map (values are compared, never echoed)
local.nodestringNoNode.js version string
local.lockfile_presentbooleanNoWhether a lockfile is present

Details

From the project README

envdiff

"It works on my machine" — which part of the machine? envdiff compares two environment descriptors, typically a developer's local environment and a CI environment, and reports exactly where they differ:

  • Node version, OS, and lockfile presence, compared as fields (a missing field is reported as null)
  • env vars present on one side only, by key
  • env vars whose values differ — by key name only. Values are compared but never echoed into the report, so a descriptor may carry secrets without leaking them.

A descriptor is a small JSON object: {"node": "20.11.0", "os": "linux", "env": {"CI": "true"}, "lockfile_present": true} — every field optional.

Pure local computation: no network, no configuration.

CLI

npx @reneturcios/envdiff diff local.json ci.json
npx @reneturcios/envdiff --version

Output is the comparison report as JSON, with a summary.total_differences count. Exit codes: 0 on success (differences are a result, not an error), 1 on a runtime error (unreadable or invalid descriptor), 2 on a usage error.

MCP server

npx -y @reneturcios/envdiff mcp

MCP client config:

{
  "mcpServers": {
    "envdiff": {
      "command": "npx",
      "args": ["-y", "@reneturcios/envdiff", "mcp"]
    }
  }
}
Tools

  • diff_environments — Compare two environment descriptors.

    • local (object, required) — the local descriptor
    • ci (object, required) — the CI descriptor

    Each descriptor: node (string), os (string), env (string map), lockfile_present (boolean), all optional.

Docker

docker run -i ghcr.io/cloudcorprecords/envdiff
docker run --rm -v "$PWD:/w" ghcr.io/cloudcorprecords/envdiff diff /w/local.json /w/ci.json

Development

npm install
npm run build   # tsc -> dist/
npm test        # tsx --test test/*.test.ts (pure local, no network)
npm run dev     # run the CLI from source

License

MIT — Copyright (c) 2026 Rene Turcios

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.