# Reported issues for zola-mcp Pod holds 8 of 8 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user. Back to [zola-mcp](/mcp/zola-mcp). ## Most discussed ### Auto-review follow-ups for PR #188: feat: add zola_healthcheck Tracking auto-review follow-ups for #188 (verdict: **fail**). ### 🔴 Important - [ ] src/tools/healthcheck.ts:23 — hostLabel 'api.zola.com' doesn't match the actual probed host mobile-api.zola.com (per client.ts MOBILE_BASE_URL and CLAUDE.md/README.md), undermining the tool's purpose of identifying which hop failed ### 🟡 Nits - [ ] src/client.ts:211-226 — pre-existing JSDoc for requestMobile() now sits above the newly-inserted describeCredential() instead o [Read the thread](https://github.com/chrischall/zola-mcp/issues/189) · 2026-08-30 · closed · outside contributor · 1 comment ### Auto-review follow-ups for PR #183: feat(auth): cache the bootstrapped refresh token so hosted cold starts need no browser Tracking auto-review follow-ups for #183 (verdict: **warn**). ### 🟡 Nits - [ ] Stale 4xx/5xx comments contradict CREDENTIAL_REJECTION_STATUS: update src/client.ts:16-17, src/client.ts:433-436, CLAUDE.md:84 (and the three-path header comment in tests/auth.test.ts:6-9) to name 400/401/422 and say 403/429 are treated as transient --- Checklist regenerated from the auto-review of `afe7edb` ([run](https://github.com/chrischall/zola-mcp/actions/runs/33276110794) [Read the thread](https://github.com/chrischall/zola-mcp/issues/184) · 2026-08-29 · closed · outside contributor · 1 comment ### Auto-review follow-ups for PR #171: chore: list mint.yaml in the manifest inventory Tracking auto-review follow-ups for #171 (verdict: **warn**). ### 🟡 Nits - [ ] Inconsistent formatting in mint.yaml entry (line 83): uses bullet prefix, backticks, and em-dash separator unlike other root-level entries --- Checklist regenerated from the auto-review of `65e5567` ([run](https://github.com/chrischall/zola-mcp/actions/runs/32910348953)). Ticks survive later rounds, but a round that reviewed an older commit can still re-list something already fi [Read the thread](https://github.com/chrischall/zola-mcp/issues/172) · 2026-08-25 · closed · outside contributor · 0 comments ### Auto-review follow-ups for PR #161: ci: sync the ci,release-please stub(s) from chrischall/workflows Tracking auto-review follow-ups for #161 (verdict: **warn**). ### 🟡 Nits - [ ] release-please.yml: Removed explanatory comment about skill-path parameter necessity and multi-skill context (lines 55-62 in original) --- When addressing the review on #161, resolve each item and add `Closes #` to the PR once everything is genuinely fixed; deferred items stay open here. See the auto-review follow-up convention in CLAUDE.md. [Read the thread](https://github.com/chrischall/zola-mcp/issues/162) · 2026-08-11 · closed · outside contributor · 0 comments ### Auto-review follow-ups for PR #155: refactor(connector): retire the standalone Cloudflare Worker connector Tracking auto-review follow-ups for #155 (verdict: **warn**). ### 🟡 Nits - [ ] src/client.ts lines 108 and 136 still reference the deleted src/worker.ts — reword both comments to describe the durable property (non-Node runtime restrictions; per-user injected refresh-token resolver) instead of naming the retired Worker --- When addressing the review on #155, resolve each item and add `Closes #` to the PR once everything is genuinely fixed; defer [Read the thread](https://github.com/chrischall/zola-mcp/issues/156) · 2026-08-06 · closed · outside contributor · 1 comment ### Auto-review follow-ups for PR #135: feat(registry): make registry reads work and expose per-item purchase state Tracking auto-review follow-ups for #135 (verdict: **warn**). ### 🟡 Nits - [x] tests/reconcile-registry.test.ts:282 — `expect(reconcileRegistry.length).toBe(1)` is a hollow guard: Function.length excludes defaulted parameters, so the removed `(client, args = {})` signature also had length 1 and would pass; replace with a spy on fetchRegistryCollection's limit/offset or a synthetic collection larger than any page cap - [x] src/registry-collection.ts:267 — fo [Read the thread](https://github.com/chrischall/zola-mcp/issues/138) · 2026-08-01 · closed · outside contributor · 0 comments ### Auto-review follow-ups for PR #128: ci: convert to chrischall/workflows reusable pipeline Tracking auto-review follow-ups for #128 (verdict: **fail**). ### 🔴 Important - [ ] ci.yml drops `npm run worker:test` from the CI test-command, leaving tests/worker.test.ts (covering src/worker.ts) completely unexercised in CI - [ ] release-please.yml removes the `skill-path: skills/zola/SKILL.md` input to mcp-publish despite both skills/zola and skills/zola-api still existing — the exact condition that silently broke releases 1.6.0, 1.6.1, and 1.6.2 per t [Read the thread](https://github.com/chrischall/zola-mcp/issues/129) · 2026-07-27 · closed · outside contributor · 1 comment ### Auto-review follow-ups for PR #100: feat(skill): add zola api access skill Tracking auto-review follow-ups for #100 (verdict: **warn**). ### 🟡 Nits - [ ] references/mobile-api-endpoints.md intro lists $ACCT and $REG but the website-settings recipe uses an undocumented third variable $WEDDING_ID (defined only in SKILL.md) — add it to the reference's variable list --- When addressing the review on #100, resolve each item and add `Closes #` to the PR once everything is genuinely fixed; deferred items stay open here. See [Read the thread](https://github.com/chrischall/zola-mcp/issues/101) · 2026-07-13 · closed · outside contributor · 0 comments ## Most recent The remaining reports are on [the project's issue tracker](https://github.com/chrischall/zola-mcp/issues).