diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 15f920f3d..59b4e9d5d 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -16,6 +16,8 @@ env: GO_VERSION: "1.27.0" IMAGE: ghcr.io/labstack/fanout DOCKERHUB_IMAGE: docker.io/labstack/fanout + MCP_PUBLISHER_VERSION: "1.8.1" + MCP_PUBLISHER_LINUX_AMD64_SHA256: "a06c9096dcb9727c13555b6be26c7effa707b01f06a4c561ba7a3635443cf2cc" jobs: verify: @@ -347,3 +349,33 @@ jobs: curl -fsSLO "${base}/${archive}" gh attestation verify "${archive}" --repo labstack/fanout done + + mcp-registry: + name: publish MCP Registry metadata + needs: verify-release + runs-on: ubuntu-24.04 + permissions: + contents: read + id-token: write + steps: + - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 + - name: Set the released version + run: | + set -euo pipefail + version="${GITHUB_REF_NAME#v}" + jq --arg version "${version}" '.version = $version' server.json > server.tmp + mv server.tmp server.json + - name: Install the MCP publisher + run: | + set -euo pipefail + archive="mcp-publisher_linux_amd64.tar.gz" + url="https://github.com/modelcontextprotocol/registry/releases/download/v${MCP_PUBLISHER_VERSION}/${archive}" + curl -fsSLo "${archive}" "${url}" + echo "${MCP_PUBLISHER_LINUX_AMD64_SHA256} ${archive}" | sha256sum -c - + tar -xzf "${archive}" mcp-publisher + - name: Validate MCP Registry metadata + run: ./mcp-publisher validate + - name: Authenticate to the MCP Registry + run: ./mcp-publisher login github-oidc + - name: Publish to the MCP Registry + run: ./mcp-publisher publish diff --git a/docs/release.md b/docs/release.md index 2acbb70b9..f08bc1d33 100644 --- a/docs/release.md +++ b/docs/release.md @@ -7,6 +7,7 @@ Fanout publishes one release from a verified commit on `main`. A release contain multi-architecture images; - byte-identical `labstack/fanout:` and `latest` Docker Hub mirrors; - SHA-256 checksums and GitHub build-provenance attestations for every archive; +- an `io.github.labstack/fanout` entry in the official MCP Registry; - the Apache-2.0 license, project notice, trademark policy, and generated third-party notices in every archive and container image. @@ -39,7 +40,9 @@ copies that accepted manifest to Docker Hub; requires the registry digests to match; and creates the GitHub release only after anonymous pulls from both GHCR and Docker Hub succeed. A final job downloads every release asset without credentials, verifies checksums, inspects the legal payload, exercises the -installer, and verifies provenance. +installer, and verifies provenance. Only after those checks pass does the +workflow publish the release's `server.json` to the MCP Registry with GitHub +OIDC; no long-lived registry credential is stored in the repository. Fanout does not currently use GoReleaser. DuckDB requires CGO and the supported targets are built on four native runners. GoReleaser's supported split-and-merge diff --git a/server.json b/server.json new file mode 100644 index 000000000..4c008ac00 --- /dev/null +++ b/server.json @@ -0,0 +1,31 @@ +{ + "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json", + "name": "io.github.labstack/fanout", + "title": "Fanout", + "description": "Investigate OpenTelemetry traces, metrics, and logs, and manage personal dashboards.", + "websiteUrl": "https://fanout.run", + "icons": [ + { + "src": "https://fanout.run/favicon.svg", + "mimeType": "image/svg+xml" + } + ], + "repository": { + "url": "https://github.com/labstack/fanout", + "source": "github" + }, + "version": "2026.9.0", + "remotes": [ + { + "type": "streamable-http", + "url": "https://{host}/mcp", + "variables": { + "host": { + "description": "Public hostname of your Fanout instance, without a scheme or path.", + "isRequired": true, + "placeholder": "fanout.example.com" + } + } + } + ] +}