Repository navigation
feat(mcp-server): Dockerfile and glama.json for the Glama server listing - #10
Merged
Merged
Conversation
awesome-mcp-servers only lists servers with their own Glama server page (glama.ai/mcp/servers/teakesdev/corpus-agent-kit), and Glama scores a server by starting it in Docker and sending initialize + tools/list. The connector listing for the hosted endpoint does not count. - Dockerfile: two-stage node:22-alpine build of the mcp-server workspace only; the runtime image is the compiled output (no runtime deps), runs as the node user, stdio entrypoint. - glama.json: claims the server for maintainer teakesdev. - CI: docker build, so the image can't silently stop building. Verified locally: the image answers initialize (corpus-legal 1.2.1), tools/list (10 tools) and ping over stdio, with no API key. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Your organization has run out of review credits. Add credits to resume code reviews. |
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
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.
Why
The awesome-mcp-servers listing (punkpeye/awesome-mcp-servers#12672) is blocked. The maintainer (2026-10-23) requires a Glama server listing at
glama.ai/mcp/servers/teakesdev/corpus-agent-kit, claimed by the owner and with a quality score. The existing connector listing for the hosted endpoint doesn't count. Glama scores a server by starting it in Docker and sendinginitialize+tools/list, and this repo had no Dockerfile.What
Dockerfile: a two-stagenode:22-alpinebuild of themcp-serverworkspace only. The runtime image holds just the compiled output, since the server has no runtime dependencies. It runs asnodewith a stdio entrypoint. No API key is needed to start it;CORPUS_API_KEYis optional..dockerignore: keepsnode_modules,dist,.gitand.env*out of the build context.glama.json: claims the server for maintainerteakesdev(schemahttps://glama.ai/mcp/schemas/server.json).docker buildstep so the image can't stop building unnoticed.Verified locally
docker build .succeeds (234 MB image).docker run -i --rmover stdio, with no API key:initialize→corpus-legal1.2.1, protocol2025-06-18tools/list→ 10 tools (law.search,law.get_node,law.list_coverage,account.status,formation.*)ping→{}npm test,npm run typecheck,node scripts/check-plugin-package.mjsandpackage-openai-plugin.py HEADpass.Not independently reviewed.
After merge
teakesdev/corpus-agent-kitat https://glama.ai/mcp/servers and let the score evaluate.🤖 Generated with Claude Code