agent-discover

agent-discover

MCP server registry and marketplace. Discover, install, activate, and manage MCP tools on demand. Acts as a dynamic proxy -- activated servers have their tools merged into the registry's own tool list, so agents can use them without restarting.

Every MCP client today — Claude Code, Cursor, Codex CLI, Aider, Continue, plain MCP clients — requires a full agent-session restart to pick up a newly registered MCP server. The tool catalog is frozen at startup. agent-discover is the only path to register a new server and have it become discoverable in the same running session. This is the one differentiator that survives against every host, even those with their own built-in deferred-tool loaders.

Search spans the official MCP registry, npm, and PyPI in one query, so popular servers that aren't in the official index (Microsoft @playwright/mcp, @modelcontextprotocol/server-*, mcp-server-fetch, mcp-server-git, …) all show up.

Built for AI coding agents (Claude Code, Codex CLI, Gemini CLI, Aider) but works equally well with any MCP client, REST consumer, or WebSocket listener.

---

Light Theme	Dark Theme

---

Why

Static MCP configs mean every server is always running, even when unused. Adding a new server requires editing config files and restarting. There is no way to browse what is available or install new tools at runtime.

	Without agent-discover	With agent-discover
Discovery	Must know server names in advance	Browse the official MCP registry, search by keyword
Installation	Edit config files, restart agent	One tool call installs and registers
Activation	All servers always running	Activate/deactivate on demand, tools appear/disappear live
Secrets	API keys in config files or env	Per-server secret storage, auto-injected on activation
Monitoring	No visibility into server health	Health checks, per-tool metrics, error counts
Management	Manual config edits	Dashboard + REST API for config, tags

---

Features