Comparison
PHAROS vs Smithery: Hosted Connect vs Local Control
Both tools get MCP servers working, and both do it well. Smithery runs the hosted path: a large registry plus a connect layer where auth, credentials, and sessions are handled for you. Pharos runs the local path: one Go binary, servers executing on your machine, and no runtime to maintain. The right question is not which tool is better. It is where you want your servers to live.
At a glance
The short version, feature by feature.
| Feature | PHAROS | Smithery |
|---|---|---|
| Install model | Single Go binary. No runtime to install. | npx @smithery/cli. Node.js required on the machine. |
| Where servers run | Local stdio, on your machine. The pharos daemon JIT-loads remote HTTP/SSE servers and unloads idle ones (--idle-timeout). | Hosted and remote. Auth, credentials, and sessions handled for you. |
| Registry scope | Seven sources: modelcontextprotocol.io, glama.ai, lobehub.com, mcp.so, mcp.directory, Smithery, plus Pharos-hosted. | Its own large registry, with thousands of tools and services by its own description. |
| Client support | 16 named clients, including Claude Desktop, Claude Code, Cursor, Codex, Zed, and Aider. | Client-agnostic install model: any client that can run npx. |
| Publishing | Supported. Search, install, publish, and manage in one CLI, with install receipts on every change. | Supported. Publish and deploy flows are part of the platform. |
| Extras | Install receipts, drift detection with pharos doctor --diff, and pharos import to adopt existing client configs. | Hosted auth and session handling for remote servers. |
Install model
PHAROS
Single Go binary. No runtime to install.
Smithery
npx @smithery/cli. Node.js required on the machine.
Where servers run
PHAROS
Local stdio, on your machine. The pharos daemon JIT-loads remote HTTP/SSE servers and unloads idle ones (--idle-timeout).
Smithery
Hosted and remote. Auth, credentials, and sessions handled for you.
Registry scope
PHAROS
Seven sources: modelcontextprotocol.io, glama.ai, lobehub.com, mcp.so, mcp.directory, Smithery, plus Pharos-hosted.
Smithery
Its own large registry, with thousands of tools and services by its own description.
Client support
PHAROS
16 named clients, including Claude Desktop, Claude Code, Cursor, Codex, Zed, and Aider.
Smithery
Client-agnostic install model: any client that can run npx.
Publishing
PHAROS
Supported. Search, install, publish, and manage in one CLI, with install receipts on every change.
Smithery
Supported. Publish and deploy flows are part of the platform.
Extras
PHAROS
Install receipts, drift detection with pharos doctor --diff, and pharos import to adopt existing client configs.
Smithery
Hosted auth and session handling for remote servers.
Where PHAROS wins
Local-first control
Servers run on your machine as local stdio processes. Your configs stay on your disk, credentials stay in your files, and nothing about a Pharos install requires phoning home. Remote servers still work: the daemon JIT-loads them when needed and unloads them when idle.
One binary, no Node runtime
Pharos is a single Go binary that installs with one curl command. There is no Node.js version to keep current and no npx indirection between you and a working install. Deterministic installs pin semver ranges, so what you install is what you get.
Receipts for every change, and drift detection
Every install writes a machine-readable receipt of exactly which config files changed. After that, pharos doctor --diff compares your managed entries against the pharos.lock baseline and catches hand edits before they become mysteries.
Where Smithery wins
Hosted auth, credentials, and sessions
For remote servers, having Smithery hold credentials and handle sessions for you is genuinely convenient. There is nothing local to manage, and connection state lives where the server lives. For remote-heavy stacks, that removes a whole class of setup work.
A large registry with a deploy flow
Smithery's registry is large by its own description, thousands of tools and services, and it pairs publishing with a deploy flow for server authors. If you are shipping a hosted server and want discovery and deployment from one place, that pipeline is real.
Zero-install path for supported clients
Smithery's hosted layer can produce a working connection for a supported client without installing a CLI first. Pharos needs its binary on your machine from step one.
Which should you pick
If your stack is remote-heavy and you would rather someone else hold the credentials and keep the sessions alive, Smithery is built for exactly that. Its hosted connect layer removes the local setup work, and its registry is deep enough that you will rarely need to look elsewhere. A lot of teams want precisely that trade, and for them Smithery is the better fit.
Pick Pharos if you want servers running on your own machine, if your agents install and manage servers themselves, if you want to search across registries instead of one, or if your environment sits near an air gap where a hosted session layer is a liability rather than a feature. The two also compose: Pharos indexes Smithery as one of its seven sources, so servers listed on Smithery are reachable through Pharos with full source attribution.
Try Pharos
Install the CLI, then import your existing configs with pharos import so nothing you already set up is lost.
# macOS / Linux
curl -fsSL https://getpharos.dev/install | sh
# Windows PowerShell
irm https://getpharos.dev/install.ps1 | iexFrequently asked questions
Is Pharos free?
Yes. The Pharos CLI is open source under MIT, and every package in the registry installs free. You only need a GitHub-linked account to publish your own servers.
What is the difference between Pharos and Smithery?
Pharos is a single Go binary with no runtime requirement. It searches seven registry sources including Smithery, installs into 16 named clients, and records a machine-readable receipt for every change. Smithery is a large MCP registry with a hosted connect layer: installs run through npx @smithery/cli, and auth, credentials, and sessions are handled for you on the hosted side. The short version: Pharos keeps servers on your machine, Smithery hosts the connect path.
Does Pharos work with Smithery servers?
Yes. Smithery is one of the seven sources in Pharos's federated search, so servers listed there appear in pharos search results with their source attributed. You can install them into any of the 16 supported clients with Pharos.
Comparing against mcpm.sh instead? See PHAROS vs mcpm.sh.