# Reported issues for vibo-mcp

Pod holds 6 of 6 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 [vibo-mcp](/mcp/vibo-mcp).

## Most discussed

### Auto-review follow-ups for PR #70: refactor(connector): retire the standalone Cloudflare Worker connector

<!-- auto-review-followup:PR-70 -->

Tracking auto-review follow-ups for #70 (verdict: **warn**).

### 🟡 Nits
- [ ] src/tools/session.ts:8-11 — comment left mid-edit reads 'NOT wired into the / a remote caller' and still names the retired 'serverless Worker runtime'
- [ ] src/tools/uploads.ts:9-14 — registerUploadTools JSDoc is a broken fragment: first sentence stops at 'while the hosted' before a new capitalised sentence starts
- [ ] tests/upload-source.test.ts — deleting the inlineUploadResolv

[Read the thread](https://github.com/chrischall/vibo-mcp/issues/71) · 2026-08-06 · closed · external user · 0 comments

### Auto-review follow-ups for PR #44: fix(deps): lift @chrischall/mcp-connector to 1.1.1

<!-- auto-review-followup:PR-44 -->

Tracking auto-review follow-ups for #44 (verdict: **fail**).

### 🔴 Important
- [ ] Commit prefix build(deps): violates first-party dependency bump convention (CLAUDE.md 188–189); should be fix: or feat: with matching bug/enhancement labels to ensure deploy-connector runs

---
When addressing the review on #44, resolve each item and add `Closes #<this issue>` to the PR once everything is genuinely fixed; deferred items stay open here. See the auto-review foll

[Read the thread](https://github.com/chrischall/vibo-mcp/issues/45) · 2026-07-26 · closed · external user · 0 comments

### Auto-review follow-ups for PR #36: ci: deploy the connector Worker on release

<!-- auto-review-followup:PR-36 -->

Tracking auto-review follow-ups for #36 (verdict: **warn**).

### 🟡 Nits
- [x] docs/DEPLOY-CONNECTOR.md still states "there is no CI/CD path" for the connector deploy, which this PR contradicts by adding one

---
When addressing the review on #36, resolve each item and add `Closes #<this issue>` 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/vibo-mcp/issues/37) · 2026-07-20 · closed · external user · 0 comments

### Auto-review follow-ups for PR #29: feat: add hosted Cloudflare Worker connector (password accounts)

<!-- auto-review-followup:PR-29 -->

Tracking auto-review follow-ups for #29 (verdict: **warn**).

### 🟡 Nits
- [ ] src/worker.ts is excluded from tsc and never statically type-checked (worker:test runs via esbuild/Miniflare which strips types); add a dedicated tsc --noEmit over the Worker entry with @cloudflare/workers-types

---
When addressing the review on #29, resolve each item and add `Closes #<this issue>` to the PR once everything is genuinely fixed; deferred items stay open here. See th

[Read the thread](https://github.com/chrischall/vibo-mcp/issues/30) · 2026-07-14 · closed · external user · 0 comments

### Auto-review follow-ups for PR #9: feat: SSO browser token auto-capture (fetchproxy) + docs polish

<!-- auto-review-followup:PR-9 -->

Tracking auto-review follow-ups for #9 (verdict: **warn**).

### 🟡 Nits
- [x] src/auth.ts:82 — saveSession() persists the captured token before GET_ME confirms it authenticates
- [x] src/tools/session.ts:17 — captureViboSession() + client.setTokens() double-save session.json
- [x] src/session-store.ts:40 — writeFileSync({ mode: 0o600 }) only applies on file creation; add chmodSync after write

---
When addressing the review on #9, resolve each item and add `Cl

[Read the thread](https://github.com/chrischall/vibo-mcp/issues/10) · 2026-06-16 · closed · external user · 0 comments

### Auto-review follow-ups for PR #5: feat: v2/v3 tools — song management, comments, song ideas, imports, collaboration, section edits, uploads

<!-- auto-review-followup:PR-5 -->

Tracking auto-review follow-ups for #5 (verdict: **warn**).

### 🟡 Nits
- [x] No unit tests for client.gqlUpload/postMultipart, vibo_set_profile_photo, or the imagePaths/filePaths branch of vibo_answer_question — PR body's 'Writes are unit-tested' claim has uploads as an exception
- [x] vibo_list_event_users in src/tools/collaboration.ts applies `limit`/`skip` per-group when `usersType` is omitted (callers can get up to 2×limit entries); description should not

[Read the thread](https://github.com/chrischall/vibo-mcp/issues/6) · 2026-06-16 · closed · external user · 0 comments

## Most recent

The remaining reports are on [the project's issue tracker](https://github.com/chrischall/vibo-mcp/issues).