Skip to content

Conversation

tonidy
Copy link

@tonidy tonidy commented Jul 9, 2025

Hi @griffithsbs,

This PR includes:

  • Introduced the --env-stdin option to read environment variables directly from stdin.
  • Updated usage instructions to reflect the new option and clarify mutual exclusivity with --env-file.
  • Added error handling for multiple --env-stdin specifications and conflicts with --env-file.
  • Implemented tests to verify the new functionality and error conditions.

I need to add this parameter --env-stdin, so I can pipe it with another command.

{
  "mcpServers": {
    "mcp1": {
      "command": "sh",
      "args": [
        "-c",
        "pa show mcp/n8n/env | npx -y envmcp --env-stdin node /Users/t/mcp/dist/mcp/index.js"
      ]
    }
  }
}

Any feedback?

tonidy added 5 commits July 9, 2025 11:14
- Introduced the --env-stdin option to read environment variables directly from stdin.
- Updated usage instructions to reflect the new option and clarify mutual exclusivity with --env-file.
- Added error handling for multiple --env-stdin specifications and conflicts with --env-file.
- Implemented tests to verify the new functionality and error conditions.
@tonidy tonidy force-pushed the read-env-from-stdin branch from 98317c1 to 7656aa9 Compare July 9, 2025 04:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant