Souls MCP Srv

🚀 Explore the Outstanding MCP Server

English Version

MCPSvr is an innovative branch from the 5ire project, aiming to host a community-driven MCP server directory. This platform enables developers to discover high-quality tools and provides a convenient way to share their own MCP server works.

🚀 The servers here support direct installation and operation with MCP clients like 5ire.

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

🚀 Quick Start

MCPSvr offers a platform for developers to engage with MCP servers. You can explore various servers and contribute your own configurations.

✨ Features

• Host a community-driven MCP server directory.
• Enable developers to discover useful tools.
• Provide a way to share MCP server works.
• Support direct installation and operation with MCP clients like 5ire.

📦 Installation

There is no specific installation process described in the original document.

💻 Usage Examples

Basic Usage

All registered MCP server configurations are centrally maintained in the /public/servers.json repository. Developers can submit new server configurations through GitHub pull requests (PRs).

Configuration Scheme

{
  "name": "Server Identifier",
  "key": "Unique Alphanumeric Identifier",
  "description": "Brief Implementation Overview",
  "command": "Execution Environment Specifier (e.g., uvx, npx, python, node)", 
  "args": [
    "Required Runtime Parameters"
  ],
  "env": {
    "Environment Variable Name": "Assignment"
  },
  "homepage": "Official Documentation URL"
}

Best Practices

1. Field Organization: Keep the configuration keys in alphabetical order.
2. Identifier Requirements:
   • Must be a unique alphanumeric string starting with a letter.
   • Prefixing with a number is strictly prohibited.
3. Metadata Handling:
   • The optional name field defaults to the value of key.
   • Environment variables and the homepage URL are auxiliary fields.

User-Defined Parameters

For interactive parameter requirements, follow the standardized format:

{{paramName@paramType::paramDescription}}

This convention allows client applications to extract and display parameters.

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 trailing slashes}}"
  ],
  "homepage": "https://github.com/modelcontextprotocol/servers"
}

Parameter Extraction:

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

Field Constraints:

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

📚 Documentation

The documentation mainly includes the configuration scheme, best practices, and user-defined parameter rules for MCP server configurations.

🔧 Technical Details

The document doesn't provide specific technical details that meet the requirement of more than 50 words.

📄 License

There is no license information provided in the original document.