stacklok / stacklok/toolhive-studio
[Task] we should always show env var and secrets field in mcp form
Open
Nobody has claimed this yet.
Task
- Dominant language
- TypeScript
- Stars
- 167
- Forks
- 24
- Avg merge
- 11h 32m
- Merged PRs (30d)
- 91
Description
Description
Currently we show the env vars and secrets fields based on configuration, we should allow the users to always add env vars. This will be useful as soon as the user will pull from upstream registry, where it will be possible to not have env vars configuration out of the box
Acceptance Criteria
No response
Priority
Medium
Task Type
Feature
Additional Context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the MCP form and the logic that conditionally displays its env vars and secrets fields. Confirm the fields remain available when no configuration is supplied, including for servers pulled from an upstream registry, and verify that users can add values in that case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100