feature: an MCP server and a CLI over data.json so agents and scripts can query licensed assets directly
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 30/100
- Issue 类型
- 功能
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- javascript, node.js
调研方向
Start with site/README.md for the documented data fields and site/lib/search.mjs for the existing Node search and filter logic. Then inspect site/dist/data.json to understand the catalog records. Done means a CLI can search from npx, an MCP server exposes the requested tools in at least one client, and the README links both.
由索引模型根据 Issue 内容生成。
描述
Why it matters
The repo already ships llms.txt and llms-full.txt, so the audience includes people asking an assistant "find me a CC0 pixel font" or "is this pack OK in a commercial Unreal game". A Model Context Protocol server turns the catalog into a tool those assistants call with structured filters (category, licence family, commercial, attribution, engine lock, format) and get back the recorded licence text and verified date instead of a guess. A CLI gives shell users and CI jobs the same (for example, fail a build if a referenced asset is commercial: false). Both are thin wrappers over data.json.
Evidence
site/dist/data.jsonwith stable, documented fields (site/README.md).site/lib/search.mjsalready holds scoring and filter logic that runs in Node unchanged.
Suggested approach
- A package (separate repo or
packages/mcp/) with toolssearch_assets,get_asset,check_license(id, engine, commercial),list_stacks; fetchesdata.jsonfrom the Pages URL with a cache and a--dataflag for local builds. - Publish to npm with a
bin:npx free-game-dev-assets search "pixel font" --license cc0 --format ttf. - README section "Use the data" with Claude Desktop / Cursor config snippets.
Done when
The CLI search works from npx, the MCP server appears in at least one client with its tools, and the README links both.
- 主要语言
- JavaScript
- 星标
- 58
- 派生
- 15
- 平均合并
- 16 小时 53 分钟
- 30 天内合并 PR
- 14
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
TMHSDigital/Free-Game-Dev-Assets 的其他 Issue
-
community marketing priority: low
难度 2/5 1-3 小时 新手友好度 72/100
TMHSDigital/Free-Game-Dev-Assets#151 ·
维护者通常 1 天内回复
-
documentation priority: medium
难度 2/5 1-3 小时 新手友好度 78/100
TMHSDigital/Free-Game-Dev-Assets#72 ·
维护者通常 1 天内回复
-
enhancement
难度 1/5 1-3 小时 新手友好度 68/100
TMHSDigital/Free-Game-Dev-Assets#3 · 1 条评论 ·
维护者通常 1 天内回复
-
marketing priority: low
难度 2/5 1-3 小时 新手友好度 55/100
TMHSDigital/Free-Game-Dev-Assets#152 ·
维护者通常 1 天内回复
-
feature priority: medium
难度 5/5 一周以上 新手友好度 25/100
TMHSDigital/Free-Game-Dev-Assets#144 ·
维护者通常 1 天内回复
查看 TMHSDigital/Free-Game-Dev-Assets 的全部 Issue
相似的 Issue
-
bug require-triage
难度 2/5 1-3 小时 新手友好度 72/100
expressjs/expressjs.com#2549 · 1 个 reaction ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
-
难度 1/5 1 小时以内 新手友好度 85/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
vercel-labs/agent-skills#348 ·
-
难度 2/5 1-3 小时 新手友好度 65/100
NanmiCoder/dsh-agent-teams#289 ·
维护者通常 1 天内回复