best-of s

This MCP server acts as a centralized catalog for the Best-of MCP Servers list. It aggregates metadata about multiple MCP projects, enabling clients to discover, rank, and query servers by category, popularity, or recency. With the provided tooling, you can start the server locally and access endpoints to list projects, filter by category, and fetch individual project details. The server is designed to be extendable, allowing you to plug in additional data sources or custom ranking metrics as needed.

To use it, start the server using the configured command, then send requests to the exposed endpoints to retrieve the ranked list, view project details, or integrate with other MCP tooling. Typical workflows include fetching the latest top projects, subscribing to weekly ranking updates, or exporting the current rankings to a consumer service for display in dashboards or editors that support MCP data feeds.

Prerequisites:

• Node.js (v14+ recommended) and npm installed on your system
• Git to clone the repository

1. Clone the repository git clone https://github.com/tolkonepiu/best-of-mcp-servers.git cd best-of-mcp-servers

2. Install dependencies npm install

3. Configure environment (optional)

   • PORT: Port to run the MCP server on (default 8080)
   • LOG_LEVEL: Logging level (e.g., info, debug) Create a .env file or export variables in your shell, for example: export PORT=8080 export LOG_LEVEL=info

4. Run the server npm start

5. Verify it is running Open http://localhost:8080 in your browser or use curl to query the MCP endpoints.

Additional setup (if you plan to deploy):

• Build steps may vary depending on deployment target; ensure the entry point is src/server.js as configured.
• Consider containerizing with Docker for consistent environments.

Notes and tips:

• The server exposes a catalog of MCP projects; ensure data sources are kept up to date to maintain accurate rankings.
• If you modify data sources or ranking logic, revalidate the API responses to ensure backward compatibility.
• Environment variables PORT and LOG_LEVEL can help tailor the server for development or production use.
• If you encounter connection or data-fetching issues, check network access to any external data sources and verify API rate limits.
• For production deployments, consider adding a reverse proxy (e.g., Nginx) and enabling TLS termination.
• The MCP data model allows for future expansion; you can add additional attributes to the server catalog without breaking existing clients.