|
|
|
|
|
|
by aghilmort
170 days ago
|
|
|
interesting! been exploring any/all of assume we ship mcp server where there is free & premium version (or could be skill, plugin, etc.). can we adapt or package this with? &/or what instructions would our users need to do to add api key for premium if point to your mcp? Etc if doesn’t make sense lmk can sketch more precisely etc |
|
|
Short answer: yes, secretctl can help manage API keys for your premium tier.
It's a single binary with no dependencies (Apache 2.0 license), so you could: - Bundle it with your distribution - Point users to Homebrew: brew install forest6511/tap/secretctl - Or link to our binary downloads
For your premium API key scenario, here's how users would set it up:
1. Store the key: secretctl set your-service --field api_key=sk-xxx
2. Use secret_run or secret_run_with_bindings to inject it into commands. The AI agent never sees the actual secret - it's injected at runtime.
Currently free and open source. We're considering team/enterprise features down the road.
Happy to discuss integration patterns in more detail if useful!