Skip to content

Rename package to @aztec/mcp-server and add CI workflow#2

Open
critesjosh wants to merge 2 commits intomainfrom
ci/publish-and-rename
Open

Rename package to @aztec/mcp-server and add CI workflow#2
critesjosh wants to merge 2 commits intomainfrom
ci/publish-and-rename

Conversation

@critesjosh
Copy link
Collaborator

Summary

  • Rename npm package from aztec-mcp-server to @aztec/mcp-server
  • Update repository URL to aztecprotocol/mcp-server
  • Add publishConfig.access: "public" for scoped package
  • Add GitHub Actions CI workflow that runs tests on PRs and auto-publishes to npm when a version bump is merged to main

Setup required

  • Add an NPM_TOKEN secret in repo Settings → Secrets → Actions (npm granular access token scoped to @aztec/mcp-server)
  • After merging, consider deprecating the old aztec-mcp-server package with npm deprecate aztec-mcp-server "Moved to @aztec/mcp-server"

Test plan

  • Verify CI workflow runs tests on this PR
  • After merging, verify publish job triggers on next version bump

🤖 Generated with Claude Code

- Rename npm package from aztec-mcp-server to @aztec/mcp-server
- Update repository URL to aztecprotocol/mcp-server
- Add publishConfig for public scoped package access
- Add GitHub Actions CI workflow with test and release jobs
- Add semantic-release for automatic versioning and npm publishing
- Add commitlint to enforce conventional commit messages on PRs

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@critesjosh critesjosh force-pushed the ci/publish-and-rename branch from 8910695 to 2473b66 Compare February 26, 2026 21:42
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