Overview

This repository is a curated catalog of MCP (Model Context Protocol) servers, aggregating both open-source and proprietary implementations. It provides a searchable index of server projects, metadata (license, docs, supported features), and contributor information to help developers evaluate, compare, and adopt MCP-compatible servers.

The catalog is useful for teams selecting a server implementation, researchers benchmarking different approaches, and maintainers who want to publish their MCP server listing. By consolidating links, documentation references, and structured metadata, the catalog reduces discovery friction and standardizes how MCP servers are described and evaluated.

Repository: https://github.com/apappascs/mcp-servers-hub

Features

Centralized catalog of MCP server projects (open-source and proprietary)
Structured metadata per entry: repo/url, license, feature flags, docs, and tags
Contributor credits and contact information for each listing
Schema-driven validation to ensure consistent entries (JSON/YAML)
Searchable/filterable dataset for quick discovery by license, feature, or tag
Examples and templates for adding new servers to the catalog
Issue and contribution guidelines to standardize submissions

Installation / Configuration

Clone the catalog to view or contribute locally:

git clone https://github.com/apappascs/mcp-servers-hub.git
cd mcp-servers-hub

View the catalog as a static site (if the repo contains a web UI), or serve the raw files:

With a simple Python HTTP server (Serves files on http://localhost:8000):

python3 -m http.server 8000

If the project includes a Node-based dev site:

# install dependencies (if package.json present)
npm install
npm run dev

Adding a new server entry (example JSON). Place entries in the designated data directory (for example data/servers/):

{
  "id": "example-mcp-server",
  "name": "Example MCP Server",
  "url": "https://github.com/example/mcp-server",
  "license": "Apache-2.0",
  "type": "open-source",
  "documentation": "https://example.com/docs",
  "features": ["context-routing", "multi-tenant", "auth"],
  "tags": ["python", "grpc"],
  "contributors": [
    {
      "name": "Jane Doe",
      "contact": "mailto:[email protected]",
      "role": "maintainer"
    }
  ],
  "notes": "Supports the MCP v1 specification and includes examples."
}

Validation (recommended): if the repository provides a JSON Schema (e.g., schema/server.schema.json), validate entries locally:

# using a CLI JSON Schema validator such as ajv-cli
npm install -g ajv-cli
ajv validate -s schema/server.schema.json -d data/servers/example-mcp-server.json

Available Resources

Repository: https://github.com/apappascs/mcp-servers-hub
Typical files to look for in the repo:
- data/ or entries/ — JSON/YAML server listings
- schema/ — JSON Schema for entry validation
- CONTRIBUTING.md — how to propose or edit entries
- ISSUE_TEMPLATE.md — reporting catalog problems or requesting additions
- README.md — overview and contribution workflow
Example entry templates and sample listings to copy when adding your server
Search/filter UI or scripts (if provided) for programmatic filtering of the catalog

Typical Entry Schema (fields)

Field	Type	Description
id	string	Unique slug for the server
name	string	Human-readable name
url	string	Repo or product URL
license	string	License identifier or “proprietary”
type	string	“open-source” or “proprietary”
documentation	string	Link to docs or API reference
features	array	Key features (e.g., auth, multi-tenant)
tags	array	Tech stack tags (e.g., python, grpc)
contributors	array	People and roles responsible for the listing
notes	string	Additional notes or limitations

Use Cases

Selecting a server by license: Filter the catalog for “Apache-2.0” or “MIT” when you need permissive licenses for integration into your product.
Feature comparison during evaluation: Use the features array to quickly find servers that support context routing, multi-tenancy, or a specific authentication mechanism.
Onboarding new implementers: Share the catalog entry template with contributors so new MCP server projects can publish standardized metadata and documentation links.
Continuous integration: Add a CI job that validates newly submitted server entries against the provided JSON Schema to maintain data quality.
Research and benchmarking: Export the catalog data to compare performance-relevant attributes, supported protocols (HTTP/gRPC), or ecosystem compatibility.

Contributing & Maintenance Tips

Follow the repository’s CONTRIBUTING.md for the preferred format (JSON or YAML), commit conventions, and required fields.
Validate entries with the provided schema before submitting a pull request.
Keep documentation links up to date and include maintainers’ contact details for follow-up questions.
For proprietary listings, clarify commercial terms and provide a public docs link if available.

This catalog aims to be a practical starting point for developers evaluating MCP servers and for maintainers who want a consistent way to share their projects. For repository-specific instructions and the latest schema, visit the GitHub repository: https://github.com/apappascs/mcp-servers-hub.

MCP Server Catalog: Open-Source & Proprietary Listings