MCP

Connect your AI tool to NateUI so it can search components, read their docs, and get their source.

Tools

The NateUI MCP server gives your AI tool four read-only tools:

Tool	What it does
`search_catalog`	Search components and Blocks by name, layer, or tier.
`get_item`	Read one item's overview, API, examples, or source.
`get_guidelines`	Read a NateUI guideline topic, such as styling, forms, or navigation.
`get_skill`	Get the command that installs the agent skill for your tool.

None of the tools change your files. To install something it finds, your agent runs npx nateui@latest add in your project, the same command you would run.

Without a license key, your agent sees free components only. See Pro access.

Server address

https://nateui.com/mcp

The server is hosted and uses Streamable HTTP, so you don't run anything locally.

Setup

claude mcp add --transport http nateui https://nateui.com/mcp

Add --scope user to use it in every project, or --scope project to share it with your team through .mcp.json.

~/.codex/config.toml

[mcp_servers.nateui]
url = "https://nateui.com/mcp"

Or from the terminal:

codex mcp add nateui --url https://nateui.com/mcp

.cursor/mcp.json

{
  "mcpServers": {
    "nateui": {
      "url": "https://nateui.com/mcp"
    }
  }
}

Use ~/.cursor/mcp.json instead to enable it in every project.

opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nateui": {
      "type": "remote",
      "url": "https://nateui.com/mcp",
      "enabled": true
    }
  }
}

Use ~/.config/opencode/opencode.json instead to enable it in every project.

.vscode/mcp.json

{
  "servers": {
    "nateui": {
      "type": "http",
      "url": "https://nateui.com/mcp"
    }
  }
}

For every workspace, run MCP: Open User Configuration from the Command Palette and add the same entry there. Works with GitHub Copilot in agent mode.

Pro access

Send your license key in an Authorization header to unlock Pro components. Copy the key from your dashboard.

The examples below read the key from an environment variable named NATEUI_LICENSE_KEY, so it never lands in a file you might commit. Set it where your AI tool can see it, then restart the tool:

# macOS / Linux: add to your shell profile
export NATEUI_LICENSE_KEY="your-license-key"
 
# Windows
setx NATEUI_LICENSE_KEY "your-license-key"

claude mcp add --transport http nateui https://nateui.com/mcp \
  --header "Authorization: Bearer $NATEUI_LICENSE_KEY"

Keep the default local scope or use --scope user. In a shared .mcp.json, write the header as "Bearer ${NATEUI_LICENSE_KEY}" so each person uses their own key.

~/.codex/config.toml

[mcp_servers.nateui]
url = "https://nateui.com/mcp"
bearer_token_env_var = "NATEUI_LICENSE_KEY"

.cursor/mcp.json

{
  "mcpServers": {
    "nateui": {
      "url": "https://nateui.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:NATEUI_LICENSE_KEY}"
      }
    }
  }
}

opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nateui": {
      "type": "remote",
      "url": "https://nateui.com/mcp",
      "enabled": true,
      "headers": {
        "Authorization": "Bearer {env:NATEUI_LICENSE_KEY}"
      }
    }
  }
}

VS Code can ask for the key once and store it securely, so no environment variable is needed:

.vscode/mcp.json

{
  "inputs": [
    {
      "type": "promptString",
      "id": "nateui-license-key",
      "description": "NateUI license key",
      "password": true
    }
  ],
  "servers": {
    "nateui": {
      "type": "http",
      "url": "https://nateui.com/mcp",
      "headers": {
        "Authorization": "Bearer ${input:nateui-license-key}"
      }
    }
  }
}

With a valid key, search results and item source include Pro components. A key that is wrong, inactive, or revoked is rejected rather than treated as free access. Remove the header to go back to free.

Limits

Access	Tool calls per minute
Without a key	20, per network address
With a key	120, per license, shared across all your tools

Calls over the limit are refused until the next minute starts. The error says how long to wait.

Troubleshooting

Key rejected

Copy it again from your dashboard and check that the header reads Bearer followed by the key. A license that was refunded or revoked no longer works. To keep using free components, remove the header.

Pro components missing

The key isn't reaching the server. Check that the environment variable is set where your AI tool runs, and restart the tool after setting it.

Too many calls

You've reached the per-minute limit. Wait for the next minute; with a key, the limit is shared by every tool using it.

Can't connect

Check the address is exactly https://nateui.com/mcp and that your tool's version supports remote HTTP MCP servers.