Puter MCP
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
Compare dotenv files and report which keys are missing or extra, by name only.
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server EnvSync-LE for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "envsync-le": { "command": "npx", "args": [ "-y", "envsync-le-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the EnvSync-LE tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"envsync-le": {
"command": "npx",
"args": [
"-y",
"envsync-le-mcp"
]
}
}
}Use EnvSync-LE and tell me what you can do for me, then show me one thing✓ If Claude says it is using EnvSync-LE or shows a EnvSync-LE tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect EnvSync-LE yet
EnvSync-LE runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect EnvSync-LE
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server EnvSync-LE for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user envsync-le -- npx -y envsync-le-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the EnvSync-LE tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user envsync-le -- npx -y envsync-le-mcpYou should see EnvSync-LE listed as connected
Use EnvSync-LE and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using EnvSync-LE or shows a EnvSync-LE tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server EnvSync-LE for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "envsync-le": { "command": "npx", "args": [ "-y", "envsync-le-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the EnvSync-LE tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use EnvSync-LE and tell me what you can do for me, then show me one thing✓ If Cursor says it is using EnvSync-LE or shows a EnvSync-LE tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server EnvSync-LE for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "envsync-le": { "type": "stdio", "command": "npx", "args": [ "-y", "envsync-le-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the EnvSync-LE tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use EnvSync-LE and tell me what you can do for me, then show me one thing✓ If VS Code says it is using EnvSync-LE or shows a EnvSync-LE tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Claude Code
claude mcp add --scope user envsync-le -- npx -y envsync-le-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"envsync-le": {
"command": "npx",
"args": [
"-y",
"envsync-le-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"envsync-le": {
"command": "npx",
"args": [
"-y",
"envsync-le-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"envsync-le": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"envsync-le-mcp"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: envsync-le-mcpBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 16, 2026
The registry name was verified with the GitHub account nolindnaidoo, which owns the repo
Code last changed 16 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for envsync-le-mcp@2.5.0
Checks only this package version, not every dependency · checked Nov 15, 2026
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 16 days ago, and the latest version (2.5.0) reached the registry 19 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Puter MCP, XcodeBuildMCP, Anki MCP Server, Sosumi, Zapier
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
MCP server for Anki flashcards: adaptive review, notes, media, and deck management via AnkiConnect.
Search and read Apple developer documentation, HIG, and WWDC transcripts as Markdown.
Connects AI to thousands of apps through one Zapier server, such as Gmail, Google Sheets and Slack. You choose which actions the AI may use.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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 ·
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).
.env file changesShow Details lists every missing key per fileauto (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).env.example) from checking| Where | What you get | Install |
|---|---|---|
| VS Code | The same comparison, live, in your editor | Marketplace |
| Cursor, VSCodium, Windsurf | The same extension | Open VSX |
| A terminal or a CI step | The same run over a whole tree, with exit codes | npx envsync-le · npm or cargo install envsync-le · crates.io |
| Any MCP agent, via Node | compare_env_files over stdio | npx envsync-le-mcp · npm |
The same engine runs as an MCP server, so an agent can call it directly instead of you running a command.
| Editor | How |
|---|---|
| VS Code 1.101+ | Nothing to install — the extension registers compare_env_files with agent mode |
| Claude Code | claude mcp add envsync-le -- npx -y envsync-le-mcp |
| Cursor, Windsurf, anything else | point it at npx envsync-le-mcp |
compare_env_files(files[], mode?, templatePath?, caseSensitive?, maxResults?)
Takes file contents directly and reports which keys are missing from which file. Only key names are returned, never values — a dotenv file is where credentials live and the answer does not need them.
The server takes content and returns data — it reads no files and makes no network requests of its own. Published as envsync-le-mcp on npm and as io.github.nolindnaidoo/envsync-le in the MCP registry.
Configuring it by hand — any host with an MCP config file
Most hosts read a JSON config. Add one entry:
{
"mcpServers": { "envsync-le": { "command": "npx", "args": ["-y", "envsync-le-mcp"] } } }
-y skips the install prompt on first run. Pin a version if you would rather not track releases — envsync-le-mcp@2.3.0.
Prefer not to go through npx on every launch? Install it once and point at the binary instead:
npm install -g envsync-le-mcp
{
"mcpServers": { "envsync-le": { "command": "envsync-le-mcp" } } }
It speaks MCP over stdio and needs no environment variables, no API key and no configuration of its own. To check it before wiring it into anything:
echo '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | npx -y envsync-le-mcp
That prints the tool list and exits — if you see compare_env_files, the server works.
| Filename | Type |
|---|---|
.env | base |
.env.local, .env.*.local | local override |
.env.example, .env.template | template |
.env.production, .env.prod | production |
.env.development, .env.dev | development |
.env.test | test |
anything.env, unknown segments | base |
Classification is segment-based on the basename — app.device.env is not "development", and Windows paths classify correctly.
The same comparison runs from a terminal or a CI step: a Rust CLI in crate/, sharing one corpus with the extension — crate/fixtures/ — so the two can never read a dotenv file differently. Install it from npm with npm install -g envsync-le (or run it with npx envsync-le) or from crates.io with cargo install envsync-le. Both install the same command and are held to the same output byte for byte.
envsync-le . # have these environments drifted? JSON on stdout when piped
envsync-le --template .env.example . # will this deploy break? envsync-le mcp # the same comparison over MCP on stdio
Install it from npm (envsync-le) or from crates.io (envsync-le). Both install the same envsync-le command.
npm install -g envsync-le # or run it once: npx envsync-le
cargo install envsync-le
.env: missing STRIPE_KEY, SENTRY_DSN (in .env.example) .env.production: missing SENTRY_DSN (in .env.example) out of sync — 2 files with mismatches across 3 files
The exit code is the product — 0 in sync, 1 out of sync, 2 malformed question. Finding no dotenv files at all is 0: there is nothing to be out of sync with. Unlike the extractors in this family there is no list to pipe onward; the number is the answer.
It never reads a value. Only key names are parsed, compared or reported, and three separate checks enforce that rather than a promise.
| Command | Description |
|---|---|
EnvSync-LE: Show Details | Run a sync check and open the markdown report |
EnvSync-LE: Compare Files | Compare the key sets of two or more selected .env files |
EnvSync-LE: Set Template | Mark a .env file as the reference template |
EnvSync-LE: Clear Template | Return to automatic comparison |
EnvSync-LE: Ignore File | Exclude a .env file from sync checking |
EnvSync-LE: Unignore File | Re-include a previously ignored file |
EnvSync-LE: Clear Ignored Files | Empty the ignore list |
EnvSync-LE: Open Settings | Open VS Code settings filtered to EnvSync-LE |
EnvSync-LE: Help & Troubleshooting | Built-in documentation |
No command is bound to a key by default. Give any of them one under Keyboard Shortcuts in the editor.
| Setting | Default | Description |
|---|---|---|
envsync-le.enabled | true | Master switch for sync checking |
envsync-le.watchPatterns | [".env*"] | Glob patterns for files to watch and compare |
envsync-le.excludePatterns | [] | Glob patterns to exclude; patterns without / match the basename (so .env.*.local excludes nested files too) |
envsync-le.notificationLevel | important | all = missing + extra keys, important = missing keys + errors, silent = nothing |
envsync-le.statusBar.enabled | true | Show the status bar item (applies immediately) |
envsync-le.debounceMs | 1000 | Delay between a file change and the sync check |
envsync-le.caseSensitive | true | Treat DB_URL and db_url as different keys |
envsync-le.comparisonMode | auto | auto, manual, or template |
envsync-le.compareOnlyFiles | [] | In manual mode, only compare these files (workspace-relative) |
envsync-le.templateFile | — | The reference file for template mode (set via Set Template) |
envsync-le.temporaryIgnore | [] | Files currently ignored (managed by the ignore commands) |
envsync-le.telemetryEnabled | false | Local-only event log (see Privacy) |
A-Za-z_*, so dotted names such as spring.datasource.url count; anything else left of = is reported as a parse error for that line (the rest of the file still counts).export KEY=value is accepted; duplicate keys count once.", ', or ` may span multiple lines; an unterminated quote is reported as an error.auto mode the reference is the union of all keys, so "extra keys" only exist in template mode.Twelve languages besides English:
German · Spanish · French · Indonesian · Italian · Japanese · Korean · Portuguese (Brazil) · Russian · Ukrainian · Vietnamese · Chinese (Simplified)
Both halves are covered — the manifest (command titles, setting names and descriptions) and everything shown while the extension runs (notifications, the status bar, quick-picks and prompts, and the headings of the report). The help page is written in English. The extension follows VS Code's display language, so it matches whatever the editor is already set to; no setting of its own.
telemetryEnabled setting only writes events to a local Output Channel you can inspect (envsync-le).