Smithery — MCP Server Registry and Installer

What it is

Smithery is a registry and CLI tool for discovering and installing MCP servers. It maintains a curated catalog of MCP servers -- database connectors, API integrations, file system tools, and more -- that you can browse, search, and install with a single command. Smithery handles the configuration for Claude Code, Cursor, and other MCP-compatible clients automatically.

Smithery targets developers who use AI coding assistants and want to extend them with MCP integrations without manually configuring each server.

How it saves time or tokens

Setting up an MCP server manually involves finding the package, installing dependencies, writing a JSON config block, and debugging connection issues. Smithery automates the entire process: search for a server, run one install command, and the server is configured and ready. For teams using multiple MCP servers, this saves significant setup and maintenance time.

How to use

1. Search for MCP servers:

npx @smithery/cli search "database"

1. Install a server for your client:

npx @smithery/cli install @modelcontextprotocol/server-postgres --client claude

1. The server is automatically configured in your MCP client settings. Start using it immediately.

Example

# Install multiple MCP servers
npx @smithery/cli install @modelcontextprotocol/server-filesystem --client claude
npx @smithery/cli install @modelcontextprotocol/server-github --client claude
npx @smithery/cli install @modelcontextprotocol/server-sqlite --client claude

# List installed servers
npx @smithery/cli list

# Update all servers
npx @smithery/cli update

After installation, your AI assistant can access the filesystem, GitHub repos, and SQLite databases through MCP tools.

Related on TokRepo

• MCP Integrations -- GitHub MCP server for repository access
• AI Tools for Coding -- Developer tools and extensions

Common pitfalls

• Some MCP servers require environment variables (API keys, database URLs). Smithery prompts for these during install but missing values cause silent failures.
• MCP server updates may introduce breaking changes. Pin versions in production environments and test updates in development first.
• Not all MCP servers in the registry are actively maintained. Check the last update date and issue count before installing unfamiliar servers.