Skip to main content
Glama
609,379 tools. Updated 2026-09-25 11:19

".ENV" matching MCP tools:

  • Scan the config/ folder for .env files and identify available configuration files to use with RESTForge runtime. Helps confirm which config to pass when generating launch scripts.
    MIT
  • Upload .env file variables to the linked secret, replacing its current value. Confirm variable names with the user before pushing.
    MIT
    Destructive
  • Store an encrypted secret in the team vault under a specified environment and key, enabling reference in deploys via vault://env/key. Each write creates a new version.
    MIT
  • Adds a new secret to a vault from a local .env file or a single key/value pair. Using the .env file is preferred so secret values are not exposed in conversation.
    MIT

Matching MCP Servers

Matching MCP Connectors

  • Export an environment's variables as .env or JSON with secret values always masked. Produce output suitable for review or re-import into another environment.
    MIT
  • Remove the .oneguard link file from a project directory to stop environment syncing while preserving the .env file. Reset the link without altering secrets.
    MIT
  • Reveals deployment details, commit, missing env vars (names only), and drift between manifest and provider for a deployed project.
    Apache 2.0
  • Creates a registered application's PostgreSQL database and role, generates its password on the host, and writes PostgreSQL and Valkey settings to shared/.env from a matching plan.
    MIT
  • Scan git diff for new routes, webhooks, middleware, or env changes missing Pinned guards to prevent bugs or leaks.
    Apache 2.0
  • Atomically bind an existing .env secret to multiple OpenServerless endpoints, making it available as ctx.<SECRET>. Removes the need to configure the same secret separately for each endpoint.
    Apache 2.0
  • Retrieve the step-by-step onboarding flow to turn a restaurant repository into a live Crave-powered app: log in, create organization, connect .env, import menu, and run.
    MIT
  • List all environment variable keys from .env and .env.example files, redacting their values.
    MIT
  • Check if a project directory is linked to a OneGuard secret, identify which secret, and list the variable names its .env file contains without exposing values.
    MIT
  • Writes the API origin and location ID into an Expo/React Native .env file, enabling storefronts to connect directly without an API key.
    MIT
  • Validate .env files against envalid schemas to catch missing variables, type mismatches, and range errors before app startup or during CI.
    MIT