Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Install & correctly use appCN React Native / Expo components, streamed from the live registry.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
APPCN_REGISTRY_URL你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"appcn": {
"command": "npx",
"args": [
"-y",
"@app-cn/mcp"
],
"env": {
"APPCN_REGISTRY_URL": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add appcn --env APPCN_REGISTRY_URL=your-value -- npx -y @app-cn/mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"appcn": {
"command": "npx",
"args": [
"-y",
"@app-cn/mcp"
],
"env": {
"APPCN_REGISTRY_URL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"appcn": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@app-cn/mcp"
],
"env": {
"APPCN_REGISTRY_URL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
APPCN_REGISTRY_URL env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
发布者(shineup.digital)不是仓库所有者(Salah-XD);可能是其他人代为上架的
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 0 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.2)于5个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, EmbeddedCI BenchPod
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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 ↗