Skip to content

docs: fix broken README badges and install buttons (DeepWiki, VS Code, add Cursor) - #829

Merged
zereight merged 2 commits into
mainfrom
docs/fix-readme-badges
Oct 12, 2026
Merged

zereight merged 2 commits into
mainfrom
docs/fix-readme-badges

Conversation

@zereight

Copy link
Copy Markdown
Owner

What was broken

  1. DeepWiki badge (README.md) — https://deepwiki.com/badge.svg now returns HTTP 429 text/html (a Vercel protection page) instead of an SVG, and GitHub's camo proxy returns 502, so the badge rendered as a broken image.
  2. VS Code install badge (all 4 READMEs + docs/clients/vscode.md) — it linked to vscode:mcp/install?.... GitHub strips non-http(s) links, so on github.com the badge only opened its own camo image and never launched VS Code.

Fix

  • DeepWiki: image replaced with a static shields.io badge (https://img.shields.io/badge/DeepWiki-Ask-blue). Link to https://deepwiki.com/zereight/gitlab-mcp unchanged.
  • VS Code: switched to the https redirect https://vscode.dev/redirect/mcp/install?name=zereight.gitlab-mcp&config=..., the same form used by github/github-mcp-server and atlassian/atlassian-mcp-server. The install payload is unchanged (npx -y @zereight/mcp-gitlab@latest, ${input:gitlab-token}, GITLAB_API_URL, GITLAB_PERMISSION_MODE=full).
  • New: Cursor one-click install button next to the VS Code badge (all 4 READMEs + docs/clients/cursor.md), using Cursor's official web install link https://cursor.com/en/install-mcp?name=...&config=<base64> with the official mcp-install-dark.svg button. Same server config, except the token is ${env:GITLAB_PERSONAL_ACCESS_TOKEN}: Cursor only supports ${env:...}, ${userHome}, ${workspaceFolder} interpolation, not VS Code's ${input:...}. docs/clients/cursor.md has a one-line note about this.
  • scripts/generate-vscode-install-link.mjs now generates both badges. README/docs badge lines are byte-identical to its output.

Verification

  • curl on the new image URLs: img.shields.io/badge/DeepWiki-Ask-blue → 200 image/svg+xml, cursor.com/deeplink/mcp-install-dark.svg → 200 image/svg+xml.
  • vscode.dev/redirect/mcp/install?... → 302 to vscode:mcp/install?{...same config..., "name":"zereight.gitlab-mcp"}.
  • Cursor link → 200 install page. Base64 config decodes to the intended JSON.
  • All other badges (shields.io, MCP Toplist, mcpindex) and local images (assets/star-history.png, docs/img/step *.png) checked OK, both directly and through the camo URLs on the rendered README. Left unchanged.
  • npm run check:skill-sync passes. mkdocs build --strict passes.

zereight and others added 2 commits October 12, 2026 09:52
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@coderabbitai

coderabbitai Bot commented Oct 12, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 83b5fccb-508a-48ec-89f6-5e55071a8b46

📥 Commits

Reviewing files that changed from the base of the PR and between b4f3e1e and 6e120d9.


📒 Files selected for processing (7)
  • README.ko.md
  • README.md
  • README.pt-BR.md
  • README.zh-CN.md
  • docs/clients/cursor.md
  • docs/clients/vscode.md
  • scripts/generate-vscode-install-link.mjs

Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review.


📜 Recent review details
⏰ Context from checks skipped due to timeout. (9)
  • GitHub Check: integration-test
  • GitHub Check: test
  • GitHub Check: docs-build
  • GitHub Check: schema-tests
  • GitHub Check: code-quality
  • GitHub Check: Analyze (actions)
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: Analyze (python)
  • GitHub Check: Analyze (ruby)

🔇 Additional comments (7)
scripts/generate-vscode-install-link.mjs (1)

2-2: LGTM!

Also applies to: 4-6, 8-8, 11-11, 13-24, 26-27, 29-29, 31-33, 35-36, 38-39, 41-42, 44-46


docs/clients/vscode.md (1)

7-7: LGTM!

Also applies to: 9-9


docs/clients/cursor.md (1)

5-7: LGTM!


README.md (1)

7-9: LGTM!


README.ko.md (1)

4-5: LGTM!


README.pt-BR.md (1)

4-5: LGTM!


README.zh-CN.md (1)

4-5: LGTM!



📝 Summary

Summary by CodeRabbit

  • Documentation
    • Added one-click installation options for Cursor, with the GitLab server settings preconfigured.
    • Updated VS Code install links to use a web redirect that works from GitHub.
    • Clarified how to adjust the GitLab token after installing in Cursor.
    • Updated the DeepWiki badge display.

Walkthrough

The install-link generator now produces links and badges for VS Code and Cursor. Client guides and localized READMEs use the updated installation links. The English README also changes the DeepWiki badge image URL.

Changes

Client installation links

Layer / File(s) Summary
Generate client links
scripts/generate-vscode-install-link.mjs
The script builds shared server configuration, creates client-specific install URLs, and outputs URLs and badges for VS Code and Cursor.
Document client installation
docs/clients/vscode.md, docs/clients/cursor.md, README.md, README.ko.md, README.pt-BR.md, README.zh-CN.md
The client guides and localized READMEs use the VS Code redirect URL and add Cursor installation links. The English README also changes the DeepWiki badge image URL.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other


Merge Risk: ⚪ Minimal · up to 6e120

The changes update client installation links and badges, with no concrete breakage established in the reviewed context. The PR appears mergeable subject to normal checks.

Pre-merge checks | Passed 4 | Failed 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files. (6 skipped: 6 … Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check Passed The title clearly identifies the broken README badges and install buttons, including DeepWiki, VS Code, and Cursor.
Description check Passed The description directly explains the badge fixes, VS Code redirect change, Cursor button addition, implementation details, and verification results.
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files. (6 skipped: 6 unsupported.)


  • Fix all pre-merge checks with AI
✨ Finishing Touches 💡 1
📝 Generate docstrings 💡
  • Commit to this branch
  • Create a new PR


🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR

✨ Simplify code
  • Commit to this branch
  • Create a new PR

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@zereight
zereight merged commit 13d837d into main Oct 12, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant