🌍 envmcp: Simplifying Environment Variables for Cursor MCP Servers

Created By
dfhgnh43terga year ago
A lightweight way to use environment variables in your Cursor MCP server definitions.
Overview

What is envmcp?

envmcp is a lightweight tool designed to simplify the management of environment variables in Cursor MCP server definitions, making it easier to handle configuration settings, credentials, and secrets.

How to use envmcp?

To use envmcp, download the latest release from the Releases page, create a configuration file with your environment variables, and load it in your MCP server definition using the command load_env('env.config').

Key features of envmcp?

  • Lightweight with minimal overhead for quick setup.
  • Easy configuration with simple syntax for defining environment variables.
  • Secure secret management to keep credentials safe.
  • Seamless integration with Cursor MCP servers.
  • Support for multiple environments (development, testing, production).

Use cases of envmcp?

  1. Managing environment variables for web applications.
  2. Keeping sensitive information secure in server configurations.
  3. Switching between different configurations for various environments easily.

FAQ from envmcp?

  • Is envmcp easy to set up?

Yes! envmcp is designed for quick and easy installation with minimal configuration required.

  • Can I use envmcp for multiple projects?

Absolutely! You can manage different environment configurations for multiple projects using envmcp.

  • Is envmcp open source?

Yes! envmcp is open source and available on GitHub under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dfhgnh43terg
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago