# MCPFinder
> Enables AI assistants to discover and integrate new capabilities by providing tools for searching, retrieving details, and configuring MCP servers across various applications.
Canonical: https://www.mcpfolio.com/servers/mcpfinder
Last updated: 2026-10-28
## Catalog record

- Publisher: mcpfinder
- Categories: development, database, search, file-system, version-control, communication

## Website

https://mcpfinder.dev/

## Repository

https://github.com/mcpfinder/server

## Transports

stdio

## Authentication

No credentials were configured; the tested read-only tool “search_mcp_servers” succeeded in an isolated environment. Other tools may have additional requirements.

## Tools

- **search_mcp_servers**: Call this first whenever the user needs a capability you do not already have. Use it when the user mentions an external service, a database, a filesystem, a SaaS tool, or asks "can you connect to X?". Examples: "connect to postgres" -> query "postgres"; "read my Slack" -> query "slack"; "browse local files" -> query "filesystem". If results are weak, retry with a broader term. After choosing a candidate, call get_server_details before recommending or installing it.
- **get_server_details**: Always call this before recommending or installing a server. It returns the metadata you need to judge safety and fit: install method, transport, environment variables, source count, trust signals, warnings, and any discovered tools/capabilities. Use it to warn the user about secrets, stale projects, or weak metadata before calling get_install_config.
- **get_install_config**: Use this after get_server_details to generate a ready-to-paste JSON config snippet for the target client. Returns structured config, file paths, required env vars, restart guidance, and safety flags like requires_user_secrets and safe_to_autoinstall.
- **browse_categories**: Single-call category browser for broad discovery. Call with no `category` to list all categories with counts; call with a `category` to get the highest-signal servers in that category. Prefer search_mcp_servers when the user names a concrete technology like Slack, Postgres, GitHub, or Notion; use this when discovery is domain-driven (database, filesystem, communication, security, ai, etc.).

## Sources

- [MCP.Directory public profile](https://mcp.directory/servers/mcpfinder)
- [Linked publisher repository](https://github.com/mcpfinder/server)
- [npm-declared package repository](https://github.com/mcpfinder/mcpfinder)
- [npm registry metadata](https://registry.npmjs.org/%40mcpfinder%2Fserver)
- [maintainer_or_vendor_tool_documentation](https://github.com/mcpfinder/mcpfinder)

## Setup

Use the interactive setup panel on [the detail page](https://www.mcpfolio.com/servers/mcpfinder) to view instructions for each supported client.