Publish GitContribute as a discoverable MCP server in the MCP Registry

[morluto]

Current limitation

GitContribute exposes an MCP server through its npm distribution, but the repository does not currently publish MCP Registry metadata or an automated registry release path. Users therefore cannot discover the server through the official MCP Registry and may need to configure it manually.

Desired outcome

Publish GitContribute under the registry name io.github.morluto/gitcontribute, with:

• an mcpName ownership marker in the npm package;
• a checked-in server.json describing the npm package, npx runtime, stdio transport, and version;
• package and registry metadata kept at the same release version;
• a trusted release-tag workflow using mcp-publisher and GitHub OIDC;
• documentation for installing, launching, and configuring the published MCP server.

The registry entry should point at the existing npm artifact rather than introduce a second distribution path.

[morluto]

Jacobian now has a working release pattern that this issue can follow:

• keep server.json at the release tag with matching top-level and package versions;
• add mcpName: io.github.morluto/gitcontribute to the published npm package;
• add a publish-mcp job after npm publication;
• install a pinned mcp-publisher release, run mcp-publisher validate, authenticate with mcp-publisher login github-oidc, and publish;
• grant only contents: read and id-token: write; no interactive login or long-lived registry token is needed.

The registry name should remain io.github.morluto/gitcontribute; the display title can be “GitContribute”. See Jacobian’s implementation in .github/workflows/release.yml and the MCP Registry GitHub Actions guide.