For AI coding agents
NativeKeel MCP: React Native ground truth for your AI agent
AI agents lose hours on React Native upgrades: native build errors, library versions that do not match your React Native version, New Architecture blockers, store rules that changed last month. NativeKeel already knows the answers. Over the Model Context Protocol, Claude Code, Codex, Cursor and other agents can ask it instead of guessing.
Set it up
Install in CursorInstall in VS Code
Claude Code
The plugin adds the MCP server and a skill that tells Claude when to use it, so you do not have to ask:
claude plugin marketplace add AlicanAkyol/nativekeel
claude plugin install nativekeel@nativekeelOr only the MCP server: claude mcp add nativekeel -- npx -y nativekeel@latest mcp
Codex
The plugin adds the MCP server and the same skill:
codex plugin marketplace add AlicanAkyol/nativekeel
codex plugin add nativekeel@nativekeelCodex starts plugin servers in the plugin's own folder, so the plugin uses your home folder as the boundary. To narrow it to one project, configure the server yourself in ~/.codex/config.toml (below) with NATIVEKEEL_MCP_ROOTS in its env.
Or only the MCP server:
# ~/.codex/config.toml
[mcp_servers.nativekeel]
command = "npx"
args = ["-y", "nativekeel@latest", "mcp"]Any agent, no MCP needed
Add one line to your project's AGENTS.md or CLAUDE.md:
Before upgrading React Native or Expo, adding a native library, or preparing a store release, run `npx -y nativekeel@latest --json` and fix the critical and high findings first.Also listed in the official MCP Registry as io.github.AlicanAkyol/nativekeel.
What changes, on one real app
We asked Claude Code the same question in an open-source Expo SDK 57 app, without naming NativeKeel: "I want to upgrade this app to the latest React Native. What will break and what should I do first?"
| With the NativeKeel plugin | Without | |
|---|---|---|
| How it worked | Loaded the skill on its own, called upgrade_plan and scan_project | Read files, searched the web |
| Turns · cost | 9 · $0.34 | 16 · $0.63 |
| Xcode 27 / UIScene | Found, with the exact package versions | Found |
| Missing account deletion (App Store 5.1.1(v), Google Play) | Found: it blocks the next release | Missed |
| Expo SDK 58 changes (R8 on by default in release builds) | Found, and checked that the app's release scripts are affected | Found |
One app, one run each, so read it as an example rather than a benchmark. The first run (NativeKeel 0.1.57) missed the SDK 58 changes, which the agent without NativeKeel found on the web; 0.1.59 added them, and the table shows the run after that.
What the agent can ask
| Tool | Answers |
|---|---|
security_audit | Focused security review: data exposure, account access, unsafe code execution and backend rules. Source evidence, attacker prerequisites, fixes, validation steps and explicit coverage limits. No live attack. |
scan_project | What is wrong with this project: upgrade blockers, New Architecture, Google Play and App Store rules (target SDK, 16 KB pages, Xcode 27 UIScene, privacy manifests), crash risks, OWASP MASVS security findings, and malware planted in the project. Each with file:line and the fix. |
upgrade_plan | The order to do it in: phases, the reason for each, concrete steps. |
explain_error | A build, launch, crash or App Store / Google Play review error: what it means, the fix, and where this project is affected. Matched locally against errors we reproduced or verified at the source. |
verify_upgrade | After an upgrade, before committing: what got fixed, what is new and how versions moved compared with the last commit (or any revision). |
check_library | Before adding or upgrading a package: latest version, New Architecture support, maintenance status, the range that works with your React Native version, replacements and known traps. |
Built for untrusted code
An agent reads what a tool returns, so a malicious repository could try to use the tool to pass instructions to the agent. The server is designed against that:
- Read-only. No tool writes to your project or executes project code.
verify_upgradeunpacks the committed version into a temporary folder outside the project and deletes it. - Warns before the agent runs a project. If the project hides malware (a VS Code task that runs on folder open, code hidden after a long run of spaces in
babel.config.js, JavaScript saved as a font), the result tells the agent not to install, start or build it. - Only your folders. It scans folders under the directory it was started in (plus
NATIVEKEEL_MCP_ROOTS), with symlinks resolved. Servers started in the filesystem root or inside a plugin directory require explicit project folders inNATIVEKEEL_MCP_ROOTS. File reads, including symlinks and parent lookups, stay within those folders. - No source code in results. Findings point to
file:line; file contents are never returned. - Cleaned text. Control, zero-width and bidi characters are removed; text that reads like instructions to an AI agent is replaced and reported.
- git cannot be turned against you. A repository's own git config cannot make the scan run a program.
- No dependencies, published with npm provenance.
Details: SECURITY.md.