Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Code To Visual Interpreter
Overview
Description from the maker (original English)
Translate between generative code and the geometry it produces, keeping output assets lean...
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
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.
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.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
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.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
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
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account farssaadeldin7-ux, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 32583 servers in this category
- Published to the registry more recently than 69% of the other 32583 servers in this category
- Basic checks equal to or better than 100% of the other 32583 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Code To Visual Interpreter safe?
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.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.3) reached the registry 17 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, sync. labs
Alternatives
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
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
sync. labs
by synchronicity-labs
Lipsync videos, dub them into other languages, make talking videos and open sync. Studio.
Computer or cloudUpdated today
Install
README from the maker
Open the README
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.
Plugin Suite
Fourteen domain-expert plugins for Claude Code and Cowork. Each one encodes how a specialist in that field actually works — the order they do things in, the question that splits the field fastest, and the point at which they say they do not know.
Browse the full catalogue with live pricing at [codestudioplugin.com](https://www.codestudioplugin.com) — plans for every plugin are listed on the pricing page. Each plugin's tool server includes free tools for evaluating it before buying; a paid licence unlocks the rest. Every plugin is also published to Open VSX as a VS Code extension — in Cursor, Windsurf, VSCodium or Gitpod, search *code-studio* in the Extensions panel and install.
Installable as a marketplace:
/plugin marketplace add farssaadeldin7-ux/claude-plugin-suite/plugin install diagnose-by-sound@plugin-suite
The plugins
| Plugin | For | The judgement it encodes |
|---|---|---|
diagnose-by-sound | Workshop service advisers | Characterise the noise before naming a cause; report calibrated confidence, not a guess |
ghost-post-preview | Social managers | Name the most likely reason a post underperforms; never fabricate an engagement number |
professor-mind-reader | University students | Answer at the level the rubric verb demands; find the sentence that satisfies each criterion |
five-minute-fluency | Competitive players | Three changes maximum, ranked by rating gain per unit of practice |
trail-split | Expedition leaders | Every critical system has a named owner and a stated backup, or the plan is not finished |
podcast-video-studio | Content agencies | A clip that needs context is disqualified however good it was in the room |
customer-sales-support | SaaS founders | An AI support agent is only as good as the docs; "I don't know — here's a person" is a first-class answer |
haptic-feedback-mapper | Creative studios | A haptic that fires for something ignorable is worse than the screen it replaced |
mental-health-chatbot | Telehealth platforms | Support, not crisis intervention — escalation is always on and never a severity judgement |
neural-link-intention-layer | UI/UX designers | Eliminate, then batch, then automate — in that order |
generative-digital-twin | Studio heads | A style is defined by what you never do; the "never" list matters most |
emotional-resonance-analyzer | Advertising and marketing video editors | Flat stretches are the problem, not low stretches; real retention data always wins |
code-to-visual-interpreter | Creative technologists | Structure, modulation, surface — and a seeded PRNG or the piece is unreviewable |
predictive-resource-allocation | VFX and 3D studios | Find the binding constraint first; buying hardware is the last remedy, not the first |
Audiences, the skill each user must bring, and the monetisation shape are in docs/AUDIENCES.md.
Design rules
These are enforced by review, and partly by scripts/validate.mjs.
- No overclaiming. If the premise implies a capability that does not exist — reading minds, measuring an audience that was never asked, predicting a number from text — the plugin says so in its first paragraph and reframes as what it honestly is. A user who trusts a meaningless number is worse off than one who got nothing.
- Thresholds, not vibes. "Under 15% separation, do not present a winner" beats "consider carefully". Every judgement in a skill should be checkable.
- The limits section is mandatory. Every skill states what it cannot answer and when to say so.
- References carry the tables. SKILL.md holds the procedure; lookup tables, taxonomies and worked examples live in
references/and are pointed at from the step where they become relevant. - British spelling. No emoji, no hype vocabulary. The validator warns on both.
Layout
.claude-plugin/marketplace.json the marketplace manifestplugins/ / one directory per plugin .claude-plugin/plugin.json plugin manifest skills/ /SKILL.md the procedure skills/ /references/*.md tables, taxonomies, worked examples .mcp.json, mcp/ only where a plugin ships a tool server packages/suite-runtime/ shared MCP + licensing runtime, vendored into plugins services/billing/ the Stripe-backed licensing service the runtime talks to scripts/ validate, vendor, build docs/ architecture, audiences, licensing
Working on it
node scripts/validate.mjs # structure, manifests, frontmatter, dead referencesnode scripts/vendor-runtime.mjs # after editing packages/suite-runtime node scripts/build.mjs # .plugin archives into dist/ node scripts/build-vsix.mjs # VS Code extensions staged into dist/vsix/
CI runs all of these on every push. See docs/ARCHITECTURE.md for how to add a plugin, and docs/LICENSING.md for the free/paid split.
Publishing to Open VSX
Each plugin also ships as a VS Code extension: a thin extension.cjs that registers the plugin's MCP tool server through VS Code's MCP server definition provider API (VS Code 1.102+), with the whole zero-dependency mcp/ directory bundled inside the .vsix. The skills ship too: the bundled server publishes each one as an MCP prompt, which VS Code surfaces as a slash command (/mcp. . ). Listing is open; the skill body itself requires an active paid licence, same as the gated tools, since the .vsix is a public download.
One-time setup, in this order:
- Create an Eclipse Foundation account and log in to open-vsx.org with it.
- Sign the Publisher Agreement (open-vsx.org → your avatar → Settings → the agreement prompt).
- Create an access token (Settings → Access Tokens) and store it:
gh secret set OVSX_PAT --repo farssaadeldin7-ux/claude-plugin-suite
Then publish from the Actions tab: run the publish-openvsx workflow (optionally naming specific plugin ids). It packages every extension with vsce, creates the code-studio namespace if needed, and uploads each .vsix with ovsx, skipping versions that are already published. To build locally instead: node scripts/build-vsix.mjs --package.
The plugins also publish to npm as @farseman/ packages with the publish-npm workflow (runnable as npx @farseman/ ; needs the NPM_TOKEN repository secret described at the top of .github/workflows/publish-npm.yml), and to the official MCP Registry with the publish-mcp-registry workflow: scripts/build-mcpb.mjs packages each one as an .mcpb bundle attached to a GitHub release, and the workflow submits each listing under the io.github.farssaadeldin7-ux namespace, authenticated with the job's own GitHub OIDC token — no stored secrets.
The same extensions publish to Microsoft's VS Code Marketplace with the publish-vsmarketplace workflow. That marketplace has no trusted publishing, so it needs a Personal Access Token stored as the VSCE_PAT repository secret — the one-time setup is described at the top of .github/workflows/publish-vsmarketplace.yml.
Status
Version 0.1.3. All fourteen plugins ship working MCP servers built on the shared runtime, each gating its licensed tools behind the billing service and keeping open tools for evaluation before buying.
Licence
Source-available, not open source. The code is published so it can be read and evaluated; publication grants no rights to copy, modify, redistribute or create derivative works from it. Paid plugin tiers are governed by the commercial terms shown at the point of purchase. See LICENSE.