/ Directory / Playground / Smithery CLI
● Official smithery-ai ⚡ Instant

Smithery CLI

by smithery-ai · smithery-ai/cli

The official Smithery CLI — smithery install <server> to add MCPs to your client config, plus a dev mode for building your own.

Smithery hosts a public registry of MCP servers. This CLI lets you install/uninstall against your client config, list installed servers, and scaffold a new MCP for publishing.

Why use it

Key features

Live Demo

What it looks like in practice

ready

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "smithery-cli": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli"
      ]
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "smithery-cli": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli"
      ]
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "smithery-cli": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli"
      ]
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "smithery-cli": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli"
      ]
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "smithery-cli",
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json
{
  "context_servers": {
    "smithery-cli": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@smithery/cli"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add smithery-cli -- npx -y @smithery/cli

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use Smithery CLI

Install an MCP without editing config by hand

👤 Developers ⏱ ~15 min intermediate

When to use: You're tired of hand-merging stdio configs.

Flow
  1. Browse
    smithery search <topic>✓ Copied
    → Matches listed
  2. Install
    smithery install <slug>✓ Copied
    → Config edited; restart client
  3. Verify
    smithery list✓ Copied
    → Server present

Outcome: New MCP installed without config archaeology.

Combinations

Pair with other MCPs for X10 leverage

smithery-cli + mcp2cli

Debug a Smithery-installed MCP directly

Combine smithery-cli with mcp2cli: Debug a Smithery-installed MCP directly✓ Copied

Tools

What this MCP exposes

ToolInputsWhen to callCost
CLI subcommands (see docs) install / uninstall / list / dev / publish 1 call

Cost & Limits

What this costs to run

API quota
N/A
Tokens per call
N/A
Monetary
Free
Tip
Pin versions — bare slugs track latest

Security

Permissions, secrets, blast radius

Credential storage: Edits your client config files
Data egress: smithery.ai for registry
Never grant: blindly install — review tool list first

Troubleshooting

Common errors and fixes

Config not found

Pass --config-path; CLI guesses defaults but they vary by OS

Alternatives

Smithery CLI vs others

AlternativeWhen to use it insteadTradeoff
Manual configYou like full controlMore work

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills