envmcp

Created By
griffithsbsa 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 manage environment variables in Cursor MCP server definitions, allowing for secure handling of sensitive information.

How to use envmcp?

To use envmcp, create a .env.mcp file in your home directory to store your secrets, then prefix your stdio command with npx envmcp to reference the environment variables in your MCP configuration.

Key features of envmcp?

  • Simplifies the management of environment variables for MCP servers.
  • Allows for secure storage of sensitive information in a dedicated file.
  • Automatically loads environment variables from the nearest .env.mcp file.

Use cases of envmcp?

  1. Managing database connection strings securely.
  2. Running MCP servers with sensitive API keys without hardcoding them.
  3. Simplifying the configuration of multiple MCP servers with shared environment variables.

FAQ from envmcp?

  • How do I install envmcp?

You can install envmcp globally using npm with the command npm install -g envmcp.

  • What format should the .env.mcp file follow?

The .env.mcp file should follow the standard environment file format, with key-value pairs for each environment variable.

  • Can envmcp be used with any command?

Yes, envmcp can be used to run any command that requires environment variables.

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

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago