licium-cli

MCP server package manager — discover, install, and manage MCP servers from the command line. Think "npm for MCP servers."

Powered by Licium — the MCP server discovery and reputation platform.

Install

npm install -g licium-cli

Or use directly with npx:

npx licium-cli search "email API"

Commands

licium init

Create a licium.json config file in the current directory.

licium init

licium search <query>

Search for MCP servers by name or natural language description. Results are ranked by reputation score and show verification status, GitHub stars, and install commands.

licium search "email"
licium search "database management" --limit 5
licium search "web scraping browser automation"

Verification badges:

• verified — install, start, and MCP handshake all passed
• partial — install succeeded but handshake could not be verified
• failed — verification failed
• untested — not yet tested

licium add <name>

Add an MCP server to licium.json and automatically sync it to your Claude Desktop configuration.

licium add resend-mcp-server
licium add puppeteer
licium add github --skip-sync    # Don't sync to Claude Desktop

This command:

1. Searches the Licium registry for the server
2. Gets server details (install command, required env vars)
3. Adds it to licium.json
4. Syncs the config to Claude Desktop's claude_desktop_config.json

licium list

List all MCP servers configured in the current licium.json.

licium list
licium ls          # alias

Shows each server's command, arguments, and required environment variables.

licium remove <name>

Remove an MCP server from licium.json and Claude Desktop config.

licium remove resend-mcp-server
licium rm puppeteer              # alias

licium test

Test all configured MCP servers by spawning each process and performing an MCP handshake (JSON-RPC initialize request over stdio).

licium test

For each server, this:

1. Spawns the server process
2. Sends an MCP initialize message
3. Waits for a valid serverInfo response (15s timeout)
4. Reports pass/fail/timeout with duration

licium doctor

Diagnose your MCP server configuration and environment.

licium doctor

Checks:

• Node.js version (>= 18 required)
• npx availability
• licium.json exists and is valid JSON
• Claude Desktop config exists and has MCP servers
• licium.json and Claude Desktop config are in sync
• Required environment variables are set
• Licium API connectivity

licium update [name]

Check for latest versions of installed MCP servers by querying the npm registry.

licium update              # Check all servers
licium update puppeteer    # Check a specific server

Shows current vs. latest version for each npx-based server. Since npx -y always fetches the latest version on each run, this mostly serves as an informational check.

licium stack [name]

Browse and install curated MCP server stacks — pre-configured combinations of servers for common use cases.

licium stack                    # List available stacks
licium stack web-dev            # Install the web development stack
licium stack data-analysis      # Install the data analysis stack
licium stack customer-support --skip-sync

Available stacks:

| Stack | Description | Tools | |-------|-------------|-------| | web-dev | Web development essentials | GitHub, Puppeteer, Brave Search, Filesystem | | data-analysis | Data analysis and visualization | PostgreSQL MCP, Filesystem, Puppeteer, Fetch | | customer-support | Customer support automation | Resend, Slack, Linear, Brave Search | | content-creation | Content creation and research | Filesystem, Brave Search, Fetch, Puppeteer | | dev-tools | Developer productivity tools | GitHub, Git, Brave Search, Linear |

Quick Start

# Initialize a new project
licium init

# Search for email-related MCP servers
licium search "email"

# Add a server (auto-syncs to Claude Desktop)
licium add resend-mcp-server

# Or install a whole stack at once
licium stack web-dev

# Test the connections
licium test

# Check everything is configured correctly
licium doctor

Configuration

licium.json

Licium creates a licium.json file in your project directory:

{
  "servers": {
    "resend-mcp-server": {
      "command": "npx",
      "args": ["-y", "@resend/mcp-server"],
      "env": {
        "RESEND_API_KEY": ""
      }
    },
    "puppeteer": {
      "command": "npx",
      "args": ["-y", "@anthropic/mcp-server-puppeteer"]
    }
  }
}

Claude Desktop

Servers are automatically synced to Claude Desktop's config at:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json
• Linux: ~/.config/claude/claude_desktop_config.json

Use --skip-sync with licium add or licium stack to disable auto-sync.

Environment Variables

• LICIUM_API_URL — Override the Licium API URL (default: https://licium.ai)

Requirements

• Node.js >= 18
• npx (included with Node.js)

License

MIT