Why

The manual "Publish to MCP Registry" run on 2026-09-28 failed at Login to MCP Registry with:

401 Unauthorized: failed to validate OIDC token: invalid audience: expected https://registry.modelcontextprotocol.io, got [mcp-registry]

Run: https://github.com/browserstack/mcp-server/actions/runs/36403198556

Two problems:

1. Stale publisher pin. The workflow pins mcp-publisher v1.3.3, which requests the old mcp-registry OIDC audience. Registry v1.7.6 (2026-04-30) bound the token exchange to the deployment audience, so any pre-1.7.6 binary fails. The registry docs' troubleshooting table lists this exact error with the fix "your binary is too old".
2. Tag trigger never fires. The registry workflow triggers on v* tags, but the release workflow pushes that tag with GITHUB_TOKEN, and GitHub does not create workflow runs from events produced by that token. Only manual dispatches have ever run it. Our official registry entry has been stuck at 1.2.7 since 2025-10-28, which is why BrowserStack is missing from the GitHub MCP Registry and the VS Code / Copilot MCP gallery (GitHub's sync only started mirroring OSS entries in December 2025).

What

• mcp-registry-publish.yml: bump pin to v1.8.1 with the linux_amd64 sha256 from registry_1.8.1_checksums.txt (verified against a fresh download).
• npm-publish.yml: add actions: write and a final step that runs gh workflow run mcp-registry-publish.yml --ref v<version>. workflow_dispatch is exempt from the GITHUB_TOKEN restriction, so every release now also publishes to the registry.

After merge

Re-run Publish to MCP Registry once via workflow_dispatch on main to publish 1.5.0. Then check https://github.com/mcp for BrowserStack after GitHub's next sync.

🤖 Generated with Claude Code