Mcpsvr
Discover Exceptional MCP Servers
Installation
npx mcpsvrAsk AI about Mcpsvr
Powered by Claude Β· Grounded in docs
I know everything about Mcpsvr. Ask me about installation, configuration, usage, or troubleshooting.
0/500
Reviews
Documentation
MCPSvr
A community-driven directory for discovering, reviewing, and contributing MCP servers.
MCPSvr is a lightweight web directory for Model Context Protocol servers. It helps developers browse available servers, understand how each one is configured, and contribute new entries through pull requests.
The repository centers on a curated public/servers.json registry, so MCP clients such as 5ire can install and run supported servers directly.
https://github.com/user-attachments/assets/3d1ec8db-2041-4f2d-b72c-eb8ae17ab31c
Table of Contents
- Why MCPSvr
- What You Can Do
- Project Structure
- Run Locally
- How to Add a Server
- Server Schema
- Parameter Placeholders
- Contribution Notes
Why MCPSvr
MCP servers are growing fast, but good discovery is still fragmented. MCPSvr gives the ecosystem a simple shared registry with enough metadata for humans to evaluate tools and for clients to automate setup.
What You Can Do
- Discover MCP servers from a single browsable directory
- Review runtime commands, arguments, environment variables, and homepage links
- Contribute new servers or improve existing metadata via pull requests
- Reuse the registry in MCP clients that support direct installation
Project Structure
.
βββ app/ # Next.js app router pages
βββ components/ # Reusable UI components
βββ lib/ # Utility helpers
βββ public/
β βββ logo.png
β βββ servers.json # Central MCP server registry
βββ README_cn.md # Chinese README
Run Locally
Prerequisites
- Node.js 18+
- npm (or another package manager compatible with
package-lock.json)
Install
npm install
Start the development server
npm run dev
Then open http://localhost:3000.
Build for production
npm run build
npm run start
How to Add a Server
All registered MCP servers are maintained in public/servers.json. To contribute a new entry:
- Fork the repository
- Add or update a server object in
public/servers.json - Keep keys consistently ordered
- Open a pull request with links to the project homepage or docs
Server Schema
{
"name": "Server Identifier",
"key": "Unique alphanumeric identifier",
"description": "Concise implementation overview",
"command": "Execution environment specifier (for example uvx, npx, python, node)",
"args": [
"Required runtime arguments"
],
"env": {
"ENVIRONMENT_VARIABLE": "Value assignment"
},
"homepage": "Official documentation URL"
}
Field Guidelines
keymust be unique, alphanumeric, and start with a letternameis optional and falls back tokeywhen omittedenvandhomepageare optional but strongly recommended- Keep descriptions short and practical so clients can display them cleanly
Parameter Placeholders
When a server needs user-provided input, use the placeholder format below:
{{paramName@paramType::paramDescription}}
Example:
{
"name": "File System Access Control",
"key": "FileSystem",
"command": "npx",
"description": "Enforces directory-level operation restrictions through specified arguments",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"{{dirs@list::directories you are about to access, include trailing slash}}"
],
"homepage": "https://github.com/modelcontextprotocol/servers"
}
Supported placeholder types include string, list, and number.
Contribution Notes
- Prefer accurate metadata over marketing copy
- Double-check command arguments before submitting
- Include a homepage or docs link whenever possible
- If you add a new field in the future, keep the schema backwards compatible for downstream clients
