Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Vaybel turns apparel ideas into designs and mockups through a public MCP server and agent skills.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://mcp.vaybel.com/在终端中运行这条命令
claude mcp add --transport http vaybel https://mcp.vaybel.com/粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"vaybel": {
"url": "https://mcp.vaybel.com/"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"vaybel": {
"type": "http",
"url": "https://mcp.vaybel.com/"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://mcp.vaybel.com/菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 vaybel.com 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于29天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Qemu MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Boot and drive QEMU VMs from an AI agent: keys, screenshots, serial. No guest agent.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Vaybel Skills are agent workflows for operating clothing-product workflows through the public Vaybel MCP server.
Documentation: https://vaybel.github.io/skills/
This repo follows the code-execution-with-MCP pattern:
Agent skill -> TypeScript orchestration -> mcp.vaybel.com
There is no CLI dependency in v1. Skills call MCP through the small wrappers in servers/vaybel/, authenticated by VAYBEL_PAT.
These skills are the advanced user's starting point: fork them and iterate on the orchestration to fit your own workflow. The public MCP and REST surface is deliberately made of primitives; workflows are yours to compose, fork, and tweak here.
/vaybel:find-trend - find a trend opportunity and generate a launch concept./vaybel:plan-drop - plan a themed release: create or open a drop, see which trends fit its brief, pin them, file designs into it, and read its readiness./vaybel:launch-product - select a blank, generate a design, generate listing-ready mockups, optionally generate listing product videos, and return concise launch links./vaybel:optimize-product - import and optimize an existing Printify or Printful product./vaybel:make-content - generate a video, slideshow, carousel, or single post for an existing listing, with social drafts and explicit publish./vaybel:analyze-insights - read performance KPIs, top design snapshots, credit state, and next-best-action guidance.The scope matches the four primary Vaybel workflows:
Find Trend -> Launch Product -> Optimize Product -> Make Content
plan-drop wraps that loop in a release: a drop pins the trends that fit its brief and tracks the designs launched from them until they are live. analyze-insights is a read-only management skill for deciding which workflow to run next.
Claude Code marketplace install:
/plugin marketplace add vaybel/skills
/plugin install vaybel@vaybel
Use one shared secret for MCP and skills: define VAYBEL_PAT in Claude Code settings, and reference it from the Vaybel MCP server config. Then run:
/vaybel:launch-product "washed trail running poster art on a heavyweight tee"
/vaybel:launch-product "washed trail running poster art on a heavyweight tee" --listing-channels tiktok_shop,etsy /vaybel:find-trend tshirt --lifecycle rising /vaybel:plan-drop "Fall '26" --kind seasonal --date 2026-10-01 --motifs pumpkin,moon /vaybel:optimize-product --provider printify --product-id /vaybel:make-content --channels tiktok,instagram /vaybel:analyze-insights --range 28d
git clone https://github.com/vaybel/skills.git
cd skills npm install export VAYBEL_PAT=" " ./setup
client.ts MCP transport and auth helper
servers/vaybel/ thin typed wrappers around public MCP tools skills/*/ SKILL.md plus TypeScript orchestration per workflow .claude-plugin/ Claude Code marketplace metadata .codex-plugin/ Codex plugin metadata .cursor-plugin/ Cursor plugin metadata docs-site/ Astro Starlight documentation site (GitHub Pages) scripts/validate.mjs structural validation for skills and manifests scripts/smoke/ clean-project host install smoke tests DEPLOYMENT.md marketplace deployment checklist
npm run validate
npm run typecheck npm run build npm audit --omit=dev --audit-level=moderate scripts/smoke/host_install_smoke.sh
The smoke script creates a clean sibling project, installs the plugin into isolated Claude and Codex homes when those CLIs are available, and runs every skill runner in no-token mode. It uses tmux automatically when installed; pass --no-tmux to run serially.
The published docs at https://vaybel.github.io/skills/ are generated from this repository, not maintained separately. docs-site/scripts/sync-docs.mjs rebuilds every page from skills/*/SKILL.md, the skill references/, and the root Markdown files, so the site cannot drift from the skills it documents.
npm run docs:dev # local dev server
npm run docs:build # production build into docs-site/dist
.github/workflows/pages.yml builds the site on every pull request and deploys it to GitHub Pages on push to main.