Get the FREE Ultimate OpenClaw Setup Guide →

awesome -registry

AI-curated, self-updating directory of MCP servers. Discovered from GitHub & the official registry, analyzed and ranked by AI weekly.

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio sunnamed434-awesome-mcp-registry node server.js \
  --env LOG_LEVEL="info" \
  --env REGISTRY_API_KEY="your-api-key-if-required" \
  --env REGISTRY_API_URL="https://example.com/registry"

How to use

Awesome -registry is an AI-powered MCP registry that curates and serves a directory of MCP servers. It aggregates metadata, categories, and quality signals to help you discover suitable MCP tools and services for your workflows. Once running, you can browse the registry to find servers by category, read brief descriptions, and access quick-start guidance. The registry supports updating its entries over time, so you’ll see newer or improved MCP servers as they’re discovered and validated. Use the provided API endpoint or UI (if available) to search by keywords, filter by category, and inspect individual MCP server details to understand what capabilities they offer and how to invoke them in your MCP-enabled tooling.

How to install

Prerequisites:

  • Node.js (LTS) and npm installed on your system
  • Basic familiarity with running Node.js scripts

Steps:

  1. Clone the registry repository git clone https://github.com/your-org/awesome-registry.git cd awesome-registry

  2. Install dependencies npm install

  3. Configure environment (example) Create a .env file or export variables in your shell: REGISTRY_API_URL=https://example.com/registry REGISTRY_API_KEY=your-api-key-if-required LOG_LEVEL=info

  4. Run the registry server npm start

    or

    node server.js

  5. Verify the server is running Visit http://localhost:3000 (or the port you configured) to access the registry UI or API endpoints.

Additional notes

Notes:

  • Replace placeholder URLs and keys with your actual registry sources and access credentials.
  • If using a public MCP registry, ensure you respect rate limits and attribution requirements.
  • The registry may rely on external MCP sources; ensure those sources are reachable from your deployment environment.
  • Common env vars include REGISTRY_API_URL, REGISTRY_API_KEY, and LOG_LEVEL. Add additional environment controls as needed for your hosting environment.
  • If you encounter startup issues, check logs for missing dependencies or misconfigured endpoints, and verify that the Node.js version matches the project requirements.

Related MCP Servers

Sponsor this space

Reach thousands of developers