mcp-directory

What problem does it solve?

With multiple Multi-Capability Platforms (MCPs) available, it's challenging to know which tool to use for a specific task, leading to inefficient choices, token waste, and unreliable operations (especially with buggy tools like Desktop Commander). This skill provides a clear guide to selecting the optimal MCP.

Core Features & Use Cases

• Comprehensive MCP Index: Lists all available MCPs (n8n, GitHub, Linear, Desktop Commander, Supermemory, Google Tasks) with their status, connection, and token cost.
• Usage Guidelines & Decision Tree: Provides clear criteria for when to use each MCP, including a decision tree for common tasks like file operations or project management.
• Anti-Patterns & Reliability Rankings: Highlights common mistakes to avoid and ranks MCPs by reliability, preventing frustration and wasted effort.
• Use Case: When Claude needs to read a file, this skill helps it decide whether to use GitHub MCP (if in a repo) or Desktop Commander (if local), saving tokens and avoiding Desktop Commander's known hangs.

Quick Start

This skill operates automatically when Claude needs to choose an MCP.

To manually query for guidance:

User: "What tools do you have for file operations?" Claude (using mcp-directory): "For file operations:

• If the file is in a GitHub repository, use GitHub MCP.
• If the file is on the local system, use Desktop Commander (with caution and timeouts).
• If the file is at a remote URL, use Desktop Commander read_file with isUrl=true."