📌Overview

Purpose: To provide a community-driven directory for MCP servers, allowing developers to discover and share exceptional tools effectively.

Overview: MCPSvr is a project derived from 5ire, designed to host a comprehensive collection of MCP server configurations that enable developers and users to easily install and run servers in compatible MCP clients.

Key Features:

Community-Driven Directory: Facilitates collaboration and sharing of MCP server configurations among developers, promoting innovation and discovery.
Streamlined Contribution Process: Developers can easily submit new server configurations via GitHub pull requests, ensuring a simple and efficient onboarding procedure.
Flexible Configuration Schema: Provides a clear structure for server definitions, allowing for diverse command specifications and environment management.

Discover Exceptional MCP Servers

MCPSvr is a community-driven directory of MCP servers, designed to help developers discover exceptional tools and share their own MCP server creations.

🚀 The servers here enable MCP clients like 5ire to install and run directly.

Contribution Guidelines

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

Configuration Schema

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

Best Practices

Field Organization: Maintain alphabetical ordering for configuration keys.
Identifier Requirements:
- Must be a unique alphanumeric string starting with a letter.
- Prohibit numeric prefixes.
Metadata Handling:
- Optional name field defaults to key display value.
- Environment variables and homepage URLs are supplementary fields.

User-Defined Parameters

For interactive parameter requirements, use the standardized format:

{{paramName@paramType::paramDescription}}

This convention allows parameter extraction and presentation in client applications.

Example Implementation:

{
  "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 about to access. Include trailing slash}}"
  ],
  "homepage": "https://github.com/modelcontextprotocol/servers"
}

Parameter Extraction:

{
  "name": "dirs",
  "type": "list",
  "description": "Directories you about to access. Include trailing slash"
}

Field Constraints: