chore: update Glama MCP metadata#655
Merged
Merged
Conversation
|
Size Report
Startup median (7 runs, lower is better):
Top changed chunks:
|
thymikee
force-pushed
the
chore/glama-mcp-metadata
branch
2 times, most recently
from
321de46 to
d9a4845
Compare
thymikee
force-pushed
the
chore/glama-mcp-metadata
branch
from
d9a4845 to
7bfb673
Compare
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.
Summary
Update Glama-facing MCP metadata so the organization-owned server can be claimed and evaluated, including
glama.json, a Glama README badge, and docs metadata alignment.Touched files: 3. Scope stayed within MCP/registry metadata and docs.
Validation
Verified metadata sync with
pnpm check:mcp-metadata. Earlier on this branch, also verifiedpnpm build, JSON metadata parsing, and a built stdio MCPtools/listsmoke request before the later scope trims.