How to Find MCP Servers | Discovery Guide with MCPfinder

Registries and directories people actually use

There is no single complete catalog. Most developers combine a few sources:

Official MCP Registry — vendor-neutral metadata for publicly published servers; best starting point for “who published this?”
Glama — large searchable index with deeper per-server metadata and inspection tooling
Smithery — registry plus hosted deployment and managed OAuth for many remote servers
Directory sites (for example mcp.so) — useful for browsing categories; still verify before you connect

MCPfinder aggregates the Official MCP Registry, Glama, and Smithery into one index your agent can query — it works with those sources, not as a replacement for your AI client.

What to check before you install

Capability fit

Search by the job (filesystem, GitHub, Slack, Postgres), not by vanity rankings. Wrong tools waste context and increase risk.

Trust signals

Prefer clear upstream repos, multi-source listings, recent updates, and low warning-flag counts. A popular listing can still be abandoned.

Secrets & scope

Read required environment variables and OAuth scopes. Prefer least privilege; treat account-wide keys as root for that service.

Client compatibility

Confirm transport and config shape for Claude Desktop, Cursor, Claude Code, Cline, Windsurf, or your IDE. Install JSON differs by client.

Let your assistant search, then install

Search

Call search_mcp_servers with a capability or keyword. Review scores and recommendation reasons across registries.

Inspect

get_server_details surfaces tools, env vars, warnings, and transport before you commit.

Install

get_install_config emits paste-ready JSON for your client. Restart and verify the tools load.

Quick start · any MCP clientEXAMPLE

# Run MCPfinder via npx, then ask your agent to search
$ npx -y @mcpfinder/server

# Example ask: "find MCP servers for sqlite and show warnings"

Common questions

How do I find MCP servers?

Start with the Official MCP Registry for publisher identity, then search broader indexes such as Glama and Smithery. For agent-driven discovery, install MCPfinder so your AI client can search those registries, inspect trust signals, and generate install JSON.

Which MCP registries should I check?

The Official MCP Registry is the vendor-neutral metadata source. Glama and Smithery are widely used downstream directories and hosting registries. Directory sites such as mcp.so are useful for browsing. MCPfinder aggregates Official Registry, Glama, and Smithery into one agent-searchable index.

Is a listing the same as a safe install?

No. A directory listing is not a security review. Inspect tools, required environment variables, warnings, transport, and the upstream repository before connecting a server to an AI client.

How is MCPfinder different from a directory website?

MCPfinder is primarily an MCP server your assistant calls. It searches registries, surfaces trust signals and warnings, and emits client-specific install config. The mcpfinder.dev site explains the workflow; the product experience is agent-native discovery.

How to find MCP servers that fit your client