Add a reproducible Glama MCP build - #100
Open
AjnasNB wants to merge 1 commit into
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changed
glama.jsonmaintainer declarationnode bin/qarinah.js mcpWhy
Glama continuously builds and introspects open-source MCP servers. Qarinah already publishes valid MCP Registry metadata and a tested stdio transport, but the repository did not contain a reproducible container entry point for Glama's sandbox.
Impact
The container exposes Qarinah's default diagnostic-only MCP surface. It does not enable
context.query, initialize a workspace, write state, or grant disclosure authority.Validation
npm run checknpm prune --omit=dev --ignore-scripts && npm run mcp:smokeglama.jsonvalidated againsthttps://glama.ai/mcp/schemas/server.jsonThe local Docker daemon was unavailable, so no local image build is claimed.
Branch migration
This PR replaces #96 only because its legacy head ref used the retired �gent/ prefix. The source tree and commit history are unchanged:$(System.Collections.Hashtable.oldBranch) and $ (System.Collections.Hashtable.newBranch) both point to exact head $(System.Collections.Hashtable.sha) at migration time. Review and merge protection remain required.