Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Install & correctly use appCN React Native / Expo components, streamed from the live registry.
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.
APPCN_REGISTRY_URLYou need
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": {
"appcn": {
"command": "npx",
"args": [
"-y",
"@app-cn/mcp"
],
"env": {
"APPCN_REGISTRY_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add appcn --env APPCN_REGISTRY_URL=your-value -- npx -y @app-cn/mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"appcn": {
"command": "npx",
"args": [
"-y",
"@app-cn/mcp"
],
"env": {
"APPCN_REGISTRY_URL": "your-value"
}
}
}
}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": {
"appcn": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@app-cn/mcp"
],
"env": {
"APPCN_REGISTRY_URL": "your-value"
}
}
}
}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.
APPCN_REGISTRY_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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 publisher (shineup.digital) is not the repo owner (Salah-XD); someone else may have listed it
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 0 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 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).
The GitHub repo last changed –, and the latest version (0.1.2) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Starreel
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.
Turn a script into a finished, downloadable short-drama episode — via MCP or REST.
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.
Copy-paste mobile components for React Native + Expo.
A shadcn-philosophy library: you own the source, NativeWind styles the surface, Reanimated drives the motion — and the featured AI-native collection ships streaming bubbles, prompt composers, reasoning traces, and a reactive 3D voice orb.
[Browse components](https://appcn.vercel.app/components) · [CLI docs](https://appcn.vercel.app/docs/cli) · [Mobile app](https://appcn.vercel.app/docs/mobile-app) · [Live showcase](https://appcn-showcase.vercel.app) · [GitHub](https://github.com/Salah-XD/appCN)
The CLI handles NativeWind + Reanimated wiring and registers the @app-cn shadcn namespace for you. One command to set up, one to add a component.
# 1. (Recommended) One-shot project setup
npx @app-cn/cli@latest init
npx @app-cn/cli@latest add voice-sphere
Prefer your own pipeline? appcn add is a thin wrapper around shadcn — you can skip the CLI entirely:
# Copy a single component via shadcn (no setup, one-off)
npx shadcn@latest add https://appcn.vercel.app/r/voice-sphere.json
npm install @app-cn/ui
Building with an AI agent? Add the appCN MCP server so Claude Code, Cursor, or Windsurf can discover and install components for you — and write new code in appCN's motion/haptic style:
# Claude Code
claude mcp add appcn -- npx -y @app-cn/mcp
See [MCP docs](https://appcn.vercel.app/docs/mcp) for Cursor / Windsurf / VS Code config.
Status: v0.1.0 live on npm. Five components shipped — the AI collection
is the marketed wedge and is the first place to land new work.
New: appCN is live on real phones — scan a QR with [Expo Go](https://appcn.vercel.app/docs/mobile-app)
and the entire component gallery loads on Android or iPhone in seconds.
No emulator, no developer account. Standalone Play Store APK is in review —
shipping soon.
| Component | Delight |
|---|---|
Button | Spring-y press scale to 0.96, settles in 140 ms — feels weighted, never twitchy |
| Component | Delight |
|---|---|
StreamBubble | Three-phase thinking → token stream → settle |
PromptInput | Send morphs into a stop with a spinning ring |
ReasoningTrace | Auto-collapses the instant the answer lands |
VoiceSphere | Reactive 3D orb that breathes with voice level |
Every component has an interactive web preview, a QR you can scan with Expo Go to run it live on your phone, and a video — same code path on every surface. → [appcn.vercel.app/components](https://appcn.vercel.app/components)
appcn CLI, the shadcn registry, @app-cn/ui from npm — or the MCP server, so your AI coding agent installs components for you. Same primitives, your call.duration / easing / spring), one delight detail per component.| Surface | What's there |
|---|---|
| [appcn.vercel.app](https://appcn.vercel.app) | Live docs site — landing, every component, live previews |
| [CLI docs](https://appcn.vercel.app/docs/cli) | init, add, env vars, the idempotency contract |
| [Mobile app](https://appcn.vercel.app/docs/mobile-app) | Play Store + Expo Go install paths, deep-link contract |
| [`CLAUDE.md`](./CLAUDE.md) | Architecture, monorepo map, commands, Metro/Reanimated gotchas |
| [`DESIGN.md`](./DESIGN.md) | Taste layer — motion rules, the "one delight detail" rule, the 8-step SOP |
| [`CONTRIBUTING.md`](./CONTRIBUTING.md) | Dev setup, the Changesets release flow, PR conventions |
| [`AGENTS.md`](./AGENTS.md) | Cross-tool guide for AI coding agents (Claude / Cursor / Windsurf / Codex / Aider) |
Every new component ships through the 8-step SOP in DESIGN.md → Component checklist. Don't skip steps — the PR template enforces them and a missing changeset blocks the release pipeline.
Working with an AI agent? Invoke the `/new-component` Claude skill — it walks the checklist, drops a typed .meta.ts template ready to fill, wires the registry + showcase entries, and verifies with typecheck + registry build.
Full guide: CONTRIBUTING.md.
Releases are driven by Changesets and published to npm via OIDC Trusted Publishing — zero long-lived secrets.
pnpm changeset # describe what changed + pick a bump
git commit -am "..." # commit the changeset alongside your code
Every published version gets a verified provenance badge on npm.
The site is two Vercel projects from one monorepo — click for setup.
| Project | Vercel root directory | What it serves |
|---|---|---|
| Docs | apps/web | Landing, /components/*, /docs/*, the shadcn registry at /r/*.json |
| Showcase | apps/showcase | Expo web export — the iframe target for interactive previews |
Deploy order (matters):
apps/showcase) so you have a URL.NEXT_PUBLIC_SHOWCASE_WEB_URL to that URL.appcn.vercel.app → docs, appcn-showcase.vercel.app → showcase).Required env vars (docs project):
| Variable | Value |
|---|---|
NEXT_PUBLIC_SHOWCASE_WEB_URL | https:// .vercel.app |
NEXT_PUBLIC_EXPO_URL | *(empty for v1 — needs EAS Update for the QR tab)* |
NEXT_PUBLIC_REGISTRY_URL | https:// /r |
The showcase project needs no env vars. Defaults live in apps/web/.env.example.
Inspired by shadcn/ui's copy-paste philosophy and react-native-reusables's docs-site polish. Built on top of NativeWind, Reanimated, and Expo.
MIT — you own the code.
Made with care by Salah-XD .
Powered by Shineup ↗