
Security News
The Hidden Blast Radius of the Axios Compromise
The Axios compromise shows how time-dependent dependency resolution makes exposure harder to detect and contain.
@kdbx/envmcp
Advanced tools
A lightweight way to use environment variables in your Cursor MCP server definitions.
Use environment variables in your Cursor MCP server definitions.
💡 Looking for more features? Consider mcpipe (npm) which includes envmcp's functionality as well as debugging tools and other capabilities.
# Use default ~/.env.mcp file
npx envmcp your-mcp-server $DATABASE_URL
# Specify custom env file
npx envmcp --env-file .env your-mcp-server $API_KEY $DATABASE_URL
# Short flag version
npx envmcp -e /path/to/secrets.env your-mcp-server $MY_SECRET
Prefix your server command with envmcp.
Before (secrets exposed in config):
{
"my_database": {
"command": "my-mcp-server",
"args": ["postgresql://user:password@hostname/db"]
}
}
After (secrets in ~/.env.mcp):
{
"my_database": {
"command": "npx",
"args": ["envmcp", "my-mcp-server", "$DATABASE_URL"]
}
}
.env.mcp in current directory, then parent directories, finally ~/.env.mcp--env-file is specified, uses that file instead$VARIABLE_NAME references in your command argumentsnpm install -g envmcp
--env-file <path>, -e <path>: Specify custom environment file pathDATABASE_URL=postgresql://user:password@localhost/db
API_KEY=your-secret-api-key
# This is a comment
QUOTED_VALUE="value with spaces"
See sample.env.mcp for more examples.
MIT
FAQs
A lightweight way to use environment variables in your Cursor MCP server definitions.
We found that @kdbx/envmcp demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
The Axios compromise shows how time-dependent dependency resolution makes exposure harder to detect and contain.

Research
A supply chain attack on Axios introduced a malicious dependency, plain-crypto-js@4.2.1, published minutes earlier and absent from the project’s GitHub releases.

Research
Malicious versions of the Telnyx Python SDK on PyPI delivered credential-stealing malware via a multi-stage supply chain attack.