Show HN: MCPfinder – An MCP server that finds and installs other MCP servers (mcpfinder.dev)

9 points by coderai 2mo ago ↗ HN

I’ve been building and using agents heavily lately. The Model Context Protocol ecosystem is growing insanely fast, but discovering and configuring new tools is still highly manual. Every time I needed to connect an agent to a new service, I had to browse registries, figure out the transport type, identify required env vars, and manually update "mcp.json" files.

So I built MCPfinder. It aggregates servers from the official MCP registry, Glama, and Smithery (around 25,000 combined entries) into a deduplicated, ranked catalog.

But the real twist is the DX: MCPfinder is itself an MCP server :D

You only install it once as your "base capability" via standard stdio: npx -y @mcpfinder/server

From then on, when you tell your AI, "I need to query my PostgreSQL database," the magic happens autonomously.

It's completely free, AGPL-3.0 licensed, and built purely to optimize AI-tool surface discovery.

I'd love to hear your thoughts, feedback, or edge cases where JSON generation for specific platforms is acting up.

1 comment

[ 4.8 ms ] story [ 10.8 ms ] thread

VitalStack 2mo ago ↗

Cool timing on this. I've been building vital-stack.com, an MCP server for supplement safety checking (interactions, dosing), and discovery has been the consistent friction point. People ask "how do I find this?" and there's no good answer right now.

Question: does MCPfinder handle domain-specific MCPs well, or is it still weighted toward dev tooling? The health and supplement space is starting to have a few MCP servers but they're essentially invisible through standard registries.