Discover Exceptional MCP Servers

What is Discover Exceptional MCP Servers?

Discover Exceptional MCP Servers (MCPSvr) is a community-driven web directory for discovering, reviewing, and contributing Model Context Protocol (MCP) servers. It hosts a curated public/servers.json registry that developers and MCP clients (such as 5ire) can use to browse available servers and install them directly.

How to use Discover Exceptional MCP Servers?

You can browse the directory online or run it locally with Node.js 18+ by cloning the repository, running npm install, then npm run dev to start at http://localhost:3000. To contribute a new server, fork the repo, add an entry to public/servers.json, and open a pull request.

Key features of Discover Exceptional MCP Servers

• Centralized registry of MCP servers in public/servers.json
• Browse servers and review commands, arguments, and environment variables
• Contribute new entries or improve metadata via pull requests
• Supports parameter placeholders for user‑provided inputs
• Reusable by MCP clients that support direct installation
• Lightweight Next.js 15 project with a clean browsing interface

Use cases of Discover Exceptional MCP Servers

• Discover MCP servers from a single browsable directory
• Evaluate a server’s runtime configuration (command, args, env) before use
• Contribute a new MCP server to the ecosystem
• Integrate the registry into an MCP client for automated server setup

FAQ from Discover Exceptional MCP Servers

What data structure does the registry use?

Each server entry requires a unique key, a command (e.g. npx, uvx), and args. Optional fields include name, env, homepage, and a description. Parameter placeholders like {{paramName@type::description}} allow user‑provided input.

How do I add a server to the registry?

Fork the repository, edit public/servers.json to add a server object following the schema, keep keys consistently ordered, and open a pull request with links to the project homepage or docs.

What are the runtime requirements to run the directory locally?

Node.js 18+ and npm (or a compatible package manager). Then run npm install and npm run dev; for production use npm run build && npm run start.

Where is the server data stored?

All server entries are maintained in the public/servers.json file inside the repository. The directory renders this file on the frontend.

Does the directory support authentication or transport details?

No. The directory only stores metadata (command, args, env, homepage). Transport, authentication, and other runtime details are left to the server’s own documentation and the client that installs it.