Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

ExpoKit

by Anshkaran7version 0.5.2i★ –iRuns on your computer
Registry nameio.github.Anshkaran7/expokit

Install

Overview

Description from the maker (original English)

Search and add animated Expo and React Native UI components, charts and screens to your app.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

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: Search & AI memory

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": {
    "expokit": {
      "command": "npx",
      "args": [
        "-y",
        "@expokit/cli",
        "mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add expokit -- npx -y @expokit/cli mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "expokit": {
      "command": "npx",
      "args": [
        "-y",
        "@expokit/cli",
        "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.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "expokit": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@expokit/cli",
        "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 Anshkaran7, 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 Search & AI memoryi

  • More stars than 0% of the other 7271 servers in this category
  • Published to the registry more recently than 84% of the other 7271 servers in this category
  • Basic checks equal to or better than 100% of the other 7271 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 ExpoKit 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 (0.5.2) reached the registry 7 days 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: Context7, Codebase Memory, Exa

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

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday
Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago
Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month
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.

@expokit/cli

The CLI for [ExpoKit](https://expokit.in) — animated UI components for Expo and React Native. It copies the component source into your app (like shadcn/ui), so you own the code.

Payment card and flip card are free; the dashboard and checkout screens are Pro blocks.

  • Buttons, inputs, cards, sheets, tabs, charts and full screens, all animated, with light and dark mode
  • Built for touch: springs, drag gestures and haptics, on iOS, Android, web and in Expo Go
  • You own the code: plain typed files in your app, with no runtime library to lock you in

[Browse every component with live previews →](https://expokit.in/docs/components) · [Try them on your phone in Expo Go →](https://expokit.in/docs/run-on-your-phone)

Usage

In your Expo app's folder:

npx @expokit/cli@latest init

npx @expokit/cli@latest add button otp-input

import { Button } from '@/components/ui/button';

Save ;

See every component: npx @expokit/cli@latest add --list

Already have a Skeleton.tsx (or any file the kit would clash with)? add skips that item, says why, and adds the rest. Put the kit's copy next to yours with --dir:

npx @expokit/cli@latest add skeleton --dir src/components/kit   # import from "@/components/kit/ui/skeleton"

init asks for your brand colour, font, radius and light / dark (or takes --brand, --font, --radius, --scheme; --yes skips the questions) and writes lib/kit-theme.tsx, an wrapper for your root layout.

Keeping up to date

components.json remembers a hash of every file add wrote. When a new CLI ships fixes:

npx @expokit/cli@latest diff toast      # your changes since install, and what changed upstream

npx @expokit/cli@latest update # refresh every installed item

update refreshes the files nobody touched and stops on a file you patched, showing the diff, so your fix is never silently replaced. update toast --force takes upstream anyway.

Docs

Everything else — live previews, props, installation, theming, Pro, AI / MCP setup and help — is on [expokit.in](https://expokit.in/docs).

Security

  • No dependencies, no install scripts.
  • Anonymous install counts only — after a successful add, the CLI sends the item's name ({"items":["button"]}) to expokit.in so the site can show how often each component is installed. No token, files, paths or machine details; repeat adds count once a day. Turn it off with DO_NOT_TRACK=1 or EXPO_KIT_TELEMETRY=0; it never runs in CI, --dry-run or update.
  • Writes only inside your app — components.json, the @/* alias in tsconfig.json and the component files. --dry-run shows every change first; add and update never overwrite a file you changed unless you pass --force (the hashes in components.json only ever mark a file as untouched; their paths are never read or written), and never replaces one that differs only by case (Skeleton.tsx vs skeleton.tsx), a symlink or a folder, not even with --force. paths in components.json that point outside the app are refused, and aliases must be plain import aliases (they are written into the copied files' imports). A file that is a symlink is never written through; a symlinked *folder* inside the app is still followed, so a cloned repo that links a folder elsewhere can send writes there.
  • Free components need no network to install — they ship inside this package. Pro components are downloaded over HTTPS from expokit.in; your token is stored readable only by you, sent only to that site and never through a redirect. In scripts, pipe it to login or set EXPO_KIT_TOKEN (--token leaves it in your shell history).
  • Runs one command: npx expo install for the packages a component needs — without EXPO_KIT_TOKEN in its environment, so install scripts never see your token.

Report a vulnerability privately: SECURITY.md.

License

MIT

Ask PopNx