chore: add glama.json for Glama claim verification#11
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Adds
glama.jsonto repo root so the org-owned server page on Glama (glama.ai/mcp/servers/intent-driven-software/idf-mcp) can be claimed via GitHub OAuth.Why
Per Glama's claim flow for org-owned servers, the manifest must live at repo root with a
maintainersarray listing GitHub usernames allowed to claim. Once onmain, "Login with GitHub to claim" verifies ownership against this file and unlocks:The release flow is the prerequisite for the Glama-score badge that punkpeye/awesome-mcp-servers maintainer requested in PR #5960 (review comment today).
Changes
glama.json(6 lines, JSON manifest with$schema+maintainers: ["DubovskiyIM"])No code, no behavioural changes.