feat: Set up npm publishing for the OTF MCP server - #179
Open
thekidnamedkd wants to merge 1 commit into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
thekidnamedkd
changed the title
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
1 participant
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.
Sets up automated npm publishing for the read-only MCP server (
mcp/, packageotf-mcp-server) and rewrites its docs to be public-facing, so the one-pastenpx -y otf-mcp-serverinstall actually resolves once DevOps provisions a token.Why
claude mcp add … npx -y otf-mcp-servercurrently registers but fails to launch — the package is not on npm. This makes the zero-install path real.Changes
.github/workflows/publish-mcp.yml— publishes on amcp-v<version>tag (or manual dispatch, dry-run by default). Runsnpm ci→ build → the 23 tests, verifies the tag equalspackage.jsonversion, thennpm publishwith provenance via GitHub OIDC (id-token: write). Actions SHA-pinned to matchci.yml.mcp/package.json— addsrepository/homepage/bugs/keywordsandpublishConfig(access: public,provenance: true). Dry-run pack is clean: 5 files (dist + README).mcp/README.md— rewritten public-facing: leads with the zero-installnpxquick start (OTF_API_BASE=https://otf.aragon.org) for Claude / Cursor / Codex; source-build moved to a contributors section.mcp/PUBLISHING.md— DevOps handoff + release runbook.DevOps handoff (the one remaining gate)
The workflow needs exactly one secret:
NPM_TOKEN(an npm Automation token for an account/org that owns theotf-mcp-servername — currently unclaimed on npm). Provenance uses OIDC, so no other credential is required. Full steps inmcp/PUBLISHING.md.Release, once the token is set
Bump
mcp/package.json, thengit tag mcp-v0.1.0 && git push origin mcp-v0.1.0— or Actions → Publish MCP → Run workflow.Verification
npm publish --dry-run→ 5 files, dist + README only.node --test test/*.test.mjs→ 23/23 pass.