appCN

digital.shineupPublished by shineup.digitalv0.1.2Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyDeveloper ToolsMedia & Design

Overview

AI-generated overview

appCN's MCP server lets a coding assistant discover and install appCN React Native / Expo UI components streamed from the live registry.

What you can do
  • Discover appCN React Native and Expo components from the live registry.
  • Install components into a project, with the CLI handling NativeWind and Reanimated wiring.
  • Write new code in appCN's motion and haptic style, including the AI-native collection (streaming bubbles, prompt composers, reasoning traces, voice orb).
  • Fetch component definitions from the registry, which can be pointed at a different base URL.
When to use it
Useful when building a React Native or Expo app and you want an AI coding agent such as Claude Code, Cursor or Windsurf to find and add appCN components for you instead of copying them by hand.
Requirements
Runs locally over stdio, typically launched with npx from the @app-cn/mcp npm package, so Node.js and network access to the appCN registry are needed. No authentication is declared. The optional APPCN_REGISTRY_URL variable overrides the registry base URL.
Before you install
Installing components writes files into your project and may modify NativeWind and Reanimated configuration, so review changes before committing. The server fetches component definitions from a remote registry, and APPCN_REGISTRY_URL can redirect that fetch to another host. The project is at an early v0.1.0 stage with five components.

Installation

In SourceWeft

  1. Open appCN in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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 ↗

Source: README.md at commit de0ffc0

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts