Onboarding request: io.github.bruchris/canvas-lms-mcp for github.com/mcp

[bruchris]

Onboarding request: io.github.bruchris/canvas-lms-mcp for github.com/mcp

• Official registry name: io.github.bruchris/canvas-lms-mcp
• Latest version: 1.25.0
• Repository: https://github.com/bruchris/canvas-lms-mcp
• License: MIT
• Description: TypeScript MCP server for Canvas LMS — 163 tools across 41 domains (courses, assignments, grades, gradebook history, quizzes, New Quizzes/LTI, outcomes, discussions, admin workflows, and more).

The server is already published on the official MCP registry (npm-verified package, GitHub OIDC namespace auth) and has been kept in sync with every release since. Following the pattern in #1257 and #2844, opening this as a Q&A request since I understand initial onboarding to github.com/mcp is still manual curation on your end — happy to provide anything else needed (repo topics, README format, etc.).

Thanks for maintaining the registry!

[stefisha]

The registry entry looks generally complete, but I noticed that the repository's current server.json still declares version 1.15.1 for both the server and npm package, while this request lists 1.25.0.

There is also a small metadata mismatch:

• Request: 163 tools across 41 domains
• Current README/server description: 165 tools across 42 domains

I would update server.json so its version, package version, and description match the latest release, then validate and republish:

mcp-publisher validate server.json

Even if the official Registry already contains 1.25.0, keeping the source repository metadata aligned may help GitHub's manual review or ingestion process. After that, inclusion on github.com/mcp still appears to depend on GitHub's curation or synchronization process.

Once it appears on github.com/mcp, you can mark this discussion as complete.