This guide provides instructions for publishing the n8n Workflow Builder MCP Server package to npm.
Before publishing, make sure you have:
- An npm account (in this case, the package will be published under the
@kernel.salacostescope) - Proper access rights to publish to this scope
- A properly configured package.json file
- All changes committed to git
npm loginFollow the prompts to authenticate with your npm credentials. You may need to provide a one-time password if you have 2FA enabled.
To update the package version:
# For patch updates (bug fixes)
npm version patch
# For minor updates (new features, backward compatible)
npm version minor
# For major updates (breaking changes)
npm version majorThis will update the version in package.json and create a git tag.
The package will be automatically built during publishing due to the prepublishOnly script, but you can also build it manually:
npm run clean && npm run buildnpm publish --access publicOr use the npm script:
npm run publishAfter publishing, verify that the package is available on npm:
https://www.npmjs.com/package/@kernel.salacoste/n8n-workflow-builder
If you have issues logging in:
npm login --registry=https://registry.npmjs.org/Common errors include:
- Version already exists: Update the version in package.json
- Permission denied: Ensure you have the right access level to publish
- Package name conflicts: Check that the package name is available and you have rights to publish to that scope
To update the package in the future:
- Make your code changes
- Update the version using
npm version - Build and publish as described above