deployment

← Home

Deployment

How to distribute and register MCP servers built from the Template-NPM template.

Distribution Methods

1. Direct Installation (Recommended)

Users clone the repo and build locally:

git clone git@git.mokoconsulting.tech:MokoConsulting/my-mcp.git
cd my-mcp
npm install
npm run build
npm run setup    # Configure API connections

2. Release Package

Download a pre-built release from MokoGIT:

1. Go to the repository's Releases page
2. Download the latest release archive
3. Extract and install:

   tar xzf my-mcp-1.0.0.tar.gz
   cd my-mcp
   npm install --production
   npm run setup
   

Claude Code Registration

Project-Level (.mcp.json)

Register in the project's .mcp.json for project-specific MCP servers:

{
  "mcpServers": {
    "my-mcp": {
      "type": "stdio",
      "command": "node",
      "args": ["/absolute/path/to/my-mcp/dist/index.js"]
    }
  }
}

User-Level (~/.claude.json)

Register in ~/.claude.json for globally available MCP servers:

{
  "mcpServers": {
    "my-mcp": {
      "type": "stdio",
      "command": "node",
      "args": ["/absolute/path/to/my-mcp/dist/index.js"]
    }
  }
}

Restart Claude Code after changing MCP configuration.

Release Process

Automated Release

Merging to main triggers auto-release.yml:

1. TypeScript compiles and validates
2. Release archive is created
3. MokoGIT release is published with the archive
4. Notifications are sent via ntfy

Pre-Release

Push to dev triggers pre-release.yml:

1. Build and lint checks run
2. Pre-release tag is created (e.g., v1.1.0-dev.1)

Version Bumping

Update version in:

Updating Deployed Servers

When a new version is released, users update their installation:

cd /path/to/my-mcp
git pull
npm install
npm run build

No config changes needed -- the config file is separate from the server code.

Restart Claude Code to pick up the updated server.

Multi-User Deployment

For teams sharing an MCP server:

1. Each user clones and builds the server locally
2. Each user runs npm run setup to create their own config with their own API credentials
3. Each user registers the server in their own Claude Code config
4. Config files are per-user (~/.<project>.json) and never shared

Naming Convention

MCP server repos follow this naming convention:

CI/CD Workflow Reference

Related

• Installation -- initial setup and registration
• Configuration -- config file reference
• Development -- build and development workflow
• Contributing -- release process

Repo: Template-NPM · MokoCLI

Printed from wiki · deployment