Repository navigation
chore: add glama.json so the MCP server can be claimed on Glama - #27
Merged
Merged
Conversation
Glama claims a server in a GitHub organisation only through a glama.json at the repository root that names its maintainers. This one names leemour. No code changes; the npm package's files list leaves it out. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
Glama (glama.ai) lists MCP servers. A server in a GitHub organisation can be claimed only through a
glama.jsonatthe repository root that names its maintainers (what is glama.json).
This file names
leemour, so the owner can claim the server.What
glama.jsonat the root.fileslist does not include it, so the published package is unchanged.🤖 Generated with Claude Code