diff --git a/.changesets/1793967022-96a857a7.yaml b/.changesets/1793967022-96a857a7.yaml new file mode 100644 index 000000000..9bb8f8ef4 --- /dev/null +++ b/.changesets/1793967022-96a857a7.yaml @@ -0,0 +1,10 @@ +id: 1793967022-96a857a7 +features: + - mcpServer +targets: + - mcp-typescript +type: feat +bump: patch +description: document http auth for MCP Registry publishing in the generated README +author: AshGodfrey +date: "2026-11-06" diff --git a/templates/templates/mcp-typescript/readme.stmpl b/templates/templates/mcp-typescript/readme.stmpl index eae70ae7b..039dc8501 100644 --- a/templates/templates/mcp-typescript/readme.stmpl +++ b/templates/templates/mcp-typescript/readme.stmpl @@ -86,6 +86,7 @@ targets: The `github-oidc` method uses GitHub Actions OIDC — no secrets required. For other auth methods: - `github` — requires a `MCP_REGISTRY_TOKEN` secret (GitHub PAT with `read:org` + `read:user` scopes) - `dns` — requires a `MCP_REGISTRY_TOKEN` secret (Ed25519 private key for custom domain namespaces) +- `http` — requires a `MCP_REGISTRY_TOKEN` secret (Ed25519 private key for custom domain namespaces verified by a `/.well-known/mcp-registry-auth` file, which must be served without redirects) When the Speakeasy workflow runs, it will automatically publish to npm first, then to the MCP Registry. diff --git a/zSDKs/mcp-typescript/README.md b/zSDKs/mcp-typescript/README.md index bf903005d..134a6b174 100644 --- a/zSDKs/mcp-typescript/README.md +++ b/zSDKs/mcp-typescript/README.md @@ -403,6 +403,7 @@ targets: The `github-oidc` method uses GitHub Actions OIDC — no secrets required. For other auth methods: - `github` — requires a `MCP_REGISTRY_TOKEN` secret (GitHub PAT with `read:org` + `read:user` scopes) - `dns` — requires a `MCP_REGISTRY_TOKEN` secret (Ed25519 private key for custom domain namespaces) +- `http` — requires a `MCP_REGISTRY_TOKEN` secret (Ed25519 private key for custom domain namespaces verified by a `/.well-known/mcp-registry-auth` file, which must be served without redirects) When the Speakeasy workflow runs, it will automatically publish to npm first, then to the MCP Registry.