This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
mcp-secrets-runner
Keep live API keys out of your .mcp.json
Starts MCP servers with secrets pulled from Infisical, 1Password or HashiCorp Vault. Yourmcp.json holds references instead of keys, and machine credentials mean no CLI login that expires and takes every server down at once. Zero deps, MIT.
I run fifteen MCP servers in Claude Code and most of them need an API key. Every setup guide tells you to paste it into the env block of .mcp.json. For Stripe that means a live key in a file I sync between machines.
Wrapping each server in `infisical run` fixed that, right up until the CLI login expired. Then every server failed to start at the same moment, and the error pointed at the MCP client, not at the login.
mcp-secrets-runner sits between the client and the server. It authenticates with credentials built for unattended use (Infisical machine identity, 1Password service account, Vault AppRole), fetches the secrets and execs the real server. There's a `doctor` command too, because "my MCP server won't start" is almost always one of four things and the client reports all four the same way.
A few details, each there because the alternative broke something for me: diagnostics go only to stderr, since one stray byte on stdout corrupts JSON-RPC. It fails closed instead of falling back to a browser login that hangs the server forever. Tokens are cached, so ten servers starting at once don't do ten logins.
AWS Secrets Manager and Doppler would both fit as providers. PRs welcome.
GitHub: https://github.com/wiktormalyska...
npm: https://www.npmjs.com/package/mc...
About mcp-secrets-runner on Product Hunt
“Keep live API keys out of your .mcp.json”
mcp-secrets-runner was submitted on Product Hunt and earned 2 upvotes and 1 comments, placing #154 on the daily leaderboard. Starts MCP servers with secrets pulled from Infisical, 1Password or HashiCorp Vault. Yourmcp.json holds references instead of keys, and machine credentials mean no CLI login that expires and takes every server down at once. Zero deps, MIT.
On the analytics side, mcp-secrets-runner competes within Developer Tools, Artificial Intelligence and Security — topics that collectively have 1M followers on Product Hunt. The dashboard above tracks how mcp-secrets-runner performed against the three products that launched closest to it on the same day.
Who hunted mcp-secrets-runner?
mcp-secrets-runner was hunted by Wiktor Małyska. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of mcp-secrets-runner including community comment highlights and product details, visit the product overview.
Wiktor Małyska