Refresh GitHub MCP Registry catalog independently of repo changes

.github/workflows/catalog.yml

@@ -11,8 +11,14 @@ on:
   push:
     branches:
       - main
+  schedule:
+    - cron: "17 * * * *"
   workflow_dispatch:
 
+concurrency:
+  group: catalog-${{ github.ref }}
+  cancel-in-progress: false
+
 permissions:
   actions: write
   contents: write
@@ -43,8 +49,8 @@ jobs:
           if gh workflow view catalog.yml >/dev/null 2>&1; then
             gh workflow run catalog.yml --ref "$HEAD_REF"
           fi
-      - name: Open fallback pull request
-        if: github.event_name == 'push' && github.ref == 'refs/heads/main'
+      - name: Open catalog refresh pull request
+        if: (github.event_name == 'push' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch') && github.ref == 'refs/heads/main'
         env:
           GH_TOKEN: ${{ github.token }}
         run: |
@@ -61,6 +67,6 @@ jobs:
               --base main \
               --head "$branch" \
               --title "Update generated ARD catalog" \
-              --body "Regenerates \`ai-catalog.json\` from the canonical entries and live MCP catalog."
+              --body "Regenerates \`ai-catalog.json\` from the canonical entries and the live GitHub MCP Registry catalog."
           fi
           gh workflow run catalog.yml --ref "$branch"

CONTRIBUTING.md

@@ -93,7 +93,7 @@ python3 scripts/generate_ai_catalog.py --check
 
 Files under `catalog/<publisher>/` remain the source of truth for contributor-managed entries. The root `ai-catalog.json` is generated for ARD ingestion, supplemented with missing entries from GitHub's public MCP catalog, and should not be edited by hand.
 
-The pull request workflow regenerates `ai-catalog.json` automatically for branches in this repository. Fork workflows validate the catalog but cannot push changes; the main-branch fallback opens a follow-up pull request if regeneration is needed after merge.
+The pull request workflow regenerates `ai-catalog.json` automatically for branches in this repository. Fork workflows validate the catalog but cannot push changes; the main-branch fallback opens a follow-up pull request if regeneration is needed after merge. Hourly scheduled runs and manual runs on `main` also open or update that same refresh pull request for GitHub MCP Registry changes, even when no contributor files have changed. Manual runs on other branches regenerate and validate only, so the refresh branch's validation does not recursively publish another pull request.
 
 ### 5. Open a pull request
 

README.md

@@ -28,6 +28,8 @@ Each augment is a single JSON file under the publisher's directory. The publishe
 
 These per-entry files are the source of truth for contributor-managed entries. The root `ai-catalog.json` is a generated Agentic Resource Discovery (ARD) ingestion artifact that also includes missing entries from GitHub's public MCP catalog. Do not edit it by hand; regenerate it with `python3 scripts/generate_ai_catalog.py`.
 
+The Catalog workflow checks the [GitHub MCP Registry](https://api.mcp.github.com/.well-known/ai-catalog.json) hourly, independently of repository changes, and opens or updates the `automation/update-ai-catalog` pull request when the generated catalog changes. This refresh picks up registry additions and current server-version references; it does not query the general public MCP registry. Refresh changes still require the pull request to be merged before they reach the main-branch catalog. GitHub Actions schedules can be delayed, and a manual workflow run on `main` uses the same publication flow.
+
 ## Contributing
 
 Want to list your skill or MCP server in the catalog? See **[CONTRIBUTING.md](CONTRIBUTING.md)** for the full guide, including the JSON schema, validation steps, and PR process.