MCP Compass
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-mcp-serversB | Use this tool when there is a need to findn external MCP tools. It explores and recommends existing MCP servers from the internet, based on the description of the MCP Server needed. It returns a list of MCP servers with their IDs, descriptions, GitHub URLs, and similarity scores. |
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
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as recommending MCP servers based on descriptions, and no other tools exist to cause confusion.
A single tool inherently exhibits perfect naming consistency, as there are no other tools to compare against. The tool name 'recommend-mcp-servers' follows a clear verb-noun pattern and uses hyphens consistently.
One tool is too few for a server named 'MCP Compass', which suggests a broader scope of functionality for exploring or navigating MCP servers. A single recommendation tool feels thin and incomplete for this apparent purpose, lacking supporting tools like search, filter, or get details.
The tool surface is severely incomplete for the inferred domain of MCP server exploration. While the tool can recommend servers, there are significant gaps: no ability to search, filter, get detailed information, list categories, or manage preferences. This will likely cause agent failures when trying to perform comprehensive MCP server discovery tasks.