Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Search and add animated Expo and React Native UI components, charts and screens to your app.
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.
You 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": {
"expokit": {
"command": "npx",
"args": [
"-y",
"@expokit/cli",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add expokit -- npx -y @expokit/cli mcpPaste 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.
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.
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 registry name was verified with the GitHub account Anshkaran7, which owns the repo
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 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.
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.5.2) reached the registry 7 days 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: Context7, Codebase Memory, Exa
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
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
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.
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.
[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)
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.
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.
Everything else — live previews, props, installation, theming, Pro, AI / MCP setup and help — is on [expokit.in](https://expokit.in/docs).
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.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.login or set EXPO_KIT_TOKEN (--token leaves it in your shell history).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.
MIT