Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Vaybel turns apparel ideas into designs and mockups through a public MCP server and agent skills.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.vaybel.com/Run this in your terminal
claude mcp add --transport http vaybel https://mcp.vaybel.com/Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"vaybel": {
"url": "https://mcp.vaybel.com/"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"vaybel": {
"type": "http",
"url": "https://mcp.vaybel.com/"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp.vaybel.com/Menu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain vaybel.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 28 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Georgia MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
An MCP server for Georgian public data, read from the organizations that publish it.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.