Port registry site over

Author: niechen

.github/workflows/deploy.yml

@@ -2,8 +2,11 @@ name: Deploy to GitHub Pages
 
 on:
   push:
-    branches: [ "main" ]
+    branches:
+      - main
   workflow_dispatch:
+  schedule:
+    - cron: '0 */6 * * *'  # Run every 6 hours
 
 permissions:
   contents: read
@@ -15,20 +18,59 @@ concurrency:
   cancel-in-progress: false
 
 jobs:
-  deploy:
-    environment:
-      name: github-pages
-      url: ${{ steps.deployment.outputs.page_url }}
+  validate:
+    uses: ./.github/workflows/validate-manifests.yml
+
+  build:
     runs-on: ubuntu-latest
+    needs: validate
     steps:
       - name: Checkout
         uses: actions/checkout@v4
+      
       - name: Setup Pages
-        uses: actions/configure-pages@v4
+        uses: actions/configure-pages@v5
+      
+      - name: Install uv with caching
+        uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+          cache-dependency-glob: "pyproject.toml"
+
+      - name: Install dependencies
+        run: |
+          uv sync
+          
+      - name: Setup site structure
+        run: |
+          mkdir -p pages/registry
+          mkdir -p pages/api/servers
+          
+      - name: Run preparation script
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          chmod +x ./scripts/prepare.sh
+          source .venv/bin/activate
+          ./scripts/prepare.sh ./pages
+        
+      
+      - name: Build with Jekyll
+        uses: actions/jekyll-build-pages@v1
+        with:
+          source: ./pages
+          destination: ./_site
+      
       - name: Upload artifact
         uses: actions/upload-pages-artifact@v3
-        with:
-          path: 'pages'
+
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    needs: build
+    steps:
       - name: Deploy to GitHub Pages
         id: deployment
-        uses: actions/deploy-pages@v4
+        uses: actions/deploy-pages@v4

.github/workflows/validate-manifests.yml

@@ -0,0 +1,25 @@
+name: Validate Server Manifests
+
+on:
+  pull_request:
+    branches: [ main ]
+  workflow_call:
+
+jobs:
+  validate:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Validate Server JSON Files
+        uses: cardinalby/schema-validator-action@v3
+        with:
+          # Path to files to validate (glob pattern)
+          file: 'mcp-registry/servers/*.json'
+          # Schema file to validate against
+          schema: 'mcp-registry/schema/server-schema.json'
+          # Mode (lax, spec, default, strong)
+          mode: 'default'
+          # Experimental: fix schema formats if needed
+          fixSchemas: 'false'

.gitignore

@@ -65,4 +65,5 @@ logs/
 # jekyll
 _site/
 .jekyll-cache/
-.jekyll-metadata
+.jekyll-metadata
+_dev/

CONTRIBUTING.md

@@ -0,0 +1,103 @@
+# Contributing to getmcp.io
+
+Thank you for considering contributing to getmcp.io! This document outlines the process for adding or updating MCP servers in the registry.
+
+## Adding a New Server
+
+1. Fork this repository
+2. Create a new JSON file named after your server under `mcp-registry/servers/` (use kebab-case, e.g., `github.json` or `time-converter.json`)
+3. Ensure your server JSON file adheres to the [server schema](/mcp-registry/schema/server-schema.json)
+
+### Server JSON Requirements
+
+Your server JSON file must include the following required fields:
+
+```json
+{
+  "name": "your-server-name",
+  "display_name": "Your Server Display Name",
+  "description": "Brief description of the server's functionality",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/your-username/your-repo"
+  },
+  "author": {
+    "name": "Your Name"
+  },
+  "license": "MIT",
+  "categories": ["category1", "category2"],
+  "tags": ["tag1", "tag2"],
+  "arguments": {
+    "EXAMPLE_ARG": {
+      "description": "Description of this argument",
+      "required": false
+    }
+  },
+  "commands": {
+    "npm": {
+      "type": "npm",
+      "command": "npx",
+      "args": ["your-server-package"],
+      "env": {
+        "EXAMPLE_ARG": "${EXAMPLE_ARG}"
+      }
+    }
+  },
+  "examples": [
+    {
+      "title": "Example usage",
+      "description": "Brief description of example",
+      "prompt": "Example prompt to demonstrate server functionality"
+    }
+  ]
+}
+```
+
+For a complete reference of all available fields, see the [server schema](/mcp-registry/schema/server-schema.json).
+
+## Schema Validation
+
+All server JSON files are automatically validated against the schema during the CI process. You can also validate your server JSON locally using the prepare.py script:
+
+```bash
+# From the repository root
+python scripts/prepare.py mcp-registry pages --validate-only
+```
+
+## Updating an Existing Server
+
+1. Fork this repository
+2. Update the relevant server JSON file in the `mcp-registry/servers/` directory
+3. Submit a pull request with a clear description of your changes
+
+## Website Development
+
+If you want to contribute to the getmcp.io website itself:
+
+1. Fork and clone the repository
+2. Run the development server:
+
+```bash
+./dev.sh
+```
+
+3. Access the site at http://localhost:4000
+4. Make your changes to the files in the `pages/` directory
+5. Submit a pull request with a clear description of your changes
+
+## Design Guidelines
+
+getmcp.io follows a minimal, clean design philosophy:
+
+- Stick to a minimal black and white color scheme
+- Focus on functionality and readability
+- Follow modern web design patterns
+- Keep UI elements simple and focused on content
+
+## Code of Conduct
+
+Please note that this project is released with a Contributor Code of Conduct. By participating in this project, you agree to abide by its terms.
+
+## License
+
+By contributing to this repository, you agree to license your contributions under the same license as this repository.

DEVELOPMENT.md

@@ -0,0 +1,53 @@
+# Development Guide for getmcp.io
+
+This guide covers how to set up and run the getmcp.io website locally for development.
+
+## Prerequisites
+
+- [Docker](https://www.docker.com/get-started/) (for running Jekyll)
+- [jq](https://stedolan.github.io/jq/download/) (for JSON processing)
+
+## Quick Start
+
+The easiest way to run the site locally is using the included development script:
+
+```bash
+./dev.sh
+```
+
+This script:
+1. Processes server manifests into JSON files
+2. Sets up the proper directory structure
+3. Starts the Jekyll development server
+
+The site will be available at http://localhost:4000 with live reloading enabled.
+
+## Manual Development Setup
+
+If you prefer to run the steps manually:
+
+1. **Process the server manifests** - The automated script handles this for you, but you can examine the script to see how manifests are processed into API endpoints.
+
+2. **Start the Jekyll server**:
+   ```bash
+   cd pages
+   docker run --rm -it -v "$PWD:/srv/jekyll" -p 4000:4000 jekyll/jekyll:4.2.0 jekyll serve --livereload
+   ```
+
+## Making Changes
+
+- **Website Changes**: Edit files in the `/pages` directory
+- **Registry Changes**: Add or modify server manifests in `/mcp-registry/servers/<server-name>/manifest.json`
+
+If you add a new server, run `./dev.sh` again to regenerate the JSON files.
+
+## Testing Production Build
+
+To test the production build that will be deployed to GitHub Pages:
+
+```bash
+cd pages
+docker run --rm -it -v "$PWD:/srv/jekyll" jekyll/jekyll:4.2.0 jekyll build
+```
+
+The built site will be in `pages/_site/`.

README.md

@@ -10,6 +10,7 @@ MCPM aims to simplify the installation, configuration, and management of Model C
 - Centralized management of server configurations across multiple clients
 - Seamless updates for installed servers
 - Server-side management capabilities
+- Registry of available MCP servers
 
 ## Supported MCP Clients
 
@@ -53,22 +54,17 @@ mcpm server status           # Show status of running MCP servers
 mcpm toggle SERVER_NAME      # Toggle an MCP server on or off for a client
 ```
 
-### Coming Soon Commands
+### Registry
 
-The following commands are planned for future releases:
-
-```
-mcpm install SERVER_NAME     # Install an MCP server
-mcpm search [QUERY]          # Search available MCP servers
-mcpm status                  # Show status of MCP servers in Claude Desktop
-```
+The MCP Registry is a central repository of available MCP servers that can be installed using MCPM. The registry is available at [mcpm.sh/registry](https://mcpm.sh/registry).
 
 ## Roadmap
 
 - [x] Landing page setup
 - [x] CLI foundation
 - [x] Search
 - [x] Install
+- [x] Registry integration
 - [ ] Server management functionality
 - [ ] Support SSE Server
 - [ ] Additional client support
@@ -97,6 +93,9 @@ mcpm.sh/
 ├── tests/           # Test directory
 ├── test_cli.py      # Development CLI runner
 ├── pyproject.toml   # Project configuration
+├── pages/           # Website content
+│   └── registry/    # Registry website
+├── mcp-registry/    # MCP Registry data
 └── README.md        # Documentation
 ```
 

dev.sh

@@ -0,0 +1,43 @@
+#!/bin/bash
+
+echo -e "\n📦 Setting up getmcp.io development environment...\n"
+
+# Check if Docker is installed and running
+if ! docker info &> /dev/null; then
+    echo "❌ Docker is required but not running. Please start Docker and try again."
+    exit 1
+fi
+
+# Cleanup previous development files
+echo -e "🗑️ Cleaning up previously generated files...\n"
+rm -rf pages/api/servers
+rm -f pages/api/servers.json
+rm -rf pages/registry/servers
+
+# Create and clean _dev directory
+DEV_DIR="_dev"
+echo -e "🔄 Setting up development directory in $DEV_DIR\n"
+mkdir -p "$DEV_DIR"
+
+# First clear the directory to ensure clean state
+rm -rf "$DEV_DIR"/*
+
+# Copy pages directory structure with all content
+echo -e "🔄 Copying site content to development directory...\n"
+cp -r pages/* "$DEV_DIR"/
+
+# Run the common preparation script
+mkdir -p "$DEV_DIR/registry"
+./scripts/prepare.sh "$DEV_DIR"
+
+echo -e "✅ Setup complete!\n"
+
+echo -e "\n🌐 Starting Jekyll development server..."
+echo "   Access the site at http://localhost:4000"
+echo -e "   Press Ctrl+C to stop the server\n"
+# Start Jekyll dev server using Docker from the _dev directory
+cd "$DEV_DIR" && docker run --rm -it \
+  -v "$PWD:/srv/jekyll" \
+  -p 4000:4000 \
+  jekyll/jekyll:4.2.0 \
+  jekyll serve --livereload || (echo -e "\nPort 4000 is already in use. Assuming development server is already running." && exit 0)