appCN

digital.shineup由 shineup.digital 发布v0.1.2更新于 Oct 24, 2026

Install & correctly use appCN React Native / Expo components, streamed from the live registry.

已验证STDIO仅桌面开发者工具媒体与设计

概览

AI 生成的概览

appCN 的 MCP 服务器让编程助手从实时注册表发现并安装 appCN 的 React Native / Expo 组件。

可以做什么
  • 从实时注册表发现 appCN 的 React Native 与 Expo 组件。
  • 把组件安装到项目中，由 CLI 处理 NativeWind 与 Reanimated 的接线。
  • 按 appCN 的动效与触感风格编写新代码，包括 AI 原生组件集（流式气泡、提示词输入框、推理轨迹、语音球）。
  • 从注册表获取组件定义，注册表基础地址可被覆盖。
适用场景
适合在开发 React Native 或 Expo 应用时使用，让 Claude Code、Cursor、Windsurf 等 AI 编程助手替你查找并添加 appCN 组件，而不必手动复制。
运行要求
以 stdio 在本地运行，通常通过 npm 包 @app-cn/mcp 用 npx 启动，因此需要 Node.js 以及访问 appCN 注册表的网络连接。未声明任何身份验证。可选变量 APPCN_REGISTRY_URL 可覆盖注册表基础地址。
安装前请注意
安装组件会向项目写入文件，并可能改动 NativeWind 与 Reanimated 配置，提交前请检查变更。服务器会从远程注册表获取组件定义，APPCN_REGISTRY_URL 可将该请求指向其他主机。项目处于 v0.1.0 早期阶段，目前仅有五个组件。

安装

在 SourceWeft 中

  1. 打开 控制台中的 appCN，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

appCN

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.

[@app-cn/ui on npm] [@app-cn/cli on npm] [License: MIT] [CI] [Stars]

[React Native] [Expo SDK 54] [NativeWind 4] [Reanimated 4] [Built with pnpm]

[Open in Expo Go] [Play Store — Coming soon]

Browse components · CLI docs · Mobile app · Live showcase · GitHub

Quick start

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.

bash
# 1. (Recommended) One-shot project setupnpx @app-cn/cli@latest init
# 2. Add any component by slugnpx @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:

bash
# Copy a single component via shadcn (no setup, one-off)npx shadcn@latest add https://appcn.vercel.app/r/voice-sphere.json
# Or pull the whole library as a managed depnpm 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:

bash
# Claude Codeclaude mcp add appcn -- npx -y @app-cn/mcp

See MCP docs 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.

What's in the box

New: appCN is live on real phones — scan a QR with Expo Go 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.

Base

ComponentDelight
ButtonSpring-y press scale to 0.96, settles in 140 ms — feels weighted, never twitchy

AI-native

ComponentDelight
StreamBubbleThree-phase thinking → token stream → settle
PromptInputSend morphs into a stop with a spinning ring
ReasoningTraceAuto-collapses the instant the answer lands
VoiceSphereReactive 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

Why appCN

  • Real-phone previews. Scan a QR with Expo Go and the component runs live on your device with native gestures. No emulator gymnastics.
  • AI-native flagship. The AI collection is the wedge — components built for AI apps that nobody else ships well.
  • Quadruple distribution. The 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.
  • Motion-first defaults. Reanimated + gesture-handler, shared motion tokens (duration / easing / spring), one delight detail per component.
  • Dark-mode first. Designed dark, then derived to light. Premium reads as depth, not rainbows.
  • You own the source. Copy-paste philosophy means no lock-in — once a component lands in your repo, edit freely.

Documentation

SurfaceWhat's there
appcn.vercel.appLive docs site — landing, every component, live previews
CLI docsinit, add, env vars, the idempotency contract
Mobile appPlay Store + Expo Go install paths, deep-link contract
CLAUDE.mdArchitecture, monorepo map, commands, Metro/Reanimated gotchas
DESIGN.mdTaste layer — motion rules, the "one delight detail" rule, the 8-step SOP
CONTRIBUTING.mdDev setup, the Changesets release flow, PR conventions
AGENTS.mdCross-tool guide for AI coding agents (Claude / Cursor / Windsurf / Codex / Aider)

Contributing

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 <slug>.meta.ts template ready to fill, wires the registry + showcase entries, and verifies with typecheck + registry build.

Full guide: CONTRIBUTING.md.

Releases

Releases are driven by Changesets and published to npm via OIDC Trusted Publishing — zero long-lived secrets.

bash
pnpm changeset           # describe what changed + pick a bumpgit commit -am "..."     # commit the changeset alongside your code# Open a PR. After merge to main, a "Version Packages" PR opens automatically.# Merge that PR → CI publishes via OIDC.

Every published version gets a verified provenance badge on npm.

Deploying

The site is two Vercel projects from one monorepo — click for setup.
ProjectVercel root directoryWhat it serves
Docsapps/webLanding, /components/*, /docs/*, the shadcn registry at /r/*.json
Showcaseapps/showcaseExpo web export — the iframe target for interactive previews

Deploy order (matters):

  1. Deploy the showcase first (apps/showcase) so you have a URL.
  2. Deploy the docs, setting NEXT_PUBLIC_SHOWCASE_WEB_URL to that URL.
  3. Optional: custom domains (appcn.vercel.app → docs, appcn-showcase.vercel.app → showcase).

Required env vars (docs project):

VariableValue
NEXT_PUBLIC_SHOWCASE_WEB_URLhttps://<showcase-project>.vercel.app
NEXT_PUBLIC_EXPO_URL(empty for v1 — needs EAS Update for the QR tab)
NEXT_PUBLIC_REGISTRY_URLhttps://<docs-domain>/r

The showcase project needs no env vars. Defaults live in apps/web/.env.example.

Acknowledgments

Inspired by shadcn/ui's copy-paste philosophy and react-native-reusables's docs-site polish. Built on top of NativeWind, Reanimated, and Expo.

License

MIT — you own the code.

Made with care by Salah-XD.
Powered by Shineup ↗

来源：README.md，提交 de0ffc0

工具

0
SourceWeft 尚未在沙箱中启动过该软件包，因此其工具未知。

版本历史

1
  1. v0.1.2最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手；SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分