@aurracloud/mcp-cli
Advanced tools
A command-line tool to install, manage, and setup MCP (Model Context Protocol) servers with Docker support
███╗ ███╗ ██████╗██████╗
████╗ ████║██╔════╝██╔══██╗
██╔████╔██║██║ ██████╔╝
██║╚██╔╝██║██║ ██╔═══╝
██║ ╚═╝ ██║╚██████╗██║
╚═╝ ╚═╝ ╚═════╝╚═╝
By aurracloud.com
CLI to install and setup MCP servers
A command-line tool to install, manage, and setup MCP (Model Context Protocol) servers with Docker support.
✨ Global CLI Tool: Install once with npm install -g and use the mcp command anywhere
🐳 Docker Support: Secure, sandboxed execution of MCP servers by default
🔍 Multi-Registry Search: Supports npm, GitHub, and Smithery registries
📦 GitHub URL Support: Install and uninstall directly from GitHub repositories
🛡️ Security First: Docker isolation by default, with optional direct execution
📋 Smart Configuration: Automatic detection and setup of MCP server configurations
🔧 Comprehensive Management: Install, uninstall, list, and get info about servers
⚡ Flexible Usage: Global installation recommended, npx available for one-time use
🤖 JSON Mode: Structured output for automation and programmatic use
⚙️ Configuration Arguments: Non-interactive setup with --args flag
📊 Multiple Log Levels: Verbose, debug, and quiet modes for different use cases
Install globally for the best experience:
# Install globally (recommended)
npm install -g @aurracloud/mcp-cli
# Now you can use the 'mcp' command anywhere
mcp install @modelcontextprotocol/server-filesystem -c claude
mcp list -c claude
mcp info @modelcontextprotocol/server-filesystem
The MCP CLI supports global options that can be used with any command:
# Verbose output - shows detailed progress information
mcp install package-name -c claude --verbose
# Debug output - shows comprehensive debugging information
mcp install package-name -c claude --debug
# Quiet mode - suppresses all output except errors
mcp install package-name -c claude --quiet
# JSON mode commands automatically use quiet mode
mcp install package-name -c claude --json # Automatically quiet
mcp info package-name --json # Automatically quiet
Global Options:
-v, --verbose: Enable verbose output with detailed progress information-d, --debug: Enable debug output with comprehensive debugging details-q, --quiet: Suppress all output except errors (useful for scripting)Note: JSON mode (--json) automatically enables quiet mode to prevent logging interference with structured output.
Install once and use everywhere:
# Install globally from npm
npm install -g @aurracloud/mcp-cli
# Now you can run the command from anywhere
mcp install package-name -c claude
mcp info package-name
mcp list -c claude
mcp uninstall package-name -c claude
For occasional use without installation:
# Run commands directly without installing
npx @aurracloud/mcp-cli install package-name -c claude
npx @aurracloud/mcp-cli info package-name
npx @aurracloud/mcp-cli list -c claude
npx @aurracloud/mcp-cli uninstall package-name -c claude
# Clone the repository
git clone https://github.com/aurracloud/mcp-cli.git
cd mcp-cli
# Install dependencies
npm install
# Run in development mode
npm run dev
# Or build and run
npm run build
npm start
# Install with default options (uses Docker for security)
mcp install package-name -c claude
# Run the MCP server directly on host (not recommended)
mcp install package-name -c claude -d
# JSON mode for programmatic use
mcp install package-name -c claude --json
# Install with configuration arguments
mcp install package-name -c claude --args API_KEY=secret DEBUG_MODE=true
# JSON mode with configuration (for automation)
mcp install package-name -c claude --json --args API_KEY=secret --verbose=true
# Direct installation with configuration
mcp install package-name -c claude --direct --args FILESYSTEM_ROOT=/tmp
# Or use npx for one-time use
npx @aurracloud/mcp-cli install package-name -c claude
Installation Options:
-c, --client <client> (required): Specify the client (cursor, claude)-d, --direct: Run directly on host instead of Docker (not recommended for security)-j, --json: Output installation result in JSON format for programmatic use-a, --args <args...>: Provide configuration arguments in key=value formatJSON Mode:
The --json flag enables structured output perfect for automation and scripting:
# Successful installation returns structured data
mcp install @modelcontextprotocol/server-filesystem -c cursor --json --args FILESYSTEM_ROOT=/tmp
{
"success": true,
"packageName": "@modelcontextprotocol/server-filesystem",
"serverName": "@modelcontextprotocol/server-filesystem",
"client": "cursor",
"installationMode": "docker",
"runtime": "node",
"configuration": {
"command": "docker",
"args": ["run", "--rm", "-i", "-e", "FILESYSTEM_ROOT=/tmp", "node:latest", "npx", "-y", "@modelcontextprotocol/server-filesystem"]
},
"environmentVariables": 1
}
# Errors also return structured JSON
mcp install nonexistent-package -c cursor --json
{
"success": false,
"error": "Package nonexistent-package does not exist on npm registry or PyPI.",
"packageName": "nonexistent-package"
}
Configuration Arguments:
Use the --args flag to provide configuration without interactive prompts:
# Environment variables (key=value format)
mcp install server-name -c claude --args API_KEY=secret DATABASE_URL=postgres://...
# Command line arguments (--flag=value format)
mcp install server-name -c claude --args --port=3000 --host=localhost
# Mixed configuration
mcp install server-name -c claude --args API_KEY=secret --verbose=true DEBUG_MODE=false
How it works:
The install command:
-d flag# Uninstall from a specific client
mcp uninstall package-name -c claude
# Also works with GitHub URLs (resolves to actual package name)
mcp uninstall https://github.com/owner/repo -c claude
mcp uninstall owner/repo -c claude
# Or use npx for one-time use
npx @aurracloud/mcp-cli uninstall package-name -c claude
The uninstall command now intelligently resolves GitHub URLs to the actual package name by:
The list command displays all currently installed MCP servers for a specific client:
# List all MCP servers for Claude
mcp list -c claude
# List all MCP servers for Cursor
mcp list -c cursor
# Or use npx for one-time use
npx @aurracloud/mcp-cli list -c claude
Features:
What it shows:
The info command provides comprehensive information about MCP servers by checking multiple registries with intelligent fallback:
# Get information about a server (checks npm, GitHub, and Smithery)
mcp info package-name
# Works with multiple formats
mcp info express # npm package
mcp info owner/repo # GitHub repository
mcp info @owner/repo # npm scoped package format
mcp info https://github.com/owner/repo # full GitHub URL
# JSON mode for programmatic use
mcp info package-name --json
# Or use npx for one-time use
npx @aurracloud/mcp-cli info package-name
# Set your Smithery API token for additional registry information
export SMITHERY_API_TOKEN=your-token
Options:
-j, --json: Output information in structured JSON format for automationJSON Mode:
The --json flag provides structured output perfect for automation:
# Get structured information about a package
mcp info @modelcontextprotocol/server-filesystem --json
{
"packageName": "@modelcontextprotocol/server-filesystem",
"npm": {
"found": true,
"packageInfo": {
"name": "@modelcontextprotocol/server-filesystem",
"version": "0.6.2",
"description": "MCP server for filesystem operations"
},
"isExecutable": true,
"command": "npx -y @modelcontextprotocol/server-filesystem"
},
"git": {
"found": true,
"repoInfo": {
"name": "servers",
"fullName": "modelcontextprotocol/servers"
},
"isExecutable": true
},
"smithery": {
"found": true,
"serverDetails": {
"qualifiedName": "@modelcontextprotocol/server-filesystem",
"displayName": "Filesystem Server"
}
},
"summary": {
"foundInNpm": true,
"foundInGit": true,
"foundInSmitery": true,
"hasMcpConfig": true
}
}
How it works:
Keep your CLI tool up to date with the latest features and bug fixes:
# Upgrade to the latest version
mcp upgrade
# Or use npx (always gets latest version)
npx @aurracloud/mcp-cli upgrade
This command:
The publish command allows you to publish your MCP server to the registry, making it available for others to discover and install. It automatically reads your existing MCP server configuration from package.json (Node.js) or pyproject.toml (Python):
# Publish from current directory (reads package.json or pyproject.toml)
mcp publish
# Publish from a specific directory
mcp publish -d /path/to/your/mcp-server
# Specify custom slug and category
mcp publish -s my-custom-slug -c tools
# Publish to a different registry
mcp publish -r https://your-registry.com
# JSON mode for automation
mcp publish --json
# Combine options
mcp publish -d ./my-server -s custom-name -c agents -r https://registry.com --json
Options:
-d, --directory <dir>: Project directory to publish from (default: current directory)-s, --slug <slug>: Custom slug for the registry (auto-generated from package name if not provided)-c, --category <category>: Category: agents, tools, prompts, data-feeds (auto-detected from keywords if not provided)-r, --registry <url>: Registry URL to publish to (default: https://aurracloud.com)-j, --json: Output result in JSON format for automationPrerequisites:
Authentication Required: You must be logged in to publish
mcp login # Authenticate first
MCP Server Configuration: Your project must have an MCP server configuration
Supported Project Types:
The publish command automatically detects and reads MCP server configurations from:
{
"name": "@myusername/my-mcp-server",
"version": "1.2.0",
"description": "My awesome MCP server for file operations",
"author": "John Doe",
"license": "MIT",
"repository": "https://github.com/myusername/my-mcp-server",
"keywords": ["mcp", "filesystem", "tools"],
"mcpServer": {
"description": "MCP server for secure file operations",
"connection": {
"type": "stdio",
"command": "node",
"args": ["dist/index.js"]
},
"capabilities": {
"tools": true,
"resources": true
},
"metadata": {
"category": "tools"
}
}
}
[project]
name = "my-mcp-server"
version = "1.2.0"
description = "My awesome MCP server for file operations"
authors = [{name = "John Doe", email = "john@example.com"}]
license = {text = "MIT"}
keywords = ["mcp", "filesystem", "tools"]
[project.urls]
repository = "https://github.com/myusername/my-mcp-server"
[tool.mcp-server]
description = "MCP server for secure file operations"
[tool.mcp-server.connection]
type = "stdio"
command = "python"
args = ["-m", "my_mcp_server"]
[tool.mcp-server.capabilities]
tools = true
resources = true
[tool.mcp-server.metadata]
category = "tools"
How It Works:
The publish command automatically extracts the following information:
From package.json/pyproject.toml:
From mcpServer/[tool.mcp-server] config:
Auto-Generated:
-s)npm (Node.js), python (Python), or github (repository-only)Publishing Workflow:
Ensure your project has MCP server configuration in package.json or pyproject.toml
Login to the registry:
mcp login
Publish your server:
mcp publish
Examples:
# Basic publish from current directory
mcp publish
# Publish with custom slug and category
mcp publish -s my-filesystem-server -c tools
# Publish Python project with custom category
mcp publish -d ./my-python-mcp -c data-feeds
# JSON mode for CI/CD
mcp publish --json
JSON Mode:
Use --json flag for automation and CI/CD integration:
# Successful publish
mcp publish --json
{
"success": true,
"message": "MCP server published successfully!",
"data": {
"id": "uuid",
"slug": "my-awesome-mcp-server",
"name": "My Awesome MCP Server",
"category": "tools",
"type": "npm",
"author": "John Doe",
"featured": false,
"verified": false,
"created_at": "2024-01-16T10:00:00Z"
}
}
# Missing MCP configuration
mcp publish --json
{
"success": false,
"error": "No MCP server configuration found."
}
Notes:
package.json) and Python (pyproject.toml) projectsThe MCP CLI is designed for both interactive use and automation. Use JSON mode and configuration arguments for seamless integration into scripts and CI/CD pipelines.
# Install with JSON output for automation
RESULT=$(mcp install @modelcontextprotocol/server-filesystem -c cursor --json --args FILESYSTEM_ROOT=/tmp)
echo $RESULT | jq '.success' # true
# Check installation status
if echo $RESULT | jq -e '.success' > /dev/null; then
echo "Installation successful"
echo $RESULT | jq '.configuration.command'
else
echo "Installation failed:"
echo $RESULT | jq '.error'
fi
# Get package information programmatically
INFO=$(mcp info @modelcontextprotocol/server-filesystem --json)
echo $INFO | jq '.summary.foundInNpm' # true
echo $INFO | jq '.npm.packageInfo.version' # "0.6.2"
#!/bin/bash
# List of servers to install
SERVERS=(
"@modelcontextprotocol/server-filesystem"
"@modelcontextprotocol/server-brave-search"
"custom-server"
)
# Configuration for each server
declare -A SERVER_ARGS
SERVER_ARGS["@modelcontextprotocol/server-filesystem"]="FILESYSTEM_ROOT=/home/user"
SERVER_ARGS["@modelcontextprotocol/server-brave-search"]="BRAVE_API_KEY=your-key"
SERVER_ARGS["custom-server"]="API_KEY=secret DEBUG_MODE=true"
# Install each server
for server in "${SERVERS[@]}"; do
echo "Installing $server..."
args="${SERVER_ARGS[$server]}"
if [ -n "$args" ]; then
result=$(mcp install "$server" -c cursor --json --args $args)
else
result=$(mcp install "$server" -c cursor --json)
fi
if echo "$result" | jq -e '.success' > /dev/null; then
echo "✅ $server installed successfully"
else
echo "❌ Failed to install $server:"
echo "$result" | jq '.error'
fi
done
# GitHub Actions example
name: Install MCP Servers
on: [push]
jobs:
install-servers:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Setup Node.js
uses: actions/setup-node@v3
with:
node-version: '18'
- name: Install MCP CLI
run: npm install -g @aurracloud/mcp-cli
- name: Install MCP Server
run: |
result=$(mcp install @modelcontextprotocol/server-filesystem -c cursor --json --args FILESYSTEM_ROOT=/workspace)
echo "$result" | jq '.success' || exit 1
- name: Verify Installation
run: |
info=$(mcp info @modelcontextprotocol/server-filesystem --json)
echo "Installed version: $(echo "$info" | jq -r '.npm.packageInfo.version')"
The CLI also includes utilities to check if GitHub repositories exist and whether they're executable via npx. This is particularly useful for MCP servers that are not published to npm but are available on GitHub:
import { checkGitRepoExistence, getGitNpxCommand, parseGitHubIdentifier } from './git';
// Check if a GitHub repository exists and is executable
const result = await checkGitRepoExistence('owner/repo');
if (result.exists) {
console.log('Repository exists on GitHub!');
if (result.packageInfo) {
console.log('Repository has a package.json');
if (result.isExecutable) {
console.log('Repository is executable via npx');
console.log(`Executable: ${result.executableName}`);
}
}
}
// Get the recommended command to run the repository
const npxCmd = await getGitNpxCommand('owner/repo');
if (npxCmd) {
console.log(`Run with: ${npxCmd.command} ${npxCmd.args.join(' ')}`);
}
The git integration supports multiple repository identifier formats:
owner/repo - Simple owner/repository format@owner/repo - npm scoped package format (@ symbol is automatically removed)https://github.com/owner/repo - Full GitHub URLhttps://github.com/owner/repo.git - Full GitHub URL with .git extensiongit@github.com:owner/repo.git - SSH format# Check a repository using the example script
npx ts-node examples/check-git-repo.ts facebook/create-react-app
npx ts-node examples/check-git-repo.ts https://github.com/vercel/pkg
npx ts-node examples/check-git-repo.ts @microsoft/vscode
npx ts-node examples/check-git-repo.ts microsoft/vscode
See the examples in examples/check-git-repo.ts for more details.
npm run build
src/commands/ directorysrc/index.tsWe use automated releases with GitHub Actions. Use the interactive release script:
# Interactive release (recommended)
npm run release
# Or quick releases
npm run release:patch # Bug fixes
npm run release:minor # New features
npm run release:major # Breaking changes
This will automatically:
See RELEASE.md for detailed instructions.
git checkout -b feature-namenpm run buildgit commit -am 'Add feature'git push origin feature-nameMIT
FAQs
A command-line tool to install, manage, and setup MCP (Model Context Protocol) servers with Docker support
The npm package @aurracloud/mcp-cli receives a total of 2 weekly downloads. As such, @aurracloud/mcp-cli popularity was classified as not popular.
We found that @aurracloud/mcp-cli demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
/Security News
Socket researchers discovered nine malicious NuGet packages that use time-delayed payloads to crash applications and corrupt industrial control systems.
Security News
Socket CTO Ahmad Nassri discusses why supply chain attacks now target developer machines and what AI means for the future of enterprise security.
Security News
Learn the essential steps every developer should take to stay secure on npm and reduce exposure to supply chain attacks.