Update documentation about Anthropic MCP registry

Author: strickvl

README.md

@@ -242,3 +242,13 @@ When you drag and drop the `.mcpb` file into Claude Desktop's settings, it autom
 - User-friendly setup process
 
 For more information, see Anthropic's announcement of Desktop Extensions (DXT) and related MCP bundle packaging guidance in their documentation: https://www.anthropic.com/engineering/desktop-extensions
+
+## Published on the Anthropic MCP Registry
+
+This MCP server is published to the official Anthropic MCP Registry and is discoverable by compatible hosts. On each **tagged release**, our CI updates the registry entry via the registry’s `mcp-publisher` CLI using GitHub OIDC, so you can install or discover the **ZenML MCP Server** directly wherever the registry is supported (e.g., Claude Desktop’s Extensions catalog).
+
+- **Always up to date:** the registry entry is refreshed with every release from the tagged commit’s `manifest.json` and `server.json`.
+- **Alternate install paths:** you can still install locally via the packaged `.mcpb` bundle (see above) or run the Docker image.
+
+Learn more about the registry here:
+- Anthropic MCP Registry (community repo): https://github.com/modelcontextprotocol/registry

RELEASE.md

@@ -1,6 +1,6 @@
 # Release Process
 
-This repository ships releases via a single "Release Orchestrator" GitHub Actions workflow. It treats the root `VERSION` file as the single source of truth, auto-updates related files, builds the MCP bundle (`mcp-zenml.mcpb`), creates a tag and GitHub Release, and triggers downstream publishers.
+This repository ships releases via a single "Release Orchestrator" GitHub Actions workflow. It treats the root `VERSION` file as the single source of truth, auto-updates related files, builds the MCP bundle (`mcp-zenml.mcpb`), creates a tag and GitHub Release, and triggers downstream publishers, including publishing to the official Anthropic MCP Registry.
 
 ## Quick Start
 
@@ -55,7 +55,7 @@ A weekly cron (Monday 09:00 UTC) also triggers the workflow as a reminder, but i
   - Builds and pushes versioned Docker images:
     - `zenmldocker/mcp-zenml:vX.Y.Z`
   - Uploads/attaches `mcp-zenml.mcpb` to the corresponding GitHub Release.
-  - If configured, publishes to the MCP Registry based on `manifest.json`/`server.json`.
+  - Publishes to the **Anthropic MCP Registry** using the `mcp-publisher` CLI with GitHub OIDC (no static secrets). The registry entry is updated from the tagged commit's `manifest.json` and `server.json`.
 
 ## Manual Recovery
 
@@ -81,8 +81,8 @@ If something goes wrong:
 - Docker Images
   - `zenmldocker/mcp-zenml:latest` (main)
   - `zenmldocker/mcp-zenml:vX.Y.Z` (tag)
-- MCP Registry (if enabled)
-  - Publishes based on `manifest.json`/`server.json` from the tagged commit
+- Anthropic MCP Registry
+  - Registry entry updated on every tagged release (derived from `manifest.json` / `server.json`)
 
 ## Notes