mcp: rename package to instanode-mcp (unscoped) to unblock npm publish#2
Merged
Conversation
The publish workflow has been 404-ing on every release because the @instanode npm org was never registered. npm rejects PUTs to a scope that doesn't exist with HTTP 404, regardless of NPM_TOKEN validity. Two options were on the table: A. Switch to an unscoped name (this PR) B. Keep the scope and have the operator run `npm org create instanode` (paid org, or claim it via npm support if available) Chose A. Unscoped removes the org-setup blocker entirely, and there's no product reason to keep the scope — agents install via `npx -y instanode-mcp@latest` rather than discovering the package by scope. The MCP registry's `name` field stays as `io.github.InstaNode-dev/mcp` (org namespace there is GitHub, not npm) so the registry listing is unaffected. Changes: - package.json: name → "instanode-mcp" - server.json: npm identifier → "instanode-mcp", version → 0.8.0 - README.md: every install command + heading - PUBLISHING.md: heading, npm view command, post-publish verification; added a top-of-file note explaining the rename for posterity - smithery.yaml: command args - src/index.ts: file header comment - test.sh: shell echoes Test gate: npm run build — clean npm test — 6/6 pass (still resolves serverInfo, tools/list, list_resources auth message, validation, claim helper) After merge, the next push to master triggers the publish workflow. Operator verification: npm view instanode-mcp version # should print 0.8.0 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
The publish workflow has been 404-ing on every release with
npm error 404 Not Found - PUT https://registry.npmjs.org/@instanode%2fmcpbecause the
@instanodenpm org was never registered. npm rejects PUTs to a non-existent scope regardless of NPM_TOKEN validity.Two options were on the table:
npm org create instanode(paid org, or claim it via npm support)Chose A. Unscoped removes the org-setup blocker entirely, and there's no product reason to keep the scope — agents install via
npx -y instanode-mcp@latestrather than discovering the package by scope. The MCP registry'snamefield stays asio.github.InstaNode-dev/mcp(the namespace there is GitHub, not npm) so the registry listing is unaffected.Changes
package.json: name →"instanode-mcp"server.json: npm identifier →"instanode-mcp", version → 0.8.0README.md: every install command + heading updatedPUBLISHING.md: heading,npm viewcommand, post-publish verification; added a top-of-file note explaining the rename for posteritysmithery.yaml: command argssrc/index.ts: file header commenttest.sh: shell echoesTest plan
npm run build— cleannpm test— 6/6 pass (still resolves serverInfo, tools/list, list_resources auth message, validation, claim helper)npm view instanode-mcp versionto confirm0.8.0.npx -y instanode-mcp@latest --versionresolves from a fresh machine.Downstream callers (out of scope for this PR)
The following repos still reference
@instanode/mcpin their READMEs / launch content and should be migrated when next touched (not blocking this fix):/sdk-python/README.md,/llama-index-instanode/README.md,/langchain-instanode/README.md,/crewai-instanode-tools/README.md/instant-lite-web/content articles/gtm-ops/playbooks and changelog/launch-content/postspackage.jsondependency on@instanode/mcp🤖 Generated with Claude Code