Purpose
awesome-mcp-tools-mcp is used to retrieve over 2000 MCP (Model Context Protocol) servers from the awesome-mcp.tools directory from a terminal or MCP client. It provides directory search capabilities to both command-line users and various MCP clients.
Key capabilities
This npm package contains two components:
- awesome-mcp CLI: Search over 2000 MCP servers in the terminal. Pure Node 18+, zero dependencies.
- awesome-mcp-bridge: A minimal stdio↔Streamable-HTTP MCP proxy, about 100 lines, zero dependencies. It lets MCP clients that only support stdio (such as Claude Desktop, older Cline) connect to servers hosted at https://awesome-mcp.tools/mcp . It reads JSON-RPC from stdin, forwards it to that address, and streams the response back, with session IDs managed automatically.
Both share the same backend, awesome-mcp.tools. The directory is refreshed from the open-source ecosystem every 6 hours.
Usage
MCP bridge
Paste the configuration into the corresponding client configuration file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Or use Claude Desktop's Settings → Connectors → Add custom connector, and enter the URL https://awesome-mcp.tools/mcp(supported only in newer versions).
Cursor natively supports remote URLs, no bridge needed; the configuration is located at ~/.cursor/mcp.json.
For Codex, append to ~/.codex/config.toml.
For Cline, configure in the VS Code panel's cline_mcp_settings.json .
Windsurf configuration is located at ~/.codeium/windsurf/mcp_config.json.
Ready-to-paste copies are located in the repository's examples/ directory.
Verify the hosted endpoint
Verify without installing, or use raw curl.
Override the bridge target
Use AWESOME_MCP_URL=https://your-mirror/mcp awesome-mcp-bridge to override the bridge target, useful for self-hosting or testing.
Use cases
- Quickly search MCP servers in the terminal.
- Connect the hosted MCP server of awesome-mcp.tools to clients such as Claude, Cursor, Codex, Cline, Windsurf, etc.
- Let clients that only support stdio access Streamable-HTTP servers through the bridge.
Limitations and notes
- The hosted server backend (Go API, ingestion crawler, SSR, OG image generation) is a separate proprietary codebase and is not in this repository. This repository contains only: the awesome-mcp CLI source code, the awesome-mcp-bridge stdio→HTTP proxy source code, client configuration examples, and a live tools/list response snapshot for offline reference.
- The directory data provided by the backend is open: each server entry retains its upstream license. The backend code is not open source.
- The transport protocol is Streamable HTTP (MCP specification 2025-06-18).
- Authentication: none (free, no API key).
- Server card:
/.well-known/mcp/server-card.json. - Underlying REST API:
/api/docs(OpenAPI 3.0). - For the complete input/output schemas, see the live tools/list endpoint; for the offline snapshot, see
tools.json, and for transport metadata, see the server card. npm testRun the CLI library tests (6 pass under Node 18+). The bridge currently only has manual smoke tests against production (piping a JSON-RPC initialize intobin/awesome-mcp-bridge.js); mock-based unit tests are planned for v0.2.1.- Production readiness: awesome-mcp.tools is live, monitored, and refreshed every 6 hours. Issue feedback: github.com/adw0rd/awesome-mcp-tools-mcp/issues.