Env MCP Server

Env MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server that scans your project for secret exposure risks — leaked API keys, unprotected .env files, secrets in logs — before your AI agent accidentally exfiltrates them.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What the assistant can call

Once Env is connected, these are the calls the assistant has available:

• scan_for_secrets — Scans source files, config files, and .env files for 20+ secret patterns. Returns file path, line number, severity, and a masked preview — never the
• check_gitignore_coverage — Checks whether sensitive files (.env, .env.local, secrets.json, private keys, certificates) are covered by .gitignore. Flags files that could be
• scan_for_log_leaks — Scans source files for console.log / logger calls that print process.env variables or objects with secret-sounding names at runtime. Catches the most

Configuration and credentials

You will need one environment variable: AWS_SECRET_ACCESS_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the env mcp server does with a few real requests.

Choosing this one

Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Env's toolset — scan_for_secrets, check_gitignore_coverage, scan_for_log_leaks — is a fair guide to whether it matches your workflow. It is maintained by vola-trebla; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.