GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
作者提供的说明(英文原文)
List, create and deploy your Prefab project templates from any MCP agent.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"prefab": {
"command": "npx",
"args": [
"-y",
"prefab-mcp"
]
}
}
}在终端中运行这条命令
claude mcp add prefab -- npx -y prefab-mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"prefab": {
"command": "npx",
"args": [
"-y",
"prefab-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"prefab": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"prefab-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
发布者(prefabapp.io)不是仓库所有者(davidjaykelly);可能是其他人代为上架的
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 0 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.1)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:GitHub, Desktop Commander, Cloudflare MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
An MCP server for Prefab, so an agent can see your templates and deploy one for you.
"Set up a new client folder for Northwind, autumn campaign, on my Desktop"
| Tool | Does |
|---|---|
list_templates | Every template, what it creates, what it asks for |
describe_template | One template in full: structure, placeholders, actions |
preview_deploy | What a deploy would create, and what values are still missing. Creates nothing |
deploy_template | Creates the folders, filling in the values given |
list_watched_folders | Folders Prefab is watching, and the rules on them |
list_globals | Library-wide placeholders, actions and value presets |
Works with any client that speaks MCP over stdio.
As a bundle - download prefab.mcpb from the releases page and double-click it. Clients that install MCP bundles, Claude Desktop among them, bring their own Node, so there is nothing else to install.
From the command line (Claude Code, and anything with the same idea):
claude mcp add prefab -- npx -y prefab-mcp
In a config file - Cursor, Zed, and most others:
{
"mcpServers": { "prefab": { "command": "npx", "args": ["-y", "prefab-mcp"] } } }
Then switch on Let agents and scripts control Prefab in Prefab's Settings ▸ Permissions. It is off by default; reading your templates works without it, creating and deploying does not.
That switch arrives in Prefab 1.1.6. On an earlier version the reading tools work and the rest say so.
Requires macOS, Prefab installed and opened once, and Node 18+ (except for the .mcpb route).
Prefab is sandboxed and has no network access, so it cannot host anything. This server runs beside it instead: it reads the library straight out of the app group (~/Library/Group Containers/group.VFDG327T66.prefab) and asks the app to deploy through the same prefab:// URL the Finder extension uses. Two consequences worth knowing:
preview_deploy and deploy_template both check first and say so, rather than leaving a permission dialog on screen that an agent cannot answer. Grant folders in Prefab, under Settings ▸ Permissions.Nothing here writes to Prefab's library. The app owns those files, and editing them behind its back would be overwritten the next time it saves.
npm test # checks placeholder resolution matches the app's Swift, case for case npm run try '[["list_templates",{}]]' # call a tool the way a client does
src/resolve.js is a deliberate duplicate of RenamePattern.swift. If you change one, change the other - npm test compiles the Swift and compares the two.