Smithery

Smithery is a CLI and marketplace for discovering MCP servers, connecting to them, and using their tools with managed credentials. It supports search, tool browsing, schema inspection, and scoped access control.

AI Developer Tools AI Agents Directory

Visit Website

Overview

Smithery is a marketplace and CLI for finding, connecting to, and using MCP tools and skills. The homepage describes it as a way to connect to 100K+ tools and skills, and the example workflow shows search, add, list, inspect, and call operations from one command-line interface.

The product is built around MCP connections, namespaces, and token scoping. That makes it useful for developers and teams that need to discover external services, connect them with managed credentials, and interact with tool APIs in a controlled way.

Features

Marketplace search

Search the marketplace for MCP servers by name or keyword, then choose the server you want to connect to.

Connect to MCP servers

Add a server by URL or qualified name and manage it as a connection with an ID and metadata.

Browse tools by namespace

List available tools in a tree view, including nested tool groups such as `issues` under a connected server.

Schema inspection

Inspect each tool's input and output JSON schema before calling it, which helps confirm expected parameters.

Tool invocation

Call tools from the CLI with structured JSON arguments after a connection is set up.

Namespace and token controls

Use namespaces, token policies, and request-level restrictions to separate environments and control access.

Use Cases

Discover new MCP servers
Search for MCP servers by keyword, compare options, and connect to the one that matches a task or integration need.
Connect and authorize services
Add a server connection, handle authorization in the browser, and keep the connection available for later tool use.
Explore and use tools
List a server's tools, inspect their schemas, and call them with structured JSON when building or testing workflows.
Organize multi-environment work
Create namespaces for different apps or environments so development, staging, and production resources stay separated.
Control access for automated use
Generate scoped tokens or request restrictions when a browser, mobile app, or agent needs limited access to connections.

Pros and Cons

Pros

Combines discovery, connection management, schema inspection, and tool calls in one CLI.
Supports managed MCP connections with OAuth flow, credential storage, token refresh, and session lifecycle.
Includes namespace support for separating app or environment resources.
Emits JSONL when output is piped, which supports scripting and automation.
Offers token scoping and request-level restrictions for tighter access control.

Cons

The pricing page is blocked in the supplied evidence, so plan details and costs are not visible.
The source gives strong CLI workflow examples, but broader integration coverage is only partially documented in the collected material.

FAQ

What does Smithery do?

Smithery provides a CLI and marketplace for finding MCP servers, connecting to them, and using their tools from one workflow. The source shows search, add, list, inspect, and call commands, plus authentication and namespace management.

How do you set it up?

The quick-start flow shows installation with `npm install -g @smithery/cli`, then `smithery auth login`, followed by searching for MCP servers and adding a connection. The CLI also supports listing tools, inspecting tool schemas, and calling tools once connected.

What kind of output does the CLI produce?

The homepage shows outputs such as search results, tool listings, and JSON schema inspection, and it notes that piped output is emitted as JSONL. That makes the CLI useful for scripting and for reading structured tool data.

Can teams or multiple environments use it?

Smithery supports namespaces for separating resources by app or environment, and it supports managed connections with OAuth flow, credential storage, token refresh, and session lifecycle.

What does Smithery cost?

The pricing page is blocked by a Vercel security checkpoint, so the source does not reveal plan names, limits, or whether there is a free tier. Pricing details are therefore not available from the provided evidence.