[!주의사항] ⚠️ ** 진행 중 **: 이 등록은 현재 활성 개발 및 테스트 단계입니다. API 및 데이터 구조는 변경할 수 있습니다. 아직 생산용으로 권장되지 않습니다.

**라이브 레지스트리 **: https://ravitemer.github.io/mcp-registry/registry.json

쉬운 통합을 위한 구조화된 설치 윤곽을 가진 Model Context Protocol (MCP) 서버의 커뮤니티 유지 보수.

환영

MCP Registry에 오신 것을 환영합니다!

Model Context Protocol (MCP) 생태계는 빠르게 성장하고 있지만, 서버 구성은 도전할 수 있습니다. 이 레지스트리는 구조화된 설치 윤곽을 가진 MCP 서버의 중앙 집중식, 지역 사회 유지한 수집을 제공해서 그 문제를 해결합니다.

**이 레지스트리 스페셜은 무엇입니까? **

• ☸ ** 원 클릭 설치 **: 각 서버는 인기 도구 (NPX, Docker, Python 등)에 대한 준비된 사용 구성으로 제공됩니다.
• 過去 Parameter System: ${VARIABLE}를 이용한 스마트 플레이스홀더 시스템
• ₱ Transport Information: 지원되는 의정서의 명확한 표시 (stdio, SSE, streamable-http)
• ✅ ** 품질 보증 ** : 포괄적 인 검증 및 테스트는 모든 정의 작업을 올바르게 보장합니다

MCP Registry

[!CAUTION] ⚠️ Work in Progress: This registry is currently in active development and testing phase. The API and data structure may change. Not recommended for production use yet.

Live Registry: https://ravitemer.github.io/mcp-registry/registry.json

A community-maintained registry of Model Context Protocol (MCP) servers with structured installation configurations for easy integration.

Welcome

Welcome to the MCP Registry! 🚀

The Model Context Protocol (MCP) ecosystem is growing rapidly, but finding and configuring servers can be challenging. This registry solves that problem by providing a centralized, community-maintained collection of MCP servers with structured installation configurations.

What makes this registry special?

• 📦 One-Click Installation: Each server comes with ready-to-use configurations for popular tools (NPX, Docker, Python, etc.)
• 🔧 Parameter System: Smart placeholder system using ${VARIABLE} syntax for easy customization
• 🚦 Transport Information: Clear indication of supported protocols (stdio, SSE, streamable-http)
• ✅ Quality Assurance: Comprehensive validation and testing ensure all definitions work correctly
• 🤝 Community-Driven: Easy contribution process via GitHub pull requests
• 🎯 Integration-Ready: Designed for seamless integration with MCP clients and hubs

Whether you’re building an MCP client, managing a server hub, or just want to discover new servers, this registry provides the structured data you need!

Registry Structure and Features

Overview

• Every MCP server in the registry is defined in a single YAML file
• Each server can have multiple installation methods (NPX, Docker, Python, etc.)
• Installation configurations are ready-to-use JSON templates
• Parameters use ${VARIABLE} syntax for easy replacement

Directory Structure

mcp-registry/
├── servers/                     # Server definition files (YAML)
│   ├── filesystem.yaml
│   ├── github.yaml
│   └── ...
└── schemas/                     # Validation schemas
  └── server-entry.js

Server Definition Format

Each server is defined in a YAML file in the servers/ directory with the following structure:

# Basic Information
id: server_name                    # Unique identifier (alphanumeric + underscore, min 3 chars)
name: Display Name                 # Human-readable name
description: Brief description under 400 characters
author: Author Name               # Author or organization
url: https://github.com/author/repo # Documentation or repository URL
license: MIT                      # Software license (optional)

# Classification
category: development             # Primary category
tags:                            # Searchable keywords
  - tag1
  - tag2

# Installation Methods
installations:
  - name: NPX                    # Installation method name
    description: Run using NPX   # Brief description