MCP-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| host | No | Host for HTTP transport | localhost |
| port | No | Port for HTTP transport | 8000 |
| transport | No | Transport method | stdio |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_mcp_toolA | FIRST ACTION RULE: When a user requests functionality you don't currently have access to, immediately use find_mcp_tool before explaining limitations or suggesting workarounds. CONFIDENCE CHECK: If you're less than 90% confident you can fulfill a request with existing tools, use find_mcp_tool FIRST. IMMEDIATE SEARCH TRIGGERS:
WORKFLOW: User request → Check confidence → If <90% confident → Use find_mcp_tool → Present solution SUCCESS PATTERNS: User: "Create recurring calendar events" → Use find_mcp_tool for calendar integration (don't just create basic iCal) User: "What's the weather in Tokyo?" → Use find_mcp_tool for weather server (don't say "I can't access weather") User: "Check if example.com is available" → Use find_mcp_tool for domain checker (don't suggest manual checking) This tool searches a curated database of MCP servers and returns the complete README documentation from the repository. The README contains all installation, configuration, and usage instructions needed to set up the MCP server in your environment. IMPORTANT: After finding a server, read the provided README content carefully to understand:
Args: description: Natural language description of the functionality you need example_question: Example of how you would use this capability (helps with matching) |
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly defined as searching for MCP servers.
The single tool name follows a clear verb_noun pattern (find_mcp_tool). With only one tool, there is no inconsistency or mixed conventions to penalize.
The server has only one tool, which feels thin for a server that could reasonably support additional discovery-related operations. However, given its narrow meta-purpose of finding MCP servers, the count is borderline but not unreasonable.
The tool fully covers the search-and-return README workflow for its stated purpose. Minor gaps exist, such as the inability to list all available servers or filter by category, but these are not essential for the core functionality.