Rename project to vaultpilot-mcp - #26
Merged
Merged
Conversation
Renames the npm package (`recon-crypto-mcp` → `vaultpilot-mcp`), the mcpName identifier, server metadata, CLI binaries (`*-mcp`, `*-mcp-setup`), and all user-facing copy (README, setup output, error messages, tool descriptions). User config dir `~/.recon-crypto-mcp` → `~/.vaultpilot-mcp` with a back-compat fallback: reads the old path if the new one doesn't exist, and copies the legacy dir to the new location on first write. Existing installs keep their WalletConnect pairing state (walletconnect.db) across the rename. Env vars follow the same pattern: RECON_ALLOW_INSECURE_RPC → VAULTPILOT_ALLOW_INSECURE_RPC RECON_FEEDBACK_ENDPOINT → VAULTPILOT_FEEDBACK_ENDPOINT RECON_FEEDBACK_STATE_FILE → VAULTPILOT_FEEDBACK_STATE_FILE Old names are still honored for one release. External follow-ups (separate steps): - Rename GitHub repo (gh repo rename vaultpilot-mcp) - Publish new npm package + deprecate old one - Re-publish to MCP registry with new mcpName - glama.ai re-indexes off the GitHub repo URL Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
szhygulin
added a commit
that referenced
this pull request
Apr 14, 2026
Marks the `recon-crypto-mcp` → `vaultpilot-mcp` rename (PR #26) as a minor release. The package name, mcpName identifier, and user config dir location all changed, with back-compat fallbacks for the config dir and env vars — worth a minor bump so npm and the MCP registry surface it as a new version rather than a patch. Co-Authored-By: Claude Opus 4.6 <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
/.recon-crypto-mcp` → `/.vaultpilot-mcp` with a back-compat fallback: reads the old path if the new one doesn't exist, and copies the legacy dir to the new location on first write. Existing installs keep their WalletConnect pairing state (walletconnect.db) across the rename.Scope of the diff
Follow-ups (intentionally not in this PR)
After merge:
Test plan
🤖 Generated with Claude Code