feat: add start arg to launchdarkly spec #225
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Dan Barr <6922515+danbarr@users.noreply.github.com>
danbarr
commented
Dec 1, 2025
Contributor
Author
danbarr
left a comment
danbarr
left a comment
There was a problem hiding this comment.
Opened as a draft because we need to wait until the next thv release picks up the updated registry, else current installs will duplicate the "start" arg.
🔒 MCP Security Scan Results✅ launchdarkly-mcp-server
Summary: Scanned 1 MCP server(s), all passed security checks. ✅ |
ChrisJBurns
approved these changes
Dec 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Moving the "start" arg from runtime to build-time.
Ref stacklok/toolhive-registry#452
Signed-off-by: Dan Barr 6922515+danbarr@users.noreply.github.com