Skip to content

docs: surface the npm package on the repo page - #1

Open
mintcloud wants to merge 1 commit into
split/mcp-standalonefrom
docs/npm-badges
Open

mintcloud wants to merge 1 commit into
split/mcp-standalonefrom
docs/npm-badges

Conversation

@mintcloud

Copy link
Copy Markdown
Owner

The repo page gave no sign the package is published. GitHub's sidebar Packages box only lists GitHub Packages (ghcr.io / npm.pkg.github.com) — an npmjs.com publish never appears there, so the npm link has to be put on the page by hand.

  • npm version badge → the package page (reads v0.1.0 live)
  • license badge (Apache-2.0, from the manifest)
  • MCP badge → modelcontextprotocol.io
  • one line under Install linking loopclub-mcp on npm

Dropped a downloads badge: shields.io/npm/dm currently renders "package not found or too new" because npm's download stats lag a day. Worth adding once it reports a real number.

Also done directly on the repo (not in this diff):

  • About → Website set to the npm package page (was empty)
  • Topics added: mcp, model-context-protocol, claude, mcp-server, typescript, music, drum-machine, onchain, megaeth, npm-package

🤖 Generated with Claude Code

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