Mmcp.market

EnvSync-LE MCP server

by nolindnaidoo·io.github.nolindnaidoo/envsync-le·v2.2.5
No reviews yet

Compare dotenv files and report which keys are missing or extra, by name only.

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

1 stars37 downloads/wk

Reviews

Write one

Nobody has reviewed EnvSync-LE yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

EnvSync-LE tools (1)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • compare_env_files

    Compare dotenv files and report which keys are missing from which file, and which are extra relative to a template. Takes file contents directly. Only key NAMES are returned \u2014 never values \u2014 because a dotenv file is where credentials live and the answer does not need them. In "auto" mode the reference is the union of all keys, so nothing can be extra; "template" mode compares every file

Public scan report

scanner v0.1.9 · 2026-09-23 · same rubric, same numbers if you re-run it

no findings
  • Code scan2 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

What the publisher says

From the EnvSync-LE repository's README, as published. We do not edit it. Read it on GitHub

EnvSync-LE: Zero Hassle .env Sync Spot missing keys across your .env files before they bite Automatic checks, a status bar counter, and a plain markdown report

Useful? A star or rating is how other developers find it —

★ GitHub ·

★ Open VSX ·

★ Marketplace

What it does

EnvSync-LE compares the variable names across the .env files in your workspace and tells you which files are missing which keys. It never reads or compares values, and it never modifies your files. Works in VS Code and in VS Code–based editors like Cursor and VSCodium (installable from Open VSX).

  • Automatic checks — a debounced sync check runs whenever a watched .env file changes
  • Status bar counter — the current issue count, one click away from the full report
  • Markdown report — Show Details (Ctrl+Alt+S / Cmd+Alt+S) lists every missing key per file
  • Three comparison modes — auto (union of all keys), manual (only the files you list), template (validate everything against one reference file; also reports keys a file has that the template lacks)
  • Ignore list — temporarily exclude files (e.g. .env.example) from checking

Install

Use it from an AI agent

The same engine runs as an MCP server, so an agent can call it directly instead of you running a command.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Install directly

Runs npx -y envsync-le-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add envsync-le -- npx -y envsync-le-mcp
Add to Cursor

EnvSync-LE: common questions

Is EnvSync-LE MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the EnvSync-LE safety report
How do I install EnvSync-LE?
It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does EnvSync-LE need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is EnvSync-LE maintained?
The last commit was 2 days ago (2026-09-22). The latest release is v2.2.5.

More from nolindnaidoo →