Repository navigation
feat(cli): add MCP Registry and Glama listing metadata - #724
Merged
Merged
Conversation
- packages/cli/server.json declares LoreKit for the official MCP Registry as io.github.mthines/lorekit: the local stdio server (npx @lorekit/cli mcp, LOREKIT_MODE=local by default) and the hosted endpoint (Bearer token). - mcpName in @lorekit/cli's package.json, which the registry checks against the published npm package before it accepts server.json. - release-please bumps both versions in server.json with the CLI, so they cannot drift from the npm version. - glama.json at the root claims the Glama listing for mthines. Claude-Session: https://claude.ai/code/session_01NH7TGCuRSockwnax7B649s
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
LoreKit isn't listed in the official MCP Registry or on Glama. The registry needs a
server.jsonand a matchingmcpNamein the published npm package, and Glama's ownership claim needs aglama.json. PulseMCP has paused its own submissions and pulls new servers from the registry.What changed
packages/cli/server.jsonregistersio.github.mthines/lorekitwith two entries: the local stdio server (npx @lorekit/cli mcp,LOREKIT_MODE=localby default) and the hosted endpoint (Bearer token). It passes the registry's2025-12-11schema.mcpNamein@lorekit/cli'spackage.json; the registry checks for it in the published package.server.jsonwith the CLI, so they can't drift from npm.glama.jsonat the repo root listsmthinesas maintainer.After merge
The
featcommit triggers a CLI release that includesmcpName. Then, frompackages/cli, runmcp-publisher login githubandmcp-publisher publish(manually, or later as a step inrelease.ymlvia OIDC).No user-facing docs or
llms.txtchanges: this is listing metadata with no change in behaviour.https://claude.ai/code/session_01NH7TGCuRSockwnax7B649s
Generated by Claude Code