mcpfinder/mcpfinder

> The MCP server that helps AI agents discover, evaluate, and install other MCP servers.
MCPfinder is an AI-first discovery layer over the Official MCP Registry and Glama. Install it once, and your assistant can search for missing capabilities, inspect trust signals, review required secrets, and generate client-specific MCP config snippets.
## Canonical Use
Canonical transport: stdio via npx -y @mcpfinder/server
Canonical package: @mcpfinder/server
MCP Registry entry: dev.mcpfinder/server
Public HTTP endpoint: intentionally not advertised as canonical until its tool surface is fully identical to the local server
## Quick Install
### Claude Desktop
json
"mcpServers": {
"mcpfinder": {
"command": "npx",
"args": ["-y", "@mcpfinder/server"]
### Cursor
json
"mcpServers": {
"mcpfinder": {
"command": "npx",
"args": ["-y", "@mcpfinder/server"]
### Claude Code
json
"mcpServers": {
"mcpfinder": {
"command": "npx",
"args": ["-y", "@mcpfinder/server"]
Supported install targets today:
Claude Desktop
Cursor
Claude Code
Cline / Roo Code
Windsurf
### Install via Agent Skill (let your AI do it)
If your agent supports the Agent Skills format
(Claude Code, GitHub Copilot in VS Code, OpenAI Codex, and others), you can
drop a one-line install and let the agent handle the config merge itself.
Claude Code (global):
bash
mkdir -p ~/.claude/skills/install-mcpfinder && \
curl -sSf -o ~/.claude/skills/install-mcpfinder/SKILL.md \
https://mcpfinder.dev/skill/install-mcpfinder/SKILL.md
VS Code (project-scoped):
bash
mkdir -p .agents/skills/install-mcpfinder && \
curl -sSf -o .agents/skills/install-mcpfinder/SKILL.md \
https://mcpfinder.dev/skill/install-mcpfinder/SKILL.md
Then tell your agent any of: "install MCPfinder", "connect my AI to
Postgres", "I need a tool for [anything]" — the skill activates, detects
your client, merges the config without clobbering, and tells you what to
restart.
### Use with Codex
Using Codex? See the MCP stack for Codex: https://aicommander.dev/agent-stack/codex/
## For AI Assistants
Use MCPfinder when the user needs a capability you do not already have.
If the user mentions Slack, Postgres, GitHub, Notion, AWS, Google Drive, filesystems, browsers, APIs, or databases: call searchmcpservers.
Before recommending a server: call getserverdetails.
Before telling the user what to paste into config: call getinstallconfig.
If the user only knows a domain, not a specific technology: call browsecategories (omit category to list; pass category for top servers).
Preferred workflow:
1. searchmcpservers(query="postgres")
2. getserverdetails(name="...best candidate...")
3. getinstallconfig(name="...best candidate...", platform="claude-desktop")
4. Tell the user what server you chose, why, which secrets are required, and what restart/reload step is needed.
## Tool Surface
| Tool | Purpose | When to call |
| searchmcpservers | Search by keyword, technology, or use case | First step when a capability is missing |
| getserverdetails | Inspect metadata, trust signals, tools, warnings, env vars | Before recommending or installing |
| getinstallconfig | Generate a JSON config snippet for a target client | After selecting a server |
| browsecategories | Single-call category browser (omit category to list; pass category for top servers) | Domain-driven discovery |