8000 Add MCP Registry server.json, mcpName, and Glama glama.json for catalog listings by dominion525 · Pull Request #12 · dominion525/familiar · GitHub
[go: up one dir, main page]

Skip to content

Add MCP Registry server.json, mcpName, and Glama glama.json for catalog listings - #12

Merged
dominion525 merged 1 commit into
mainfrom
feat/registry-manifests
Jun 22, 2026
Merged

dominion525 merged 1 commit into
mainfrom
feat/registry-manifests

Conversation

@dominion525
Copy link
Copy Markdown
Owner

Summary

Add the repo-level files required by the official MCP Registry and Glama so the package can be listed in their catalogs.

Files

  • mcp/server.json — MCP Registry spec manifest, namespace io.github.dominion525/familiar-mcp, points at the npm package @dominion525/familiar-mcp with stdio transport.
  • mcp/package.json — adds mcpName: "io.github.dominion525/familiar-mcp" so the MCP Registry can verify ownership against the matching name in server.json (registry checks the npm package for this field).
  • glama.json (repo root) — declares maintainers: ["dominion525"]. Glama auto-discovers public MCP repos; this file claims the listing under the actual maintainer so any future metadata overrides are attributable.

Out of scope

  • MCP Scoreboard: web-form submission, no repo-level file needed.
  • Smithery: uses the .mcpb already attached to the v0.1.0 GitHub Release, no additional repo-level file needed.
  • MCP Registry auto-publish workflow (publish-mcp.yml): deferred. Initial registry publish will be done manually with mcp-publisher publish.

…alog listings

- Add mcp/server.json (MCP Registry spec) declaring the npm package @dominion525/familiar-mcp as a stdio MCP server under the namespace io.github.dominion525/familiar-mcp
- Add mcpName field to mcp/package.json so the MCP Registry can verify ownership of the npm package against the server.json name (both set to io.github.dominion525/familiar-mcp)
- Add glama.json at repo root with the maintainers field so Glama can attribute the auto-discovered repo to dominion525
- MCP Scoreboard and Smithery do not require repository-level files: Scoreboard uses a web submit form, Smithery uses the existing .mcpb already attached to the v0.1.0 GitHub Release
- The MCP Registry publish itself remains manual for now (mcp-publisher CLI); a publish-mcp.yml workflow can be added later as a follow-up

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@dominion525
dominion525 merged commit f287857 into main Jun 22, 2026
3 checks passed
@dominion525
dominion525 deleted the feat/registry-manifests branch June 22, 2026 15:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0