env-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@env-mcp get the database host variable"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
š env-mcp - Environment Variable MCP Server
A Model Context Protocol (MCP) server for secure environment variable and configuration management with Claude Code integration
Features
Secure Storage: Store environment variables with optional sensitive data protection
Categories: Organize variables by category for better management
Search & Filter: Find variables quickly with search functionality
Multiple Formats: Export/import support for .env, JSON, and YAML formats
MCP Integration: Seamlessly integrates with Claude Code for AI-assisted configuration management
CLI Tool: Powerful command-line interface for manual management
Related MCP server: empaya-mcp-server
Installation
# Clone the repository
git clone https://github.com/buildappolis/env-mcp.git
cd env-mcp
# Install dependencies
pnpm install
# Build the project
pnpm run buildConfiguration
Add to Claude Code
The server is already configured with Claude Code. To verify:
claude mcp listYou should see:
env-mcp: node /home/cory-ubuntu/coding/env-mcp/dist/index.js - ā ConnectedManual Configuration
If you need to reconfigure:
claude mcp add env-mcp "node" "/path/to/env-mcp/dist/index.js"CLI Usage
Basic Commands
# Set a variable
./env-mcp-cli set KEY "value" --description "Description" --category "category"
# Set a sensitive variable (will be redacted in output)
./env-mcp-cli set API_KEY "secret" --sensitive --category "secrets"
# Get a variable
./env-mcp-cli get KEY
# List all variables
./env-mcp-cli list
# List by category
./env-mcp-cli list --category "secrets"
# Search variables
./env-mcp-cli search "api"
# Delete a variable
./env-mcp-cli delete KEY
# List categories
./env-mcp-cli categoriesImport/Export
# Export to .env format
./env-mcp-cli export --format env --output .env
# Export to JSON
./env-mcp-cli export --format json --output config.json
# Export to YAML
./env-mcp-cli export --format yaml --output config.yaml
# Import from .env file
./env-mcp-cli import .envMCP Tools (Available in Claude)
When using Claude Code, the following tools are available:
env_get- Get an environment variable valueenv_set- Set an environment variable with optional metadataenv_delete- Delete an environment variableenv_search- Search for variables by queryenv_list- List all variables or filter by categoryenv_export- Export variables in different formatsenv_import- Import variables from a file
Data Storage
Configuration is stored in: ~/.env-mcp/config.yaml
The storage format includes:
Variable key/value pairs
Optional descriptions
Categories for organization
Sensitive data flags
Creation/update timestamps
Examples
Setting up a development environment
# Database configuration
./env-mcp-cli set DB_HOST "localhost" --category "database"
./env-mcp-cli set DB_PORT "5432" --category "database"
./env-mcp-cli set DB_NAME "myapp" --category "database"
./env-mcp-cli set DB_USER "admin" --category "database"
./env-mcp-cli set DB_PASS "secret" --sensitive --category "database"
# API Keys
./env-mcp-cli set OPENAI_API_KEY "sk-..." --sensitive --category "api-keys"
./env-mcp-cli set STRIPE_API_KEY "sk_test_..." --sensitive --category "api-keys"
# Application settings
./env-mcp-cli set NODE_ENV "development" --category "app"
./env-mcp-cli set PORT "3000" --category "app"
./env-mcp-cli set LOG_LEVEL "debug" --category "app"
# Export for use in application
./env-mcp-cli export --format env --output .envSearching and filtering
# Find all database-related variables
./env-mcp-cli search "db"
# List all API keys
./env-mcp-cli list --category "api-keys"
# Show all categories
./env-mcp-cli categoriesJSON output for scripting
# Get JSON output for parsing
./env-mcp-cli list --json | jq '.[] | select(.category == "database")'
# Export specific category to JSON
./env-mcp-cli list --category "app" --json > app-config.jsonSecurity
Variables marked as
--sensitiveare redacted in normal outputUse
--show-sensitiveflag withgetcommand to view sensitive valuesSensitive values are still exported normally (be careful with exports)
Configuration file permissions should be restricted (chmod 600)
Development
Project Structure
env-mcp/
āāā src/
ā āāā index.ts # MCP server implementation
ā āāā cli.ts # CLI tool implementation
ā āāā store.ts # Storage layer
ā āāā types.ts # TypeScript type definitions
āāā dist/ # Compiled JavaScript
āāā package.json # Dependencies and scripts
āāā tsconfig.json # TypeScript configurationScripts
# Build the project
pnpm run build
# Run in development mode
pnpm run dev
# Run CLI in development
pnpm run cliTroubleshooting
MCP Server won't connect
Check if the server is built:
pnpm run buildTest the server manually:
echo '{"jsonrpc":"2.0","method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"1.0.0"}},"id":1}' | node dist/index.jsReconnect with Claude:
claude mcp list # Check status
Variables not persisting
Check the configuration file:
cat ~/.env-mcp/config.yamlEnsure write permissions:
mkdir -p ~/.env-mcp
chmod 755 ~/.env-mcpLicense
MIT
Contributing
Feel free to submit issues and pull requests to improve the env-mcp server.
Available Tools
7 toolsenv_deleteC
Delete an environment variable
Inputs: key (required).
env_exportC
Export environment variables
Inputs: format.
env_getC
Get an environment variable value
Inputs: key (required).
env_importC
Import environment variables from file
Inputs: path (required).
env_listA
List all environment variables or by category
Inputs: category.
env_searchC
Search environment variables
Inputs: query (required).
env_setC
Set an environment variable
Inputs: key (required), value (required), description, category, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogā¦
TDQS
Scored across 7 tools
Each tool has a clear, distinct action (delete, export, get, import, list, search, set) on environment variables, with no overlapping functionality.
All tools follow the consistent pattern 'env_<verb>' using snake_case, making them predictable and easy to distinguish.
With 7 tools covering CRUD, listing, searching, export, and import, the count is well-scoped for environment variable management.
The tool set covers all essential operations (create/set, read/get, update/set, delete/list/search, plus import/export), leaving no obvious gaps for typical workflows.
Maintenance
Related MCP Connectors
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
Augments MCP Server - A comprehensive framework documentation provider for Claude Code
Shared memory and mail for your AI agents. Verified with Claude Code; other MCP clients in testing.
Shared memory MCP server for Claude Code, Codex, Gemini CLI and Cursor. Cited, editable.
Related MCP Servers
- -licenseNot gradedqualityBmaintenanceEnterprise-grade MCP server for persistent, intelligent memory management across Claude Code sessions.-
- AlicenseBqualityDmaintenanceMCP server for Cloudways enabling server management, app deployment, backups, SSL, environment variables, and monitoring via Claude Code.12MIT
- AlicenseNot gradedqualityDmaintenanceSecure MCP server for Boomi Platform API integration with Claude Code. Enables natural language interaction with Boomi Platform APIs, including managing accounts, processes, components, deployments, schedules, and more.1MIT

@lobsterkit/vault-mcpofficial
AlicenseAqualityDmaintenanceMCP server for LobsterVault, enabling AI agents to securely store, retrieve, manage, and share encrypted secrets with KMS envelope encryption, including environment variable injection.1113 npmMIT