Skip to main content

​
System Requirements

Before installing MCPKit, ensure your system meets these requirements:
  • Node.js 18.0.0 or later
  • npm 9.0.0 or later (comes with Node.js)
  • Operating System: macOS, Linux, or Windows
Check your Node.js version with node --version

​
Install with npm

The easiest way to install MCPKit is via npm: 
npm install -g @kevinoconnell/mcpkit
The -g flag installs MCPKit globally, making it available from anywhere in your terminal.

​
Verify Installation

Confirm MCPKit is installed correctly: 
mcpkit version
You should see the current version number printed to the console.

​
Alternative Installation Methods

  • pnpm
  • yarn
  • From Source
pnpm add -g @kevinoconnell/mcpkit

​
Initial Configuration

After installing MCPKit, you need to configure your API keys.

​
Get Your API Keys

You’ll need:
  1. Browserbase API Key and Project id
    • Sign up at browserbase.com
    • Navigate to your dashboard
    • Copy your API key and Project ID from the settings
  2. LLM API Key (choose one):

​
Configure Secrets

Run the setup wizard: 
mcpkit secrets
You’ll be prompted to enter your credentials: 
? Enter your Browserbase API key: bb_xxxxxxxxxxxxxxxx
? Select your LLM provider: Google Gemini
? Enter your Gemini API key: AIxxxxxxxxxxxxxxxxx
Your credentials are stored locally in ~/.mcpkit/secrets.json and are never shared.

​
Verify Configuration

Check that your secrets are configured correctly: 
mcpkit secrets show
This will display your configured provider (without showing the full API keys).

​
Updating MCPKit

To update to the latest version: 
npm update -g @kevinoconnell/mcpkit
Or reinstall: 
npm install -g @kevinoconnell/mcpkit@latest
Check for updates regularly to get the latest features and bug fixes.

​
Uninstalling

To remove MCPKit from your system: 
npm uninstall -g @kevinoconnell/mcpkit
Your configuration files in ~/.mcpkit/ will remain. To completely remove all MCPKit data:
  • macOS/Linux
  • Windows
npm uninstall -g @kevinoconnell/mcpkit
rm -rf ~/.mcpkit

​
Troubleshooting Installation

If you encounter permission errors on macOS/Linux, you have two options:Option 1: Use a Node version manager (recommended)
# Install nvm
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash

# Install Node.js
nvm install 18
nvm use 18

# Now install mcpkit
npm install -g @kevinoconnell/mcpkit
Option 2: Use sudo (not recommended)
sudo npm install -g @kevinoconnell/mcpkit
Using sudo with npm can cause permission issues. We recommend using a Node version manager instead.
If mcpkit command is not found after installation:
  1. Check npm global bin path: 
    npm config get prefix
  2. Add npm bin to PATH: macOS/Linux (add to ~/.bashrc or ~/.zshrc): 
    export PATH="$(npm config get prefix)/bin:$PATH"
    Windows: Add the npm global bin path to your system PATH environment variable.
  3. Restart your terminal and try again.
MCPKit requires Node.js 18 or later. Update Node.js:Using nvm (recommended):
nvm install 18
nvm use 18
Or download from: nodejs.org
If installation hangs or fails:
  1. Clear npm cache: 
    npm cache clean --force
  2. Use a different registry: 
    npm install -g @kevinoconnell/mcpkit --registry=https://registry.npmjs.org/
  3. Try with verbose logging: 
    npm install -g @kevinoconnell/mcpkit --verbose

​
Next Steps

Quickstart Guide

Create your first MCP server in 5 minutes

CLI Commands

Learn about all available commands