Distribution: publish MCP server to PyPI (uvx), add Claude Code plugin manifest, list on Cursor marketplace and MCP registries

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

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
csharp, python

研究方向

Start by reading release.yml, the current MCP server packaging and entry point, and the README sections describing installation and Claude Code support. Check how package data is currently loaded and what Cursor and Claude Code expect in their plugin manifests. Done means a one-command PyPI install works, both plugin installation paths are documented and usable, and the project is listed in at least two MCP directories.

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

描述

feature marketing priority: high

Why it matters

Right now the only way to get the MCP server is to clone the repo and pip install inside it, and the project is not discoverable where Unity developers look for AI tooling. CLAUDE.md claims Claude Code support, but there is no Claude Code plugin manifest. Distribution is the main growth lever for a 4-star project.

Proposal

  1. PyPI package for the MCP server (unity-developer-tools-mcp), runnable with uvx unity-developer-tools-mcp or pipx. Data files packaged as package data (also fixes the CWD bug). Publish from release.yml with trusted publishing.
  2. Claude Code plugin: add .claude-plugin/plugin.json and .mcp.json so the same skills and MCP server install via /plugin; document it in README.
  3. Cursor marketplace submission (roadmap M4), with screenshots and a short demo.
  4. MCP registries: list on the official MCP registry and common directories (Smithery, mcp.so, Glama), and in awesome-cursor / awesome-mcp-servers / awesome-unity lists.
  5. One-click install link / deeplink for Cursor MCP config in README.

Done when

A user can install the server with one command, install the plugin from Cursor or Claude Code without cloning, and the project appears in at least two MCP directories.

主要語言
C#
星號
4
分支
0
PR 合併指標
30 天內沒有已合併 PR

環境準備

從這裡開始

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

TMHSDigital/Unity-Developer-Tools 的其他 Issue

查看 TMHSDigital/Unity-Developer-Tools 的全部 Issue

相似的 Issue

更多 C# Issue

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

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