MCP Server for Uniwind React Native Templates

CLAUDE.md knows one template. This knows all of them.

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:

Borrow a whole flow

“Add the checkout screen from UniBook to this app. Use our existing Button and Header.”

Find the right starting point

“Which templates have a chat screen? Show me how UniMarket builds its conversation view.”

Reuse a single piece

“I need a payment methods screen. Is there one in the library, and what does it depend on?”

What your agent can do

Eight read-only tools. Your agent picks them itself; you just describe what you want in plain language.

Browse templates

See every template in your bundle and each one's screens and components.

Search

Find screens, components and patterns by what they do: checkout, order tracking, paywall.

Read a screen

Get a screen's source together with the components, packages and images it depends on.

Read a component

Get one template's version of a component, its props, and where it is identical elsewhere.

Read any file

Hooks, contexts, mock data, layouts and config, by path.

Check conventions

Read a template's rules, or ask which component it uses for a given UI need.

Compare themes

Colour tokens for light and dark mode, and the differences between two templates.

Porting checklist

What to copy, what your project already has, missing packages, import changes and tokens.

Set it up in 2 minutes

Nothing to install. You add one address and your license key to your AI tool.

Copy your license key

Open the customer portal, sign in with the email you purchased with, open your bundle and copy the Uniwind MCP key. Paste it here and the commands below are filled in for you.

Your Uniwind MCP key

The key stays in your browser. It is not sent or saved anywhere by this page.

Add the server to your tool

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 Code (run in your terminal)

claude mcp add --transport http uniwind-templates https://www.uniwind-templates.com/api/mcp \
  --header "Authorization: Bearer YOUR_LICENSE_KEY" --scope user

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "uniwind-templates": {
      "url": "https://www.uniwind-templates.com/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_LICENSE_KEY" }
    }
  }
}

Codex

# in your shell profile
export UNIWIND_TEMPLATES_KEY="YOUR_LICENSE_KEY"

# in ~/.codex/config.toml
[mcp_servers.uniwind-templates]
url = "https://www.uniwind-templates.com/api/mcp"
bearer_token_env_var = "UNIWIND_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.

Ask for what you need

Restart your tool so it connects, then ask in plain language, for example: “Add the checkout screen from UniBook to this app. Use our existing Button and Header.” The agent searches the library, reads what it needs and adapts it to your project.

It tells your agent how to fit the pieces together

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.

Only copies what is missing
Files your project already has are kept, so you do not end up with two Buttons.
Catches the small differences
Import paths, colour tokens and packages that differ between templates are listed up front.
Nothing is changed for you
The server only reads. Your agent writes the code in your project, where you can review the diff.

porting checklist

Porting uni-book app/screens/checkout.tsx into a project based on uniwind

1. Files this needs (11):
   Copy from uni-book (not in uniwind), dependencies first:
   - [screen] app/screens/checkout.tsx (165 lines)
   uniwind has its own version of these, keep the project's file:
   components/Header.tsx, components/forms/Selectable.tsx,
   components/layout/Divider.tsx
   Already identical in uniwind: components/Button.tsx,
   components/Icon.tsx, components/forms/Input.tsx, ...

2. Packages:
   uniwind already has every package these files use.

3. Imports:
   Both templates use @/contexts; no path rewrite needed.

4. Theme tokens:
   All tokens used (background, secondary, text, border,
   primary, invert, highlight) exist in uniwind.

5. Assets:
   Not served; replace with assets in the project:
   @/assets/img/stay-1.jpg

Which key comes with which bundle

There is one license key per product line. Each key opens the server for its own templates.

Uniwind Bundle

Uniwind MCP key

This server (4 Uniwind templates)

NativeWind Bundle

NativeWind MCP key

Native Templates server

Mega Bundle

Both keys

Both servers

Single template

Not included

Upgrade to a bundle to get access

MCP server FAQ

Got questions? Please contact me on Email

It is a hosted server your AI coding tool connects to. It gives the agent a searchable library of the screens, components and conventions from all 4 templates in the Uniwind Bundle, so it can reuse a screen from one template in the app you are building from another.

Buyers of the Uniwind Bundle and the Mega Bundle. Single-template purchases do not include a license key.

In the customer portal. Sign in with the email you purchased with, open your bundle purchase and copy the license key. You can also rotate the key there if it leaks.

The Mega Bundle comes with two keys, one per product line. Use the Uniwind key with this server and the NativeWind key with the Native Templates server. You can add both servers to the same tool.

Claude Code, Cursor and Codex, and any other MCP client that can connect over HTTP and send an Authorization header.

No. Every tool is read-only and takes only template names, file paths and search words as input. Your project files stay on your machine; the agent decides what to write locally.

No. The server returns source code and conventions. Screens that reference images list them so the agent can substitute assets from your project.

Each license key can make up to 120 requests per minute, which is far more than a normal coding session uses. The key is for you and your team's own projects; do not share it publicly.

Check that you copied the whole key and that it is the key for this server, not the NativeWind one. If you rotated the key, update it in your tool. If it still fails, email me.

Early bird discount

All Uniwind Templates

Lifetime access to all current and future Uniwind React Native templates

$119$149

All future Uniwind templates

MCP server for AI agents

All future updates

Commercial license

Buy now

Mega Bundle

All Uniwind + NativeWind Templates

All Uniwind templates + all NativeWind templates from Native Templates — one price, forever

$149$199

All Uniwind templates

All NativeWind templates

Templates from both sites

All future templates

MCP servers for both libraries

All future updates

Commercial license

Buy now

Every template in your bundle, on call for your AI agent

CLAUDE.md knows one template. This knows all of them.

What your agent can do

Browse templates

Search

Read a screen

Read a component

Read any file

Check conventions

Compare themes

Porting checklist

Set it up in 2 minutes

Copy your license key

Add the server to your tool

Ask for what you need

It tells your agent how to fit the pieces together

Which key comes with which bundle

MCP server FAQ

What is the Uniwind Templates MCP server?

Who gets access?

Where do I find my license key?

I bought the Mega Bundle. Which key do I use?

Which AI tools does it work with?

Does the server see or change my code?

Are images and other assets included?

Are there usage limits?

What if my key stops working?

All Uniwind Templates

All Uniwind + NativeWind Templates