Directory listings and one-click install badges (VS Code, Cursor, Smithery, Glama, awesome-mcp-servers)

未關閉
#178 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
2/5
預估耗時
半天
新手友好度
40/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
json, markdown, typescript, vscode

研究方向

The badges should be generated from the same MCP config JSON that the README already uses, so start by finding that config and the README install section. Build the vscode:mcp/install?... and Cursor deeplinks from it, then test them in VS Code and Cursor on Windows. The directory submissions (Glama, Smithery, PulseMCP, mcpservers.org, awesome-mcp-servers) are external and need a maintainer's account, so a newcomer should expect to coordinate on those parts. Done means working badges and listings in at least four directories, plus a merged awesome-list PR.

由索引模型根據 Issue 內容生成。

描述

effort: small impact: medium marketing

What / who: Add "Install in VS Code" / "Install in VS Code Insiders" badges (vscode:mcp/install?... deeplinks, VS Code MCP docs) and a Cursor install deeplink (Cursor MCP docs) to the README and connect page. List the server on Glama, Smithery, PulseMCP, mcpservers.org, and via PR to awesome-mcp-servers. For developers browsing for MCP tools.

Why: Comparable servers (DevStudio, third-eye-mcp, mcp-screenshot) are found through exactly these directories (Glama search, mcpservers.org). None of them match this repo's depth, but this repo isn't listed where people look. The official Registry (#90) is done; these are the next channels and cost an afternoon.

Approach: Badges generated from the same config JSON used in the README. Submit each listing; add glama.json if needed for ownership claim. Track listings in a short checklist in the issue.
Done: Badges live (tested on Windows VS Code + Cursor), listed in 4+ directories, and an awesome-list PR is merged.

主要語言
TypeScript
星號
1
分支
4
平均合併
14 小時 8 分鐘
30 天內合併 PR
48

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

TMHSDigital/screencast-mcp 的其他 Issue

查看 TMHSDigital/screencast-mcp 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。