Environment Variable Usage Auditor

Environment Variable Usage Auditor MCP Connector for Claude

A+

Cross-references environment variable usage against declaration files to find missing or unused keys.

3 tools Official Updated Oct 1, 2026 Official Vinkius Partner

The Environment Variable Usage Auditor prevents production crashes by ensuring your application code and configuration files are in sync. It identifies 'Ghost Variables' (used in code but missing from .env) and 'Dead Configuration' (declared in .cdotenv but never used). By using extract_keys to scan .env, docker-compose.yml, or Kubernetes ConfigMaps, and extract_used_keys to analyze your source code, you can then run audit_consistency to generate a complete parity report.

envdotenvauditkubernetesdocker

3 tools expose this connector's capabilities to your AI agent.

audit_consistency

env) against a list of used keys (from code). Audits consistency between declared and used environment variables

extract_keys

Extracts keys from file contents (e.t. .env, docker-compose)

extract_used_keys

g., .js, .ts, .py). Extracts used environment variable keys from code contents

See how to talk to your AI agent using Environment Variable Usage Auditor.

Check if my environment variables are consistent for this project.

The audit is complete. The `isConsistent` status is true, meaning all declared keys match the used keys with no discrepancies found.

I have a list of keys from my .env file and a list from my code. Can you audit them?

Yes, please provide the JSON arrays for both sets of keys, and I will use `audit_consistency` to identify any mismatches.

Extract all variable names from this .env content: 'PORT=3000 DB_URL=postgres://localhost'

The extracted keys are: `PORT`, `DB_URL`.

It scans files like `.env`, `.env.example`, `docker-compose.yml`, and Kubernetes ConfigMaps using the `extract_keys` tool.

Related Connectors