Pharos

situational

Package manager and registry for MCP servers, with dependency resolution and a local daemon.

Visit getpharos.dev →Add to kit Open in Noemium

ledger entry · observed by @whysanesanders

Brings npm-like semantics to MCP servers: search across multiple registries, install with dependency resolution, lock versions, and run a local daemon that JIT-loads HTTP/SSE servers. The safe config writes and broad client support make it the most credible attempt yet to tame the growing MCP-server zoo.

Strengths

npm-like package management for MCP servers with dependency resolution and version locking.
Local daemon JIT-loads HTTP/SSE MCP servers and keeps client configs clean.
Broad client support makes it practical across different MCP consumers.

Known limitations

Registry and discovery are new; package quality varies.
stdio servers are not managed by the daemon; clients still handle those as child processes.
Publishing requires GitHub OAuth and acceptance of a young registry's policies.

Use it when

Teams managing many MCP servers and wanting install/lock semantics.
Setups that rely on HTTP/SSE MCP servers served locally.

Skip it when

You mostly use stdio MCP servers the daemon cannot manage.
You are not comfortable trusting a young registry's policies.
You cannot accept OAuth-based publishing requirements.

Buy-check

·Price — free, MIT open source CLI; registry is free to use as of 2026-08-19. Open the pricing page, not a screenshot.
·Free tier — Free tier exists — burn it first.
·Cancel fallout — What happens to your data/projects on cancel — check the ToS, not the FAQ.
·Seat math — Per-seat pricing multiplies quietly. Count seats before the annual plan.
·Who skips it — Also skipped when: You mostly use stdio MCP servers the daemon cannot manage.; You are not comfortable trusting a young registry's policies..