Add MCP-server Dockerfile (stdio) for Glama introspection#1
Merged
Conversation
The existing docker/Dockerfile builds the `grasp` CLI (ENTRYPOINT grasp --help), which cannot answer the MCP handshake — so Glama reports the server as 'cannot be installed'. This adds a root Dockerfile that starts the MCP server on stdio (dist/index.js, the grasp-mcp bin / npm start), mirroring the proven build stage so it stays in lock-step with the published grasp-mcp-server package. Runs with no config (public repos, 60 req/hr); GITHUB_TOKEN raises limits.
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
Adds a root
Dockerfilethat runs the MCP server on stdio (dist/index.js— thegrasp-mcpbin /npm start).Why
docker/Dockerfilebuilds thegraspCLI (ENTRYPOINT ["grasp"],CMD ["--help"]), which can't answer the MCP handshake (initialize/tools/list). Glama therefore reports the server as "cannot be installed", which blocks the awesome-mcp-servers listing (PR punkpeye/awesome-mcp-servers#8191) and keeps the Glama quality/security checks from completing.How
docker/Dockerfile(samenpm ci --legacy-peer-deps --ignore-scripts+npm run build), so it stays in lock-step with the publishedgrasp-mcp-server.node dist/index.js), not the CLI.GITHUB_TOKENraises limits — matchingsmithery.yaml.Note on the Glama "license not found"
The package already declares
"license": "Elastic-2.0"(a valid SPDX id) inmcp/package.json, and the LICENSE + image labels are consistent. GitHub's detector reportsNOASSERTIONbecause Elastic-2.0 is source-available, not OSI-approved — so this is inherent to the license choice, not a metadata bug. The awesome-mcp-servers maintainer has stated the license grade is not required for merge; a fresh Glama re-evaluation should at minimum resolve the license toElastic-2.0rather than "not found".