You build from one template, but you own 18. Connect Claude Code, Cursor or Codex to the Native Templates MCP server and your agent can search all of them, pull the screen or component you need, and get a checklist for fitting it into your app.
The rules file in each template teaches your agent that one codebase. The MCP server adds the rest of your bundle as a library it can read from, so you can ask for things like this:
“Add the checkout flow from Velora to this app. Use our existing Button and Header.”
“Which templates have an order tracking screen with a map? Show me how Foody builds it.”
“I need a swipeable card stack. Is there one in the library, and what does it depend on?”
Eight read-only tools. Your agent picks them itself; you just describe what you want in plain language.
See every template in your bundle and each one's screens and components.
Find screens, components and patterns by what they do: checkout, order tracking, paywall.
Get a screen's source together with the components, packages and images it depends on.
Get one template's version of a component, its props, and where it is identical elsewhere.
Hooks, contexts, mock data, layouts and config, by path.
Read a template's rules, or ask which component it uses for a given UI need.
Colour tokens for light and dark mode, and the differences between two templates.
What to copy, what your project already has, missing packages, import changes and tokens.
Nothing to install. You add one address and your license key to your AI tool.
Open the customer portal, sign in with the email you purchased with, open your bundle and copy the NativeWind MCP key. Paste it here and the commands below are filled in for you.
The key stays in your browser. It is not sent or saved anywhere by this page.
Your tool will not ask for the key: it has to be part of the command or config, as shown here. Paste your key above to fill it in.
claude mcp add --transport http native-templates https://www.native-templates.com/api/mcp \ --header "Authorization: Bearer YOUR_LICENSE_KEY" --scope user
{
"mcpServers": {
"native-templates": {
"url": "https://www.native-templates.com/api/mcp",
"headers": { "Authorization": "Bearer YOUR_LICENSE_KEY" }
}
}
}# in your shell profile export NATIVE_TEMPLATES_KEY="YOUR_LICENSE_KEY" # in ~/.codex/config.toml [mcp_servers.native-templates] url = "https://www.native-templates.com/api/mcp" bearer_token_env_var = "NATIVE_TEMPLATES_KEY"
Use the address exactly as shown, including www. Keep the key out of files you commit: add the server at user level rather than inside a project.
Restart your tool so it connects, then ask in plain language, for example: “Add the checkout flow from Velora to this app. Use our existing Button and Header.” The agent searches the library, reads what it needs and adapts it to your project.
Components with the same name are not always the same file in two templates. Before copying anything, the agent asks for a porting checklist. This is a real one, for moving a checkout screen from one template into another.
Porting velora app/screens/checkout.tsx into a project based on drivo 1. Files this needs (13): Copy from velora (not in drivo), dependencies first: - [component] components/Toggle.tsx (61 lines) - [screen] app/screens/checkout.tsx (727 lines) drivo has its own version of these, keep the project's file: components/Button.tsx, components/Header.tsx, components/forms/Input.tsx, ... Already identical in drivo: utils/BackHandlerManager.tsx 2. Packages: drivo already has every package these files use. 3. Imports: Rewrite @/app/contexts/... to @/contexts/... in every copied file. 4. Theme tokens: Used here but not defined in drivo: subtext. Add it (light and dark) or swap for an existing token. 5. Assets: Not served; replace with assets in the project: @/assets/img/delivery.png, @/assets/img/payment.png, ...
There is one license key per product line. Each key opens the server for its own templates.
Got questions? Please contact me on Email
The MCP server is included with both bundles. One payment, lifetime access, no subscription.
All current and future NativeWind templates for solo builders.
One-time payment · Lifetime access
Every NativeWind and Uniwind template, in one payment.
One-time payment · Lifetime access
Secure checkout via Polar