search_servers
Search MCP Registry for servers matching a keyword. Rank results by project tech stack relevance and evaluate GitHub maturity signals.
Instructions
Search the MCP Registry for servers matching a keyword.
Use this when the user asks for a specific server or technology. Pass project_path to automatically rank results by relevance to the project's detected tech stack — each result gets a "relevance" field ("high", "medium", "low") and a "match_reason" explaining the score.
When evaluate is True (default), each result also gets a "maturity" field with GitHub-based quality signals (stars, last commit, tier). Set evaluate=False for faster results without GitHub API calls.
After finding the right server, use configure_server with the package_identifier and registry_type from the results to install it.
Args: query: Search term (e.g. "postgres", "github", "slack", "docker"). limit: Maximum results to return (1-50, default 10). project_path: Optional project directory path. When provided, results are ranked by relevance to the detected tech stack and include credential_status for each result. evaluate: Whether to fetch GitHub maturity signals for each result (default True). Set to False for faster searches.
Returns: List of servers, each with: name, description, version, registry_type, package_identifier, transport, is_official, env_vars_required, repository_url, and source ("official" | "smithery" | "both"). When project_path is set, also includes relevance, match_reason, and credential_status. When evaluate is True, also includes maturity. All results include deterministic ranking metadata: intent_match_score, intent_match_reason, composite_score, and composite_breakdown. Smithery results also include use_count (popularity) and verified (quality badge).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| limit | No | ||
| project_path | No | ||
| evaluate | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |