VS Code can run MCP servers so agents like Cline reach databases, browsers, docs, and APIs. MCPfinder searches Official Registry, Glama, and Smithery, then emits a VS Code-compatible install config so you spend less time hunting directories.
Agents in VS Code are strongest when they 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 VS Code. From there the agent can search catalogued servers, inspect manifests and warnings, and ask for a VS Code-ready JSON snippet.
Keep browsing optional. Let VS Code call MCPfinder when a capability is missing.
Add the npx @mcpfinder/server entry to .vscode/mcp.json, then reload the window.
Ask for “an MCP server for Postgres” (or similar). The agent uses search_mcp_servers and ranks candidates.
get_install_config returns a VS Code-oriented snippet plus the usual trust checks before you commit secrets.
// .vscode/mcp.json (project) { "servers": { "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 a project .vscode/mcp.json.
MCPfinder treats Cline in VS Code as 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 platform="cline". It returns a ready-to-paste snippet that uses the servers key and a project .vscode/mcp.json path.Install MCPfinder once. Search registries, inspect trust signals, and paste client-ready config.