
Mcp Server Find
Discover and install MCP servers from the Official Registry, Glama, and Smithery without manually searching three sites every time you extend your agent.
Overview
io.github.daedalus/mcp-server-find is a MCP server for the Build phase that discovers and helps install MCP servers from the Official Registry, Glama, and Smithery.
What is this MCP server?
- Aggregates MCP server discovery across Official Registry, Glama, and Smithery.
- PyPI package mcp-server-find v0.1.1 with stdio MCP transport.
- Reduces tab-hopping when solo builders expand Claude Code or Cursor capabilities.
- Open source at github.com/daedalus/mcp-server-find with standard MCP server.schema.json.
- Meta-layer tooling: an MCP server whose job is to find more MCP servers.
- Indexes discovery across 3 named sources: Official Registry, Glama, and Smithery
- Server version 0.1.1 on PyPI identifier mcp-server-find
- stdio transport in MCP server metadata
Community signal: 1 GitHub stars.
What problem does it solve?
MCP ecosystems are fragmented across registries and marketplaces, so finding the right server and install steps wastes time before you can build.
Who is it for?
Indie builders assembling their first or tenth MCP stack in Claude Code, Cursor, or Codex who want unified search.
Skip if: Teams that already pin a fixed internal server list with governance, or builders who need deep security attestation beyond catalog metadata.
What do I get? / Deliverables
After you add the stdio server, your agent can query multiple MCP catalogs and guide installs from one discovery workflow.
- Unified agent-driven search across three MCP server sources
- Faster shortlist and install flow for new MCP integrations
Recommended MCP Servers
Journey fit
Server discovery is core Build work when you assemble the MCP toolbox around your product and workflow. Agent-tooling is the primary shelf because the product’s purpose is finding and installing other MCP servers for your coding agent.
How it compares
MCP discovery/install helper, not a replacement for individual domain MCP servers or Skillselion’s curated journey browse.
Common Questions / FAQ
Who is io.github.daedalus/mcp-server-find for?
Solo developers and agent users who regularly add MCP servers and want one discovery path across Official Registry, Glama, and Smithery.
When should I use io.github.daedalus/mcp-server-find?
Use it during Build agent-tooling setup whenever you need to search catalogs, compare options, or install new MCP servers into your client.
How do I add io.github.daedalus/mcp-server-find to my agent?
Install PyPI package mcp-server-find, configure it as a stdio MCP server in your client, then use its discovery tools before installing chosen servers per their docs.