Skip to main content
Glama
README.md
# MCP Compass 🧭

[![Model Context Protocol](https://img.shields.io/badge/Model%20Context%20Protocol-purple)](https://modelcontextprotocol.org)

<a href="https://glama.ai/mcp/servers/85uxmq6wx7"><img width="380" height="200" src="https://glama.ai/mcp/servers/85uxmq6wx7/badge" alt="Compass MCP server" /></a>

## MCP Discovery & Recommendation

### Experience MCP Compass 🌐

You can now experience MCP discovery directly on our website!  
šŸ‘‰ **[Explore MCP Compass](https://mcphub.io/)** šŸ‘ˆ  

Dive in to discover the power of MCP services in action with real-time recommendations and insights.

---

## What is this? šŸ¤”

MCP Compass is a discovery & recommendation service that helps you explore Model Context Protocol servers. It acts as a smart guide that helps AI assistants find and understand available MCP services out there based on **natural language queries**, making it easier to discover and utilize the right tools for specific tasks.

### Quick Example
<div align="center">
  <img src="assets/demo.png" alt="MCP Compass Demo - Airtable Server Search" width="800"/>
</div>

## Features 🌟

- šŸ” **Smart Search**: Find MCP services using natural language queries
- šŸ“š **Rich Metadata**: Get detailed information about each service
- šŸ”„ **Real-time Updates**: Always up-to-date with the latest MCP services [![MCP Servers](https://img.shields.io/badge/MCP-Servers-red?logo=github)](https://github.com/modelcontextprotocol/servers)
- šŸ¤ **Easy Integration**: Simple to integrate with any MCP-compatible AI assistant

## Quick Start šŸš€

### Usage

1. Clone the repository

or 

2. Use `npx`


### Installation

For Claude Desktop, edit your `claude_desktop_config.json` file:

#### MacOS/Linux
``` bash
code ~/Library/Application\ Support/Claude/claude_desktop_config.json
```

#### Windows
``` bash
code $env:AppData\Claude\claude_desktop_config.json
```

1. **As an MCP Service**:

   Add to your AI assistant's MCP configuration to enable service discovery capabilities.
   

   ``` json
   {
   "mcpServers": {
      "mcp-compass": {
         "command": "npx",
         "args": [
            "-y",
            "@liuyoshio/mcp-compass"
         ]
      }
   }
   }
   ```

   or

   ``` json
   {
   "mcpServers": {
      "mcp-compass": {
         "command": "node",
         "args": [
            "/path/to/repo/build/index.js"
         ]
      }
   }
   }
   ```



## License šŸ“

MIT License - See [LICENSE](LICENSE) file for details.

## Support šŸ’¬

- šŸ› [Report issues](https://github.com/liuyoshio/mcp-compass/issues)
- šŸ’” [Feature requests](https://github.com/liuyoshio/mcp-compass/issues)
- šŸ“– [Documentation](https://github.com/liuyoshio/mcp-compass)

TDQS

B3.4/5.0

Scored across 1 tool

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness2/5

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.

Maintenance

ActivityInactive
ResponsivenessUnresponsive