Skip to content

feat(mcp): add windsurf host to init-client config - #2664

Closed
glorydavid03023 wants to merge 1 commit into
JSONbored:mainfrom
glorydavid03023:feat/mcp-windsurf-host
Closed

feat(mcp): add windsurf host to init-client config#2664
glorydavid03023 wants to merge 1 commit into
JSONbored:mainfrom
glorydavid03023:feat/mcp-windsurf-host

Conversation

@glorydavid03023

Copy link
Copy Markdown
Contributor

Summary

Adds windsurf to gittensory-mcp init-client --print, so Windsurf users can generate their MCP config like the other supported hosts.

Windsurf reads ~/.codeium/windsurf/mcp_config.json using the same shared mcpServers JSON shape as claude / cursor / mcp, so it reuses that snippet branch (no new snippet, unlike vscode's servers / "type": "stdio" shape).

$ gittensory-mcp init-client --print windsurf
{ "mcpServers": { "gittensory": { "command": "gittensory-mcp", "args": ["--stdio"] } } }

Mirrors the merged vscode host addition (#1770): CLI usage text, the empty-client and unsupported-client error messages, the README example + host description, and — for docs parity — the public MCP-clients docs page (docs.mcp-clients.tsx) generate-config command list. A test asserts the windsurf snippet equals the shared mcpServers snippet.

No issue because issue creation is restricted on this repo for outside accounts; this is a small additive host with no schema or API change.

Scope

  • Conventional Commit title; focused; follows CONTRIBUTING; small self-evident change (no linked issue).

Validation

  • git diff --check
  • npm run typecheck
  • npm run build:mcp (node --check clean)
  • npm run ui:typecheck (clean)
  • npm run test:coverage (scoped: test/unit/mcp-cli-basics.test.ts — 20 pass, incl. the added windsurf snippet assertion; CLI exercised by spawning init-client --print windsurf)
  • npm run test:mcp-pack / ui:lint / ui:build (see note)
  • npm audit --audit-level=moderate
  • New/changed behavior has tests

If any required check was skipped, explain why:

  • MCP package CLI/README/test + a one-line addition to the docs.mcp-clients.tsx generate-config command list. build:mcp and ui:typecheck pass; prettier --check on the changed docs file passes; mcp-cli-basics.test.ts passes (20). The MCP-package JS is outside Codecov's src/**/*.ts include (no patch-coverage obligation). I could not run test:mcp-pack locally (Node 24 vs the repo's pinned Node 22 — check-mcp-package.mjs throws ERR_INVALID_ARG_TYPE, identically on unmodified main), and ui:lint/ui:build are dominated by pre-existing CRLF noise on this Windows checkout (core.autocrlf); CI runs both on a clean LF, pinned-Node checkout.

Safety

  • No secrets/wallets/hotkeys/trust/reward/private terms exposed.
  • Public GitHub text stays sanitized and low-noise.
  • Auth/cookie/CORS/session negative-path tests. — N/A.
  • API/OpenAPI/MCP behavior updated/tested where needed. (Additive CLI host + docs parity; covered by the added test. No request/response schema changed.)
  • UI changes use live API data. — N/A: static docs command-list line.
  • UI Evidence. — N/A: the only UI change is one text line added to an existing bash code-block on the docs page (no visual/layout change), so a screenshot adds nothing.
  • Docs/changelog updated where needed. (README + MCP-clients docs updated; changelogs are release-prep artifacts.)

Notes

  • This is the complete follow-up to a prior attempt that was closed for missing docs parity: the docs.mcp-clients.tsx generate-config list now includes windsurf alongside codex/claude/cursor/mcp.

Add `windsurf` to `gittensory-mcp init-client --print`. Windsurf reads
~/.codeium/windsurf/mcp_config.json using the same shared `mcpServers` JSON
shape as claude/cursor/mcp, so it reuses that snippet branch (unlike vscode's
`servers`/`type` shape).

Updates the CLI usage text, the empty-client and unsupported-client error
messages, the README example + host description, and the public MCP-clients docs
page (docs.mcp-clients.tsx) generate-config command list so the docs match the
new CLI surface. A test asserts the windsurf snippet equals the shared
mcpServers snippet.

No issue because issue creation is restricted on this repo; this is a small
additive host mirroring the vscode host addition (JSONbored#1770), no schema/API change.
@dosubot dosubot Bot added the size:XS label Jul 3, 2026
@loopover-orb

loopover-orb Bot commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

Warning

🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨

⏸️ Gittensory review result - manual review recommended

Review updated: 2026-07-03 02:36:10 UTC

4 files · 1 AI reviewer · no blockers · readiness 80/100 · CI green · clean

⏸️ Suggested Action - Manual Review

Review summary
This change cleanly adds `windsurf` as another `init-client --print` target and routes it through the existing shared `mcpServers` JSON snippet, which matches the documented Windsurf config shape. The CLI usage, empty-client error, unsupported-client error, README, docs command list, and unit coverage are updated consistently enough for the functional path. The only notable gap is documentation depth on the docs page: it lists the command but does not tell users the Windsurf config filename there.

Nits — 4 non-blocking
  • nit: apps/gittensory-ui/src/routes/docs.mcp-clients.tsx:43 adds the Windsurf command, but the adjacent explanatory paragraph still names only Claude Desktop and Cursor for the shared `mcpServers` shape.
  • nit: apps/gittensory-ui/src/routes/docs.mcp-clients.tsx:43 does not include the Windsurf target file path, while packages/gittensory-mcp/README.md:160 does, so the public docs page is less useful than the package README.
  • apps/gittensory-ui/src/routes/docs.mcp-clients.tsx:48 should mention Windsurf in the shared-shape sentence and include `~/.codeium/windsurf/mcp_config.json` for parity with packages/gittensory-mcp/README.md:160.
  • test/unit/mcp-cli-basics.test.ts:31 could also assert the unsupported-client message includes `windsurf`, since the PR updates that user-facing contract in packages/gittensory-mcp/bin/gittensory-mcp.js:2837.
Signal Result Evidence
Code review ✅ No blockers 1 reviewer
Linked issue ✅ No-issue rationale PR body explains why no issue is linked.
Related work ✅ No active overlap found No same-issue or scoped active PR overlap found.
Change scope ✅ 20/20 Low review scope from cached public metadata (size label size:XS; no linked issue context).
Validation posture ❌ 5/25 Preflight is holding this PR: the review lane is unavailable, so it is not ready for automated review.
Contributor workload ✅ 10/10 Author activity: 224 registered-repo PR(s), 143 merged, 11 issue(s).
Contributor context ✅ Confirmed Gittensor contributor glorydavid03023; Gittensor profile; 224 PR(s), 11 issue(s).
Gate result ✅ Passing No configured blocker found.
Review context
  • Author: glorydavid03023
  • Role context: outside_contributor
  • Public audience mode: oss maintainer
  • Lane context: Repository registration is not available in the local Gittensory cache.
  • Public profile languages: not available
  • Official Gittensor activity: 224 PR(s), 11 issue(s).
  • PR-specific overlap: none found.
Contributor next steps
  • Await review-lane availability.
  • Refresh registry data or choose a registered active repo.
  • Link the issue being solved, or explicitly explain why this is a no-issue PR.
Signal definitions
  • Related work = same linked issue, overlapping active PRs, or title/path similarity.
  • Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
  • Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
  • Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
  • Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed


💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers.

  • Re-run Gittensory review

@loopover-orb loopover-orb Bot added gittensor gittensor:feature Gittensor-scored feature linked to a feature issue — scores a 0.25x multiplier. labels Jul 3, 2026
@codecov

codecov Bot commented Jul 3, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.10%. Comparing base (066398e) to head (54f0ac8).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2664   +/-   ##
=======================================
  Coverage   96.10%   96.10%           
=======================================
  Files         237      237           
  Lines       26540    26540           
  Branches     9625     9625           
=======================================
  Hits        25507    25507           
  Misses        424      424           
  Partials      609      609           
🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@JSONbored JSONbored left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please fix:

The only notable gap is documentation depth on the docs page: it lists the command but does not tell users the Windsurf config filename there.

@JSONbored JSONbored closed this Jul 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gittensor:feature Gittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants