Claude MCP技能安装工具

Growth Nirvana Claude MCP + Skills

Install and maintain a ready-to-run MCP server entry and Growth Nirvana skills for Claude Code/editor workflows.

Why this is the best install UX

• Users do not clone repos or edit JSON manually.
• npx always runs the latest installer (or a pinned version).
• Installer updates a project-local .mcp.json safely, preserving other MCP servers.
• Includes Claude-compatible skills in standard skills/<skill>/SKILL.md format.
• Includes a standard Claude plugin manifest at .claude-plugin/plugin.json.
• Works as a repeatable command for onboarding and support.

Setup (First Time Only)

Get Your API Key

Obtain a Growth Nirvana MCP API key from the Growth Nirvana dashboard (Settings → API Keys).

Quick Start

1) Create .env.local with your API key

echo 'GROWTH_NIRVANA_API_KEY=gnmcp_your_key_here' > .env.local
echo '.env.local' >> .gitignore

2) Initialize project MCP config

npx @growthnirvana/claude-mcp-installer init

The installer auto-detects .env.local and configures the MCP server to use it.

This adds an MCP server entry named growth-nirvana to:

• ./.mcp.json (project root)

3) Install skills into your project

npx @growthnirvana/claude-mcp-installer add-skills

This installs skills to:

• ./.claude/skills/

4) Reload your editor

Reload your editor (VS Code/Cursor/Claude Code) so MCP config and skills are re-read.

Claude Plugin Structure

This repo also ships a standard Claude plugin layout:

• .claude-plugin/plugin.json
• skills/<skill-name>/SKILL.md
• supporting files (reference.md, examples.md, etc.)

Commands

npx @growthnirvana/claude-mcp-installer init
npx @growthnirvana/claude-mcp-installer init --force
npx @growthnirvana/claude-mcp-installer init --pin-server-version 1.2.3
npx @growthnirvana/claude-mcp-installer remove
npx @growthnirvana/claude-mcp-installer add-skills
npx @growthnirvana/claude-mcp-installer add-skills --global

Options

• --config <path>: custom config file path
• --server-name <name>: MCP server key (default: growth-nirvana)
• --force: overwrite existing server entry when running init
• --pin-server-version <version>: pin growth-nirvana-mcp-server version
• --global: for add-skills, install to ~/.claude/skills
• --target <path>: for add-skills, install to a custom skills directory

API Key & Security

Automatic .env.local Detection

The installer auto-detects if .env.local exists in your project root:

• If found: Configures the MCP server to source GROWTH_NIRVANA_API_KEY from .env.local (or .env as fallback)
• If not found: Uses environment variables from your editor/shell session

.env.local Method (Recommended for Projects)

Create .env.local in your project root:

echo 'GROWTH_NIRVANA_API_KEY=gnmcp_your_key_here' > .env.local

Add to .gitignore:

echo '.env.local' >> .gitignore

The installer will automatically configure the MCP server to read from this file.

Environment Variable Method (Recommended for Persistence)

Set the API key in your shell profile (.zshrc, .bashrc, etc.):

echo 'export GROWTH_NIRVANA_API_KEY="gnmcp_your_key_here"' >> ~/.zshrc
source ~/.zshrc

Then start/restart your editor from that shell session.

Check it was set:

echo "$GROWTH_NIRVANA_API_KEY"

Security Best Practices

• Do not commit .env.local to version control (add to .gitignore)
• Do not commit secret values in .mcp.json or other config files
• Keep API keys in environment variables or .env.local, never in JSON config

Suggested .gitignore entries:

.env.local
.env
# MCP config files (may contain secrets)
mcp.json
.mcp.json
.cursor/mcp.json

Releasing (Assumes v1.0.0 already exists)

Use this flow for every release after v1.0.0 so npm version, git tag, and GitHub stay in sync.

# 1) Ensure working tree is clean
git status

# 2) Commit any non-release edits
git add .
git commit -m "chore: prepare release"

# 3) Bump version and create release commit + tag together
# (from v1.0.0 this creates v1.0.1)
npm version patch -m "release: v%s"

# 4) Publish that version to npm
npm publish --access public

# 5) Push commits and tags to GitHub
git push origin main --follow-tags

Notes:

• Do not manually create release tags when using npm version.
• If v1.0.0 is already on npm and GitHub, the next patch release should be v1.0.1.