Mcpsvr

🚀 Explore the Outstanding MCP Server

English Version

MCPSvr is an innovative derivative project nurtured by 5ire, aiming to build a community-driven MCP server directory. This platform empowers developers to discover excellent tools and provides a convenient way to share their MCP server works.

🚀 The servers here allow MCP clients like 5ire to be directly installed and run.

https://github.com/user-attachments/assets/3d1ec8db-2041-4f2d-b72c-eb8ae17ab31c

🚀 Quick Start

MCPSvr is a platform that enables developers to find great tools and share their MCP server works. It is a community-driven MCP server directory where MCP clients can directly install and run servers.

✨ Features

• Build a community-driven MCP server directory.
• Empower developers to discover excellent tools.
• Provide a convenient way for developers to share their MCP server works.
• Allow MCP clients like 5ire to directly install and run servers.

📚 Documentation

Contribution Guidelines

All registered MCP server configurations are uniformly maintained in a centralized repository located at /public/servers.json. Developers can submit pull requests (PRs) on GitHub to add new server configurations.

Configuration Architecture

{
  "name": "Server identifier",
  "key": "Unique alphanumeric identifier",
  "description": "Concise functional overview",
  "command": "Execution environment specifier (e.g., uvx, npx, python, node)",
  "args": [
    "Required runtime parameters"
  ],
  "env": {
    "Environment variable name": "Value assignment"
  },
  "homepage": "Official documentation URL"
}

Best Practices

1. Field Organization: Keep the configuration keys arranged in alphabetical order.
2. Identifier Requirements:
   • Must be a unique alphanumeric string starting with a letter.
   • Numeric prefixes are strictly prohibited.
3. Metadata Handling:
   • The optional name field uses the display value of key by default.
   • Environment variables and the homepage URL are auxiliary fields.

User-Defined Parameters

For interactive parameter requirements, please follow the standardized format:

{{paramName@paramType::paramDescription}}

This convention allows parameters to be extracted and displayed in the client application.

Example Implementation:

{
  "name": "File system access control",
  "key": "FileSystem",
  "command": "npx",
  "description": "Implement restrictions on directory-level operations by specifying parameters",
  "args": [
    "-y",
    "@modelcontextprotocol/server-filesystem",
    "{{dirs@list::Directories to be accessed. Include a trailing slash}}"
  ],
  "homepage": "https://github.com/modelcontextprotocol/servers"
}

Parameter Extraction:

{
  "name": "dirs",
  "type": "list",
  "description": "Directories to be accessed. Include a trailing slash"
}

Field Constraints:

• paramName must be unique in the server configuration.
• Supported data types include string, list, and number. Please ensure the correct type is used!
• Descriptive text is optional.