MCP Recommender
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| recommend_mcpB | Recommend MCP servers based on your development needs. Args: query: Description of the functionality you need (e.g., "database operations", "web scraping", "file management") limit: Maximum number of recommendations to return (default: 5) category: Filter by specific category (optional) language: Filter by programming language (optional) Returns: Formatted markdown string with MCP recommendations |
| list_categoriesB | List all available MCP categories. Returns: Formatted list of available categories |
| get_functional_keywordsB | Show available functional keyword mappings for better search results. Returns: Formatted list of functional keywords |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap: get_functional_keywords provides keyword mappings, list_categories shows available categories, and recommend_mcp generates server recommendations based on user needs. The tools target different aspects of the recommendation system and cannot be confused.
The naming follows a consistent verb_noun pattern (get_functional_keywords, list_categories, recommend_mcp) with clear, descriptive names. The minor deviation is that 'recommend_mcp' uses a verb-object structure rather than verb_noun, but this is still readable and maintains overall consistency.
With only 3 tools, the set feels thin for a server named 'MCP Recommender' that aims to help users find MCP servers. While the core functionality is covered, additional tools like filtering or detailed server information could enhance the scope. The count is borderline but workable.
The tool surface covers the essential workflows: exploring keywords and categories, and getting recommendations. Minor gaps exist, such as no tool to get detailed information about a specific server or to save/favorite recommendations, but agents can work around these with the provided tools.