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
Font Lab
Overview
Description from the maker (original English)
A decision surface for typography: curate font directions on your real site, ship next/font code.
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.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"font-lab": {
"command": "npx",
"args": [
"-y",
"font-lab",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add font-lab -- npx -y font-lab mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"font-lab": {
"command": "npx",
"args": [
"-y",
"font-lab",
"mcp"
]
}
}
}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.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"font-lab": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"font-lab",
"mcp"
]
}
}
}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 jmg698, 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 32678 servers in this category
- Published to the registry more recently than 19% of the other 32678 servers in this category
- Basic checks equal to or better than 100% of the other 32678 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 Font Lab 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 (1.0.0) reached the registry 3 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, Starreel
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 2 days ago
Install
Starreel
by starreel
Turn a script into a finished, downloadable short-drama episode — via MCP or REST.
Runs on your computerUpdated 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.
Font Lab
Pick the fonts. Fix the words. Your agent does the work.
Font Lab is a real-time typography and text editor for AI-built sites. Your agent installs it, composes curated font directions Google fonts and distinctive open-foundry faces, and renders them live on your real site. You can toggle between the fonts and pick the one you like. The agent then finishes it up— next/font + Tailwind on Next.js, self-hosted @font-face everywhere else — reversibly.
Most AI-built sites ends up with generic fonts, like Inter or Geist, because the agent just uses defaults. Font Lab brings the human choose from options the agents curates based on some intake questions. It also allows you to edit text to make it sound like you wrote it.
copy-able prompt here: https://www.jack-mcgovern.com/fontlab
Install
Inside your project — use this prompt:
Install font-lab (npx font-lab install) and set it up for me — start whatever needs to run; I shouldn't have to touch the terminal. Ask me a couple of questions, compose font directions for this project, and show them on my real pages: the live panel if you're on my machine, screenshots if you're not. Before you tell me to look, make sure it actually worked — the panel really loaded, or the screenshots really came out. I make the call. Don't pick for me. Then write the code for the one I choose, and stick around — I'll have text fixes as I go.Works with: Claude Code · Cursor · VS Code · Codex · Windsurf · Gemini CLI For: any framework with a CSS seam — Next.js gets the full live-panel experience; everything else ships through the same engine (see the matrix below).
Install auto-detects which agents you have and wires them all — skill, MCP server, config, each in the right format. On a stack with no seam at all, Font Lab refuses to half-apply and hands you the generated code with a clear reason instead.
Newly registered MCP tools load on the next session reload — but the agent never has to wait: every tool also runs as a one-shot CLI, npx font-lab run ' ' (same tool table, same JSON out), so the loop starts the moment install finishes. That's also the fallback whenever an MCP server drops mid-session.
Frameworks — what ships where
The taste engine, shippability gate, portable preview, and screenshots work on every stack. What varies is the preview surface and how the pick lands in your code — font-lab analyze prints the exact verdict for your project:
| Your stack | Preview | Auto-ship |
|---|---|---|
| Next.js App Router + Tailwind v4 | live in-app panel + real-site screenshots | next/font + Tailwind codegen |
| Any framework + Tailwind v4 (Vite, Astro, Remix, SvelteKit, TanStack, …) | real-site screenshots (headless paint) + portable sheet | self-hosted @font-face + @theme role map in your CSS entry |
Any framework + Tailwind v3 (fonts in tailwind.config fontFamily) | real-site screenshots (headless paint) + portable sheet | self-hosted @font-face + utility/Preflight overrides in your CSS entry |
No Tailwind, fonts routed through CSS variables (--font-body, --fd, …) | real-site screenshots (headless paint) + portable sheet | self-hosted @font-face + your own font vars repointed |
No seam (hardcoded font-family, CSS-in-JS) | real-site screenshots (headless paint) + portable sheet | hand-apply: Font Lab generates the block, you paste it |
Every auto-ship path is fenced, idempotent, and reversible (font-lab undo). Agents: read capabilities + shipNote from font_lab_analyze — a non-Next stack is a different route through the same loop, never a reason to stop.
Upgrading
Always use `upgrade`, not bare `npm install`.
npx font-lab upgradeFont Lab lives in two places: the npm package and the panel code stamped into your project (app/_fontlab/). A bare npm install font-lab@latest updates the package but leaves the panel on the old version — which shows a "stale version" warning. upgrade moves everything together in one command: package, panel re-stamp, MCP re-pin, and stale-endpoint shutdown.
How it works
- Ask. Font Lab asks what you're going for — what feeling, how bold a departure, a brand to evoke or avoid — so the directions are tailored to you, not a generic default.
- Compose. Your agent composes a small set of font directions (display + body + mono, each with a rationale), reaching past the overexposed AI defaults. A built-in anti-generic rubric rejects menus that are all Inter/Geist/Space Grotesk.
- Pick. You compare them on your own site — screenshots in chat (works on web or phone) or a live flip/mix/compare panel locally. You always make the pick.
- Ship. The agent writes the real code for your stack —
next/font+ Tailwind on Next.js; self-hosted@font-facewired through Tailwind's theme, v3 utilities, or your own CSS font variables elsewhere. Every change is reversible. - Finish clean. Click done ✓ (or say so) and the agent runs
font_lab_finish: the dev-panel scaffolding comes out, and you get a git-verified commit plan — your copy edits and font change with ready-to-run commands, nothing of Font Lab's mixed in. The scaffolding and state are self-ignoring in git the whole session, sogit statuswas never noisy to begin with.
The panel
The Font Lab panel sits on top of your running site — your real pages, your real content — and lets you change fonts and words in real time.
- Flip through directions with arrow keys — see each pairing on your actual content across multiple routes
- Mix roles — heading from one direction, body from another — and save the mix as its own direction
- Before/after — hold
Bto peek at your current fonts; tapspaceto snap between your two finalists - Inspect — hover any text to see its role, typeface, size, and how many elements share it
- Edit words — double-click any text, retype it, and it saves straight to your source files
- Change receipts — see exactly what changed across the page after every edit
- Undo everything — every modification ships with a reversal command
- Done ✓ — one click ends the session cleanly: your agent strips the dev tooling and hands you the exact commit plan
The panel runs headless too: the agent screenshots your site in each direction and shows you the images in chat — a chat-sized hero shot per direction, with the full-page capture behind it. Works on a phone, on the web, anywhere your agent runs.
The live panel is Next-only — but the real-site preview isn't. On every other framework, Font Lab paints your actual running pages in each direction (the same render-first census machinery the panel flips with, injected headlessly — no scaffolding, no source writes; preview fonts cache in self-ignored state, so your git status stays clean until you actually ship). If no dev server is running, the screenshot tool starts your project's own dev command itself — bound to 127.0.0.1, health-checked, stopped after the capture — which is what makes the loop work unattended in cloud/container agents (Claude Code on the web, and friends) where the human can't reach the agent's localhost. With no dev server possible at all, the fallback is the portable preview: a self-contained HTML specimen sheet (fonts embedded, opens offline) on your own palette and copy — clearly labeled as specimen cards, never passed off as your pages.
Honesty
Font Lab's core promise is preview == ship: what you see in the panel is what the codegen writes.
- Guaranteed fidelity for every font the gate admits — or an honest "may render slightly differently" badge when it can't be byte-for-byte.
- Auto-ships only where the stack has a real seam; anywhere else it hands you the generated code with a clear reason rather than guessing. Never a half-applied change — that's the contract.
- Text sourced externally triggers an explicit notice, never a silent edit.
- The human's pick overrides everything.
Contributing & testing
Testers are the point — especially "it did the wrong thing on *my* repo" reports. The analyzer output is the most useful thing you can include.
- Issue forms — bugs and "support my stack" requests
CONTRIBUTING.md— code contributions and how to run the testsSECURITY.md— security issues
Going deeper
cli/README.md— the full user guide: install flags, the agent loop, every keyboard shortcut, the CLI referencedocs/CONCEPT.md— the vision and the core beliefdocs/ARCHITECTURE.md— how the choosing moment works and theselection.jsoncontractdocs/SHIP-SPEC.md— how a pick becomes real, reversible codedocs/PRODUCT.md·docs/PANEL-VISION.md— product and brand context
Open source · MIT · Published with npm provenance — every release is traceable to this repo and commit. Built and dogfooded on jack-mcgovern.com.