Cursor can run MCP servers so the in-editor agent reaches databases, browsers, docs, and APIs. MCPfinder searches Official Registry, Glama, and Smithery, then emits Cursor-compatible install config so you spend less time hunting directories.
Cursor’s agent is strongest when it can pull the right tools for the repo in front of you. MCP servers supply those tools — filesystem helpers, issue trackers, SQL, browsers, and more — but picking and configuring them from scattered registries is slow.
MCPfinder installs as one MCP server inside Cursor. From there the agent can search 25K+ catalogued servers, inspect manifests and warnings, and ask for a Cursor-ready JSON snippet.
Keep browsing optional. Let Cursor call MCPfinder when a capability is missing.
Add the npx @mcpfinder/server entry to Cursor MCP settings / mcp.json, then reload.
Ask for “an MCP server for Postgres” (or similar). Cursor uses search_mcp_servers and ranks candidates.
get_install_config returns a Cursor-oriented snippet plus the usual trust checks before you commit secrets.
// Cursor mcp.json / MCP settings { "mcpServers": { "mcpfinder": { "command": "npx", "args": ["-y", "@mcpfinder/server"] } } }
Official Registry + Glama + Smithery in a single agent tool, instead of three browser tabs mid-debug.
See required secrets and install complexity before you paste a server into project or global Cursor config.
MCPfinder knows Cursor is a first-class client and shapes install output accordingly.
Free AGPL-3.0 tooling. Run via npx, pin a version, or vendor the package — your call.
get_install_config with Cursor as the client. It returns a ready-to-paste snippet and notes the config location Cursor expects.Install MCPfinder once. Search registries, inspect trust signals, and paste client-ready config.